| Summary: | sys-fs/udisks:0 has issues with floppies (pinpointed to certain upstream commit), fixed in sys-fs/udisks:2 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ian Abbott <ian> |
| Component: | Current packages | Assignee: | Freedesktop bugs <freedesktop-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aklhfex, rick |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugs.freedesktop.org/show_bug.cgi?id=30283 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Partial strace from running /usr/libexec/udisks-daemon | ||
|
Description
Ian Abbott
2010-09-20 12:20:37 UTC
Created attachment 248163 [details]
Partial strace from running /usr/libexec/udisks-daemon
There were two udisks-daemon processes running, one is a child of the other. This strace is from the parent (process 2306) showing what happens when the 'mount' command is used to mount the floppy. The interesting part is where it (falsely) decides there is no media in the drive and causes it to be forcibly unmounted (around line 108 of the trace).
The reason it decided there was no media in the drive is because of the "no_floppy" patch applied to the sources.
I filed a bug report upstream: https://bugs.freedesktop.org/show_bug.cgi?id=30283 1.0.2 is tree now, and it includes the patch that caused the problem in the first place... upstream bug still open :/ Wait, you have floppy drive in /etc/fstab? It shouldn't be there if handled by udisks (udev). I guess this would be "INVALID" then... well, it still isn't nice to crash, right ? (In reply to comment #4) > Wait, you have floppy drive in /etc/fstab? It shouldn't be there if handled by > udisks (udev). I guess this would be "INVALID" then... > I can confirm that taking the floppy drive out of /etc/fstab allows it to be mounted with the 'mount' command, but only by 'root'. Trying to mount the floppy by opening the 'Floppy Drive' icon in the 'computer:///' (Computer) location in nautilus still fails with the error 'No medium in the drive', which I think is due to same bug, or at least a very similar bug. I have the same problem. Also you'll get an error message trying to unmount floppy: # udisks --unmount /dev/fd0 Unmount failed: Cannot unmount because file system on device is busy You must kill udisks-daemon to unmount it. http://bugs.freedesktop.org/show_bug.cgi?id=30283#c26 Solution: Use sys-fs/udisks:2 instead of sys-fs/udisks:0 (In reply to comment #8) > http://bugs.freedesktop.org/show_bug.cgi?id=30283#c26 > > Solution: Use sys-fs/udisks:2 instead of sys-fs/udisks:0 I suppose that means waiting for Gentoo to update Gnome or for a udisks2 patch to be developed for gnome-base/libgdu-3.0.2. (In reply to comment #9) > (In reply to comment #8) > > http://bugs.freedesktop.org/show_bug.cgi?id=30283#c26 > > > > Solution: Use sys-fs/udisks:2 instead of sys-fs/udisks:0 > > I suppose that means waiting for Gentoo to update Gnome or for a udisks2 > patch to be developed for gnome-base/libgdu-3.0.2. ... though perhaps not. I currently have the 'gdu' local USE flag set for gnome-base/gvfs in my /etc/portage/package.use but it probably isn't needed any more as gvfs also has the 'udisks' local USE flag set in my system's make.profile cascade. Use USE="udev udisks" instead of USE="udev gdu" for gnome-base/gvfs. The USE="udev udisks" is already the default for ~arch >=gnome-base/gvfs-1.12.3-r1. And will move to stable soon as we are ready to stabilize newer udev, messing with udev-171-r* is a waste of time as so so many fixes have landed to >=udev-192. So anyone suffering this problem: Change gvfs to use UDisks2 and drop any legacy programs still using UDisks1 as it's really going away... *** Bug 453744 has been marked as a duplicate of this bug. *** while sys-fs/udisks:2 is the real fix, I've now also added +*udisks-1.0.4-r5 (25 Jan 2013) + + 25 Jan 2013; Samuli Suominen <ssuominen@gentoo.org> +udisks-1.0.4-r5.ebuild, + +files/udisks-1.0.4-revert-floppy.patch: + Revert part of upstream commit that prevented UDisks1 from polling for floppy + drive so often but while at it broke the actual mounting of floppies wrt + #338185 by Ian Abbott and others luckily udisks:2 is in stable now too (at least for amd64, others pending) Updated udisks and floppies now work. Thanks for all your efforts.
It's not clear if the patch is the fix, since udiscs2 is now stable for x86, and the update brought in both:
> equery list udisks
* Searching for udisks ...
[IP-] [ ] sys-fs/udisks-1.0.4-r5:0
[IP-] [ ] sys-fs/udisks-2.0.91:2
|
