Usually I start X-window with XFCE4 by issuing "startx" in the command line. I noticed, that after expanding my .bashrc resource file, the icons, normally present on the left side (such as trash bin, drive icons etc.) doesn't appear anymore, and - even worse - I'm unable to bring menu by clicking right mouse button. After I exit X-window, I can see such error messages on the text screen: (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.90 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.92 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.94 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.96 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.98 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.100 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.102 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorUDisks2: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) (xfdesktop:8289): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.104 for volume monitor org.gtk.Private.UDisks2VolumeMonitor connected to the bus; seeding drives/volumes/mounts Googling around, I found this old thread: http://www.linuxquestions.org/questions/slackware-14/thunar-1-4-0-and-fluxbox-on-current-no-trash-or-automount-usb-devices-4175418186/ And indeed: I've got in my modified .bashrc the lines: export LC_ALL=pl_PL export LANG=pl_PL When I commented them out - or modified by adding "UTF-8", like this: export LC_ALL=pl_PL.UTF-8 export LANG=pl_PL.UTF-8 ...the problem doesn't occur anymore. Still: it should be working with ISO locale! Thunar 1.4.0, thunar-volman 0.8.0, Slackware 14 32-bit.
I forgot: kernel 3.7.0
The topic you link to had nothing to do with locales, but they claim dbus is not initialized for the client.
When my locales are ISO* - there is an error. When my locales are UTF* - there's no error. Checked it several times before filing a bug - the result was always the same. Now you're telling me, that it has nothing to do with locale settings.
I didn't say that, I said the link referrers to another problem/solution.
Ah, I misunderstood you, it seems. Alas, after such long time I'm unable to fix the link - maybe indeed I included different link by mistake (just can't remeber right now), not the one I wanted. Anyway, the described problem persists.
Please reopen if this is still a problem in current version (1.6.6 or newer).