Mageia x86_64 fully up to date. USB drive was a Western Digital "My Book" Raising this bug report so it is fixed before release of Mageia5, I don't know how many other users / USB devices this affects. Description of problem: After buying a new USB hard drive, it did nothing in Linux (was okay in Win7), no notification in the kickoff panel to access it and invisible in file managers like Dolphin. If the drive was formatted in gparted in that session for NTFS type, on completion there is notification in kickoff that the drive is ready for use, and you can move files to it using Dolphin. If you disconnect or reboot, the drive is no longer accessible (it appears invisible). If you find the drive mount point (/dev/sdg for example), you can mount it using the mount command as root, but only root can see it, the kickoff does not show any notification of the drive mounting. If you left the USB drive connected when rebooting, any normal user can access the USB drive using Dolphin, but as soon as it's unmounted, it becomes invisible to the system if you try re-mounting it (disconnect / reconnect). After searching the internet, someone on another Linux distro has the same problem, he performed more extensive tests than I performed, and found a workaround. Having implemented this workaround, I have not found a problem in normal use of the system, so maybe it should be permenant solution and rolled out to future Mageia releases. Solution: The problem was not in KDE as I thought, but a udev problem. https://bugzilla.redhat.com/show_bug.cgi?id=1091513 What the comment states is: " I traced the problem to a "blkid" filesystem probe in "/usr/lib/udev/rules.d/60-persistent-storage.rules" @ line 70. Calling blkid manually takes around 34 seconds to return on my machine, so udev kills it at 30 seconds. The excessive blkid wait is triggered higher up in "60-persistent-storage.rules" @ line 35, where "ata_id" is called to probe the device. I believe one of the ata_id returned attributes is causing blkid to probe for something that isn't there. A temporary fix is to comment out line 35, causing a fallback to "usb_id" rule at line 37, and a successful blkid probe. After implementing this suggestion, the USB drive is no longer invisible to the system. Reproducible: Steps to Reproduce:
CC: (none) => mageia, tmb
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD