You are not logged in.
Starting sometime a few days ago—I'm not sure when—Thunar stopped automounting removable media. Before that it was automounting OK. I'm using a by-the-wiki Openbox/Thunar/PolicyKit/etc. setup.
Today I got around to diagnosing the problem. I checked my pacman.log and saw that a few days ago a new package, udisks2, was installed. Also, gvfs was upgraded. Those are suspects. But I couldn't find any instructions online explaining what to do, so I dug deeper.
I started thunar from the command line and inserted a USB flash drive. It outputted the following warnings and errors, which, judging by a search of users' past Thunar mounting problems, are typical when Thunar fails to automount.
thunar-volman: Unsupported USB device type.
thunar-volman: Unsupported USB device type.
thunar-volman: Unknown block device type.
thunar-volman: Could not detect the volume corresponding to the device.
I ran strace to see how thunar was invoking thunar-volman. I then manually started thunar-volman with the same arguments.
thunar-volman --device-added /sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/usb2/2-1/2-1:1.0/host15/target15:0:0/15:0:0:0/block/sdb/sdb1
It worked! The device was mounted correctly. Why?
I wrote a script, /usr/local/bin/thunar-volman, which precedes the system's /usr/bin/thunar-volman in $PATH. All my script does is sleep for a second and then invoke the system's thunar-volman with the same arguments. Then I logged out and in to restart everything and confirmed that Thunar automounting now works with the extra sleep 1. Problem solved… kinda.
I would like to submit a bug report, but I don't even know which package is at fault here. Does anyone have any ideas?
Last edited by c.m.brandenburg (2012-04-27 19:06:07)
Offline
udisks2 required me to change a PolicyKit Local Autority entry as it didn't aquire permissions granted for udisks(1).
You can take a look here for more info: https://bbs.archlinux.org/viewtopic.php … 7#p1093197
It must be a combination of PolicyKit & udev2 that causes the problem.
I added a note at the wiki which - I hope - helps to solve it.
Offline
udisks2 required me to change a PolicyKit Local Autority entry as it didn't aquire permissions granted for udisks(1).
I don't have that file. In fact, the only file I have in /etc/polkit-1 is /etc/polkit-1/localauthority.conf.d/50-localauthority.conf.
In any event, my problem doesn't appear to be a permission problem, being as how Thunar automounts OK so long as it delays an extra second before doing so.
Offline
Did you ever find the solution for this? I am experiencing the same issue atm
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
Yes and no. The problem went away for me after some unknown number of system upgrades. Eventually I was able to delete my thunar-volman wrapper script and have everything work as normal.
Good luck.
Offline
I am experiencing a similar issue after the Jun 1 update that merged udev with systemd, and installed udisks2, only I use PacmanFM, not Thunar.
"I just don't know what went wrong" - Derpy
Offline
Same here. Thunar doesn't automount anymore after the update. The fix posted above doesn't work for me.
Offline
I don't know if you'll consider this a solution, but I use udiskie to get removable drives to automount in Xfce. Python2-udiskie is in community now. Works flawlessly. BTW, when I ran Openbox this is what I used as well.
Last edited by oboedad55 (2012-06-26 05:09:46)
Registered Linux user #436067
Offline
Reboot if you updated your system recently, specifically the linux package (the Linux kernel).
Always reboot after a kernel update. Then USB devices will start working again.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Reboot if you updated your system recently, specifically the linux package (the Linux kernel).
Thank you. I feel like an idiot now because I always reboot after a bigger update, but apparently not this time. So this was indeed the solution. Sorry for wasting anyone's time.
Offline