sys-fs/udisks-2.1.0 binds usb volumes to /run/media/uuid/label. xfce-extra/thunar-volman expect them at /media/label. So it does not automount them. sys-fs/udisks-2.1.0 is pulled by gnome-base/gvfs-1.12.3-r1. ---------------------------------------- emerge -pv --depclean udisks gvfs thunar Calculating dependencies... done! gnome-base/gvfs-1.12.3-r1 pulled in by: xfce-base/thunar-1.4.0 requires >=gnome-base/gvfs-1.10.1[udisks,udev], >=gnome-base/gvfs-1.10.1 sys-fs/udisks-2.1.0 pulled in by: gnome-base/gvfs-1.12.3-r1 requires >=sys-fs/udisks-1.90:2 xfce-base/thunar-1.4.0 pulled in by: xfce-extra/thunar-volman-0.8.0 requires >=xfce-base/thunar-1.4[udev] ---------------------------------------- There is a Solution: You don't need udisks for gvfs. So set the use flag -udisks in /etc/portage/package.use: gnome-base/gvfs-1.12.3-r1
Sorry there is an error. This is right: So set the use flag -udisks in /etc/portage/package.use: gnome-base/gvfs-1.12.3-r1 -udisks
Works fine here with UDisks2 because Thunar nor thunar-volman doesn't use UDisks* directly at all, there is no reference to /media in thunar-volman sources at all Instead it uses whatever you have compiled gnome-base/gvfs with (USE="udev gdu -udisks" for UDisks1, USE="udev udisks -gdu" for UDisks2) As in... Thunar doesn't care what UDisks is being used by gvfs... Thunar -> File Manager Preferences -> Advanced -> Removable Drives and Media -> Make sure [X] is enabled for at least the 2 first opts: Mount removable drives ... media ... For eg. my USB stick got automounted as /run/media/ssuominen/SYSRESC (it's a systemrescuecd image on USB stick) and Thunar automatically mounted and popped up a window I can browse it I know this to be working on multiple other distributions too as I have this setupped this was on production at work So you'll have to provide a bit more info what doesn't work
These work: [ebuild R ] xfce-extra/thunar-volman-0.8.0 USE="libnotify -debug" 0 kB [ebuild R ] xfce-base/thunar-1.6.2 USE="dbus exif libnotify pcre startup-notification udev -debug {-test}" XFCE_PLUGINS="trash" 1,908 kB [ebuild R ] gnome-base/gvfs-1.14.2 USE="archive cdda fuse gtk http udev udisks -afp -avahi -bluetooth -bluray -doc -gdu -gnome-keyring -gphoto2 -ios -samba -systemd" 1,434 kB [ebuild R ] sys-fs/udisks-2.1.0:2 USE="crypt gptfdisk introspection -debug (-selinux) (-systemd)" 0 kB
(In reply to comment #3) > These work: > > [ebuild R ] gnome-base/gvfs-1.14.2 USE="archive cdda fuse gtk http > udev udisks -afp -avahi -bluetooth -bluray -doc -gdu -gnome-keyring -gphoto2 > -ios -samba -systemd" 1,434 kB This work for me too with the new mountpoints, but gnome-base/gvfs-1.14.2 is not stable. eix -I gvfs [I] gnome-base/gvfs Available versions: 1.12.3 1.12.3-r1 ~1.14.2 [M]~1.16.0 { So you still have to solve the problem manually.
(In reply to comment #4) > (In reply to comment #3) > > These work: > > > > [ebuild R ] gnome-base/gvfs-1.14.2 USE="archive cdda fuse gtk http > > udev udisks -afp -avahi -bluetooth -bluray -doc -gdu -gnome-keyring -gphoto2 > > -ios -samba -systemd" 1,434 kB > > This work for me too with the new mountpoints, but gnome-base/gvfs-1.14.2 is > not stable. > > eix -I gvfs > [I] gnome-base/gvfs > Available versions: 1.12.3 1.12.3-r1 ~1.14.2 [M]~1.16.0 { > > So you still have to solve the problem manually. Converting this to stabilization request of new gvfs then.
gnome: OK to CC arch teams to get working gvfs stable?
I am using thunar and thunar-volman with gvfs-1.12.1-r1[udisks]. These work fine for hotplugging and automounting USB sticks, so this bug sounds little bit strange to me... xfce-base/thunar-1.6.2 was built with the following: USE="dbus exif libnotify pcre startup-notification udev -debug -test" XFCE_PLUGINS="trash" xfce-extra/thunar-volman-0.8.0 was built with the following: USE="libnotify -debug" gnome-base/gvfs-1.12.3-r1 was built with the following: USE="udev udisks -afp -archive -avahi -bluetooth -bluray -cdda -doc -fuse -gdu -gnome-keyring -gphoto2 -http -ios -samba" sys-fs/udisks-2.1.0 was built with the following: USE="crypt gptfdisk introspection -debug (-selinux) (-systemd)" PS. I, as a normal user, have no objection for newer gvfs stabilization. I wrote this as just for your information.
(In reply to comment #7) > xfce-base/thunar-1.6.2 was built with the following: > USE="dbus exif libnotify pcre startup-notification udev -debug -test" > XFCE_PLUGINS="trash" xfce-base/thunar-1.6.2 is not stable too. eix -I thunar [I] xfce-base/thunar Available versions: 1.4.0 ~1.6.1 ~1.6.2
(In reply to comment #8) > (In reply to comment #7) > > xfce-base/thunar-1.6.2 was built with the following: > > USE="dbus exif libnotify pcre startup-notification udev -debug -test" > > XFCE_PLUGINS="trash" > > xfce-base/thunar-1.6.2 is not stable too. > > eix -I thunar > [I] xfce-base/thunar > Available versions: 1.4.0 ~1.6.1 ~1.6.2 We will handle Thunar stabilization in another bug. I'll file one mass bug for all of the outdated Xfce packages together as we have always done. Lets just stick with the stabilization of new gvfs here. For that, we don't need a discussion here, just waiting for gvfs maintainers to CC archteams if they are fine with us proceeding.
(In reply to comment #9) > Lets just stick with the stabilization of new gvfs here. For that, we don't > need a discussion here, just waiting for gvfs maintainers to CC archteams if > they are fine with us proceeding. It was just a information, not a new stable request. Sorry!
It cannot be stabilized because it needs glib-2.34, that has problems with gnome2 (like bug #450930)
(In reply to comment #11) > It cannot be stabilized because it needs glib-2.34, that has problems with > gnome2 (like bug #450930) Ouch. And I was about to make libcdio, libcdio-paranoia, cdparanoia, eselect-cdparanoia stabilization Tracker depend on this bug as we need 1.14 for that too...
For now, I've simply masked USE=udisks for <gnome-base/gvfs-1.14, as suggested by Samuli.
Well, base/package.use.mask and the desktop profile was fixed so that gvfs-1.12.3-r1's default is still gdu, instead of udisks2 And Xfce, as in, the new required Thunar is now going stable too in bug 465286 And once gnome@ folks are ready, we can get newer gvfs stable, but I expect that to happen on those "Gnome stabilization list, April 2013" bugs So closing this one Thanks!
