[SOLVED] Thunar 1.4.0 and Fluxbox on -current: no trash or automount usb devices
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
so weird... i have automount working on my old laptop using XFCE 4.10
no special tunning, just install fresh
probably it's because a new installation. The bug only occurred when upgrading from previous version?
It's fine in xfce - the trouble is with fluxbox (and probably a few other non-(kde|xfce) environments).
seems that the "dbus-launch --exit-with-session" addition is needed also with blackbox, wmaker, fvwm2 and openbox.
twm, i3 and wmii don't work with thunar even with the addition.
seems that the "dbus-launch --exit-with-session" addition is needed also with blackbox, wmaker, fvwm2 and openbox.
twm, i3 and wmii don't work with thunar even with the addition.
Sorry Pat, I got it wrong: I launched thunar from one of the pre-started xterms, and it hadn't got the consolekit session.
Starting it from a newly created xterm from the twm environment, it works
I have to add to the twm invocation in xinitrc "ck-launch-session dbus-launch --exit-with-session"
If I launch Thunar in Fluxbox with "ck-launch-session dbus-launch --exit-with-session" added to .xinitrc Thunar freezes and spits out the following in a terminal window/console:
Code:
(Thunar:7622): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.453 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts
(Thunar:7622): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
(Thunar:7622): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.455 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts
(Thunar:7622): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
What causes that?
Update: I've reinstalled Xfce and dbus, but I've yet to find where the problem lies...
Last edited by mats_b_tegner; 07-23-2012 at 04:17 PM.
reverified also with wmii and i3 (sorry I don't them that much and I had made a similar error as with twm): it works fine also there adding the "dbus-launch --exit-with-session".
mats, just FYI, I just tried here with fluxbox with the same addition and I don't have those errors (it works).
If I launch Thunar in Fluxbox with "ck-launch-session dbus-launch --exit-with-session" added to .xinitrc Thunar freezes and spits out the following in a terminal window/console:
Code:
(Thunar:7622): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.453 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts
(Thunar:7622): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
(Thunar:7622): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.455 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts
(Thunar:7622): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
What causes that?
Update: I've reinstalled Xfce and dbus, but I've yet to find where the problem lies...
I had that same problem. Try setting your locale to UTF-8.
I updated to current again today. My xinitrc files all have the added dbus-launch stuff--Thunar works fine in XFCE but not in windowmaker. No errors appear when run from a terminal. What else could it be?
If I run: dbus-launch thunar
then it works fine. I never needed to do that before, but launching it this way works.
Last edited by htitan; 09-01-2012 at 10:51 PM.
Reason: solved problem
Upgraded to RC4 and Thunar automounting of hard drive partitions and usb sticks works fine in Xfce, Windowmaker, and Fluxbox. If you are having issues, you might want to consider removing some things from ~/.cache -- perhaps the Thunar and any Xfce related directories. I would also remove ~/.gvfs and then try again.
@htitan - is your user a member of the plugdev group? That is required for the 20-plugdev-group-mount-override.pkla file in /etc/polkit/localauthority/50-local.d/.
@htitan - is your user a member of the plugdev group? That is required for the 20-plugdev-group-mount-override.pkla file in /etc/polkit/localauthority/50-local.d/.
Hmmm..... my own file is in a slightly different location:
# Start the window manager:
if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
exec ck-launch-session dbus-launch --exit-with-session /usr/bin/startfluxbox
else
exec /usr/bin/startfluxbox
fi
to achieve auto-mounting. Not sure if this is relevant?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.