>>>>>>>>>> When trying to eject a USB camera in thunar in xfce4, the error >>>>>>>>>> appears and the device >>>>>>>>>> does not umount. Here is a command that also produces the error: >>>>>>>>>> >>>>>>>>>> # udisks --detach /dev/sdb Detach failed: Error detaching: helper >>>>>>>>>> exited with exit code >>>>>>>>>> 1: Detaching device /dev/sdb USB device: >>>>>>>>>> /sys/devices/pci0000:00/0000:00:02.0/usb2/2-6) SYNCHRONIZE CACHE: >>>>>>>>>> FAILED: No such file >>>>>>>>>> or directory (Continuing despite SYNCHRONIZE CACHE failure.) STOP >>>>>>>>>> UNIT: FAILED: No such >>>>>>>>>> file or directory >>>>>>>>>> >>>>>>>>>> # emerge -pv gvfs libgdu [ebuild R ] gnome-base/libgdu-3.0.2 >>>>>>>>>> USE="-avahi -doc >>>>>>>>>> -gnome-keyring" 0 kB [ebuild R ] gnome-base/gvfs-1.12.3-r1 >>>>>>>>>> USE="cdda gdu http >>>>>>>>>> udev -afp -archive -avahi -bluetooth -bluray -doc -fuse >>>>>>>>>> -gnome-keyring -gphoto2 -ios >>>>>>>>>> -samba (-udisks)" 0 kB >>>>>>>>> ^^^^^^^ >>>>>>>>> >>>>>>>>> There's your problem. >>>>>>>>> >>>>>>>>> thunar depends on gvfs, which can use udisks, but in your case the >>>>>>>>> USE flag is forced, >>>>>>>>> masked, or removed. >>>>>>>>> >>>>>>>>> You need to find out why that happened, it might be a profile thing, >>>>>>>>> maybe it's a local >>>>>>>>> config. Try >>>>>>>>> >>>>>>>>> grep -r udisks /etc/portage/ >>>>>>>> >>>>>>>> Nothing comes back from that grep. My profile is >>>>>>>> default/linux/amd64/13.0/desktop. What >>>>>>>> else could be preventing me from enabling that USE flag? >>>>>>> >>>>>>> It might be masked by the profile. As I understand it, recent EAPIs >>>>>>> allow USE flags to be >>>>>>> forced per-profile. This makes sense - a dev might enable USE=udev >>>>>>> everywhere except on >>>>>>> gentoo-freebsd profiles, just as an example. But I'm not yet up to >>>>>>> speed on how to detect and >>>>>>> over-ride such things. >>>>>>> >>>>>>> I think you should log a bug now at b.g.o. and let the devs tell you >>>>>>> what's really going on >>>>>>> with your selections. >>>>>> >>>>>> Will do, and I'll report back with the results. >>>>>> >>>>>> Thanks, Grant >>>>>> >>>>> >>>>> - From $PORTDIR/profiles/base/package.use.mask: >>>>> >>>>> # GNOME <gn...@gentoo.org> (02 Oct 2012) >>>>> # Mask USE="udisks" and use USE="gdu" as the default for >>>>> <gnome-base/gvfs-1.14; >>>>> # older gvfs releases have problems with recent stable udisks:2 (bug >>>>> #463792) >>>>> <gnome-base/gvfs-1.14 udisks >>>> >>>> OK, there it is. If I keyword gvfs I get into trouble because >>>> gobject-introspection wants <dev-libs/glib-2.33 and gvfs wants >>>>> =dev-libs/glib-2.36. >>> >>> >>> Don't keyword gvfs, >>> >>> for gvfs: >>> >>> USE="-udisks gdu" >>> >>> gvfs doesn't care what does the automounting, as long as something does >> >> That's what I have now and I have this ejecting problem. Should I >> just emerge udisks-2 into a new slot? > > > I have a hunch that won't work and USE="udisks" is hard masked for gvfs. > Logic tells me that even if udisks:2 is available, gvfs won't use it. > > But, it's worth a try.
I tried but no luck. I should hear from the maintainer soon. Another SLOT question. udisks:0 was installed and now udisks:2. What about slot #1? - Grant > I also think you need the maintainer to take a closer look - it all > looks like the ebuild needs some tweaking, or maybe it's just a magic > combination of USE that we missed.
