LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page [SOLVED] XFCE4 Thunar does not automount USB flash drive
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
Page 1 of 2 1 2
  Search this Thread
Old 02-04-2020, 06:43 AM   #1
mchagas
LQ Newbie
 
Registered: Oct 2010
Location: Brasil
Distribution: Slackware64 current
Posts: 27

Rep: Reputation: 10
XFCE4 Thunar does not automount USB flash drive

Hi,

After a fresh install of Slackware64 -current I noticed that XFCE4 Thunar does not automount USB.

Running dbus-launch thunar, I have this messages:
Code:
$ dbus-launch thunar
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127 (g-dbus-error-quark, 25)
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127 (g-dbus-error-quark, 25)
thunar-volman: Unsupported USB device type "usb".
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127 (g-dbus-error-quark, 25)
thunar-volman: Unsupported USB device type "usb-storage".
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127 (g-dbus-error-quark, 25)
thunar-volman: Could not detect the volume corresponding to the device.
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127 (g-dbus-error-quark, 25)
thunar-volman: Could not detect the volume corresponding to the device.
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127 (g-dbus-error-quark, 25)
thunar-volman: Could not detect the volume corresponding to the device.
And /var/log/messages is showing this:

Code:
Feb  4 09:41:00 lovelace kernel: [ 3088.392002] usb 1-1.2: new high-speed USB device number 13 using ehci-pci
Feb  4 09:41:00 lovelace kernel: [ 3088.406920] usb 1-1.2: New USB device found, idVendor=0781, idProduct=5571, bcdDevice= 1.27
Feb  4 09:41:00 lovelace kernel: [ 3088.406927] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb  4 09:41:00 lovelace kernel: [ 3088.406931] usb 1-1.2: Product: Cruzer Fit
Feb  4 09:41:00 lovelace kernel: [ 3088.406934] usb 1-1.2: Manufacturer: SanDisk
Feb  4 09:41:00 lovelace kernel: [ 3088.406937] usb 1-1.2: SerialNumber: 4C530007060205114090
Feb  4 09:41:00 lovelace kernel: [ 3088.407160] usb-storage 1-1.2:1.0: USB Mass Storage device detected
Feb  4 09:41:00 lovelace kernel: [ 3088.407264] scsi host6: usb-storage 1-1.2:1.0
Feb  4 09:41:00 lovelace mtp-probe: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2" 
Feb  4 09:41:00 lovelace mtp-probe: bus: 1, device: 13 was not an MTP device 
Feb  4 09:41:00 lovelace dbus-daemon[2797]: [session uid=1000 pid=2795] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.138' (uid=1000 pid=5722 comm="thunar-volman --device-added /sys/devices/pci0000:")
Feb  4 09:41:00 lovelace dbus-daemon[2797]: [session uid=1000 pid=2795] Activated service 'org.gtk.vfs.UDisks2VolumeMonitor' failed: Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127
Feb  4 09:41:00 lovelace dbus-daemon[2797]: [session uid=1000 pid=2795] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.142' (uid=1000 pid=5728 comm="thunar-volman --device-added /sys/devices/pci0000:")
Feb  4 09:41:00 lovelace dbus-daemon[2797]: [session uid=1000 pid=2795] Activated service 'org.gtk.vfs.UDisks2VolumeMonitor' failed: Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127
Feb  4 09:41:01 lovelace kernel: [ 3089.426215] scsi 6:0:0:0: Direct-Access     SanDisk  Cruzer Fit       1.27 PQ: 0 ANSI: 6
Feb  4 09:41:01 lovelace kernel: [ 3089.428035] sd 6:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
Feb  4 09:41:01 lovelace kernel: [ 3089.430298] sd 6:0:0:0: [sdb] Write Protect is off
Feb  4 09:41:01 lovelace kernel: [ 3089.431522] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb  4 09:41:01 lovelace kernel: [ 3089.451108]  sdb: sdb1 sdb2
Feb  4 09:41:01 lovelace kernel: [ 3089.456408] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Feb  4 09:41:01 lovelace dbus-daemon[2797]: [session uid=1000 pid=2795] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.146' (uid=1000 pid=5736 comm="thunar-volman --device-added /sys/devices/pci0000:")
Feb  4 09:41:01 lovelace dbus-daemon[2797]: [session uid=1000 pid=2795] Activated service 'org.gtk.vfs.UDisks2VolumeMonitor' failed: Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127
Feb  4 09:41:06 lovelace dbus-daemon[2797]: [session uid=1000 pid=2795] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.150' (uid=1000 pid=5746 comm="thunar-volman --device-added /sys/devices/pci0000:")
Feb  4 09:41:06 lovelace dbus-daemon[2797]: [session uid=1000 pid=2795] Activated service 'org.gtk.vfs.UDisks2VolumeMonitor' failed: Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127
Feb  4 09:41:11 lovelace dbus-daemon[2797]: [session uid=1000 pid=2795] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.154' (uid=1000 pid=5753 comm="thunar-volman --device-added /sys/devices/pci0000:")
Feb  4 09:41:11 lovelace dbus-daemon[2797]: [session uid=1000 pid=2795] Activated service 'org.gtk.vfs.UDisks2VolumeMonitor' failed: Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127
Thunar-volman is configured to automount removable storages

Does anyone know how to solve this?

---
UPDATE:

Check if you have libluray installed! It's a dependency to thunar and thunar-volman works properly.
Plus gvfs, udisks, udisks2, dbus and polkitd installed and running!
Last edited by mchagas; 02-05-2020 at 07:29 PM.
 
Old 02-04-2020, 09:24 AM   #2
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,631

Rep: Reputation: 489Reputation: 489Reputation: 489Reputation: 489Reputation: 489
> Thunar-volman is configured to automount removable storages

Just a stupid question here, but did you remember to reinstall the Thunar-volman plugin after the new install of Slack Current?
 
1 members found this post helpful.
Old 02-04-2020, 11:29 AM   #3
mchagas
LQ Newbie
 
Registered: Oct 2010
Location: Brasil
Distribution: Slackware64 current
Posts: 27

Original Poster
Rep: Reputation: 10
Hi Eric,

The hole system is a new fresh install. This should not work that way?

But, just to take this doubt out, I reinstalled the thunar-volman right now and have same issue.

Thanks.
 
1 members found this post helpful.
Old 02-04-2020, 11:42 AM   #4
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware64-Current
Posts: 871

Rep: Reputation: 364Reputation: 364Reputation: 364Reputation: 364
I just solved this on my old desktop. Go into settings and look for removable drives. The settings are there and you can change them to suit your circumstances
Last edited by Gordie; 02-04-2020 at 11:48 AM.
 
Old 02-04-2020, 11:56 AM   #5
mchagas
LQ Newbie
 
Registered: Oct 2010
Location: Brasil
Distribution: Slackware64 current
Posts: 27

Original Poster
Rep: Reputation: 10
Hi Gordie,

If you talking about Thunar > Edit > Preferences [Advanced tab] - Volume Management (Enable Volume Management) is set.
And in the configuration of management of removable drives, devices and media is ticked the to mount removable drives options available.

This isn't look simples as options on the GUI. IMO.

Thanks anyway.
 
Old 02-04-2020, 04:59 PM   #6
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,374

Rep: Reputation: 2753Reputation: 2753Reputation: 2753Reputation: 2753Reputation: 2753Reputation: 2753Reputation: 2753Reputation: 2753Reputation: 2753Reputation: 2753Reputation: 2753
This looks like a dbus issue.
Are you starting the dbus daemon at boot? i.e. Is /etc/rc.d/rc.messagebus executable?
Does it work if you boot to run level 3 then run 'startx', but not if you boot directly to run level 4?
 
Old 02-04-2020, 05:49 PM   #7
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,631

Rep: Reputation: 489Reputation: 489Reputation: 489Reputation: 489Reputation: 489
Thanks for the reply, @mchagas. Like I said, it was probably a stupid question, but had to check before any of us could continue on with assisting you.
 
Old 02-04-2020, 07:11 PM   #8
mchagas
LQ Newbie
 
Registered: Oct 2010
Location: Brasil
Distribution: Slackware64 current
Posts: 27

Original Poster
Rep: Reputation: 10
Quote:
Originally Posted by allend View Post
This looks like a dbus issue.
Are you starting the dbus daemon at boot? i.e. Is /etc/rc.d/rc.messagebus executable?
Does it work if you boot to run level 3 then run 'startx', but not if you boot directly to run level 4?
Hi, yes, messagebus is executable. And it is starting at boot. Does not work, at run level 3 wheither level 4, that's what I'm using actually.
I'm always use -current, and a month ago, after this fresh install, was working normally..

IDK whats possible got wrong this time.. last time dbus was upgraded on -current was in march 8, 2018 dbus-python was rebuilt against python3 in last december 31 and after that had an upgrade january 14.. could this be related?

Hey Eric, I'm really appreciate your help!

Thanks everybody.
 
1 members found this post helpful.
Old 02-04-2020, 07:21 PM   #9
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware64-Current
Posts: 871

Rep: Reputation: 364Reputation: 364Reputation: 364Reputation: 364
Quote:
Originally Posted by mchagas View Post
Hi Gordie,

If you talking about Thunar > Edit > Preferences [Advanced tab] - Volume Management (Enable Volume Management) is set.
And in the configuration of management of removable drives, devices and media is ticked the to mount removable drives options available.

This isn't look simples as options on the GUI. IMO.

Thanks anyway.

XFCE Settings
 
Old 02-04-2020, 07:34 PM   #10
mchagas
LQ Newbie
 
Registered: Oct 2010
Location: Brasil
Distribution: Slackware64 current
Posts: 27

Original Poster
Rep: Reputation: 10
Quote:
Originally Posted by Gordie View Post
XFCE Settings
Hi Gordie, could you be more specific?

I've already configured xfce4-settings-manager and xfce4-settings-editor. Automout drives and medias are set.

Thanks for your reply.
 
Old 02-04-2020, 08:12 PM   #11
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware64-Current
Posts: 871

Rep: Reputation: 364Reputation: 364Reputation: 364Reputation: 364
You know, the laptop I am on is set to boot directly into plasma 5. It is no picnic to change it so I can get to XFCE. The desktop is in the basement and Parkinson's Disease is really giving me a bad time today so I cannot risk the stairs.

Look. It is there but I can't do it for you
 
Old 02-04-2020, 08:45 PM   #12
Uncle Lumpy
Member
 
Registered: Feb 2010
Posts: 63

Rep: Reputation: 48
I'm not Gordie, but if I open the Settings manager in XFCE, then click on File Manager Settings, then the Advanced tab, I see a Volume Management section at the bottom. There is a clickable link (Configure) in the description for Volume Management that takes you to a settings page that might be relevant. Maybe.

Hope that helps!
Lumpy
 
1 members found this post helpful.
Old 02-04-2020, 09:02 PM   #13
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware64-Current
Posts: 871

Rep: Reputation: 364Reputation: 364Reputation: 364Reputation: 364
I did a search.

https://docs.xfce.org/xfce/thunar/using-removable-media
 
1 members found this post helpful.
Old 02-04-2020, 09:03 PM   #14
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,631

Rep: Reputation: 489Reputation: 489Reputation: 489Reputation: 489Reputation: 489
@mchagas, I believe @Gordie may be talking about "Enable Volume Management", but I see that you've already set that to "Enable" in your post above.

From your posts above, it looks like you're going to have to determine why "org.gtk.vfs.UDisks2VolumeMonitor" is failing to start. Duh. I guess you figured that part out already.

Anyway, if I'm covering old ground here, forgive me. I've had three or four bourbon drinks tonight. Keep us posted on any progress.

I'm beginning to agree with Allend here that this may be a Dbus issue.

Oh, and... just curious, but can you manually mount the USB device?

~Eric
 
Old 02-04-2020, 09:05 PM   #15
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,631

Rep: Reputation: 489Reputation: 489Reputation: 489Reputation: 489Reputation: 489
Quote:
Originally Posted by Uncle Lumpy View Post
I'm not Gordie, but if I open the Settings manager in XFCE, then click on File Manager Settings, then the Advanced tab, I see a Volume Management section at the bottom. There is a clickable link (Configure) in the description for Volume Management that takes you to a settings page that might be relevant. Maybe.

Hope that helps!
Lumpy

Ah, and YES. I see what Lumpy is talking about here. You need to check those settings, for sure.
 
  


Reply
Page 1 of 2 1 2



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Android phone : Thunar[1765]: thunar-volman: Unsupported USB device type "(null)". DBabo Linux - Software 10 08-28-2019 01:59 PM
[SOLVED] Thunar does not automount USB stick in Windowmaker on Slackware64-current allend Slackware 4 04-18-2016 08:29 AM
[SOLVED] Failed to mount ... Not authorized (xfce4 or Thunar) kaz2100 Debian 13 10-02-2014 06:34 AM
[SOLVED] Thunar 1.4.0 and Fluxbox on -current: no trash or automount usb devices andrew.46 Slackware 29 09-05-2012 02:59 AM
How to automount usb flash drives in Thunar (openbox) iamthat Linux - Newbie 1 05-12-2010 12:56 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:21 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration