If I plug a removable drive while the system is running, it is detected and auto-mounted, but if I start the system with the drive *already* plugged, the drive is detected (I can see its icon) but it isn't automatically mounted.
Why should it be mounted on startup?
Because if I insert it and it is auto-mounted, then it should be auto-mounted if it already inserted on startup (it would be a coherent behaviour: the concept is "mount what is inserted").
Totally agree with this. I have a regular pair of external drives, for my desktop-replacement laptop, one of which I keep music on. MPD will not start because I can't get the drive to mount at startup. I have to killall any running MPDs, then mount the drive with a right-click, then run MPD -- everytime I boot. I thought I was going crazy for a while -- the music was there when I double-clicked on the drive (because then Thunar would mount the drive.) As to the question "why should it be mounted at startup?" -- why SHOULDN'T it be? It's plugged in for a reason, isn't it? :) And I've set drives to be automounted in preferences. I assume that currently there is nowhere to configure this behavior? volmanrc doesn't seem to have anything. Thunar rocks, honestly. I've fallen in love with Custom Actions, and the Renamer. m a r (In reply to comment #2) > Because if I insert it and it is auto-mounted, then it should be auto-mounted > if it already inserted on startup (it would be a coherent behaviour: the > concept is "mount what is inserted"). >
Mass reassign. Nick, please check these pending reports. Thx.
Created attachment 2769 Parse all UDI's at start The attached patch fixes this bug. It was written for thunar 0.2.0-2, I'll update it to the latest version when I have the time or someone else can. What this patch does is when the thunar daemon is first started it gets all the UDI's from HAL and handles each of them as if they were just plugged in. This does mean that if you have something configured to pop-up when a mouse or printer is plugged in it will do that as soon as thunar is started. It would however be a very simple change for it to only handle storage devices.
Created attachment 2791 Updated patch which only handles volumes While thunar-volman can handle many different devices it really doesn't make sense to pass every UDI to thunar-volman. It actually causes problems so just pass the volumes. This mimics that way gnome-volume-manager does it.
I forgot to mention I've been testing this patch on both x86 and armel. The platform should be changed to all Linux.
I finally got some time to test this under Xfce 4.6 with thunar 1.0.1 and thunar-volman 0.3.80. I can confirm the posted patch works with the latest packages.
I'm having this issue too - when my laptop is docked, I like to use external drives for back-up and media. fstab's not a great option because I dock / undock the laptop a lot. Can I apply still apply this patch to the current source code, or is it outdated?
*** Bug 9240 has been marked as a duplicate of this bug. ***
I can get my "regular" drives auto-mounted using a script during startup, as follows (Xubuntu 12.04): thunar-volman --device-added /sys$(udevadm info -q path -n /dev/disk/by-uuid/09f41052-ce64-4d14-9684-e0b5bd241a5c) (replace UUID with the UUID of your drive) This makes thunar volume manager think the disk has just been added, allowing it to do its mounting thing. It uses udevadm to convert the UUID to the sysfs device path, as thunar-volman does not accept UUIDs. You can get disk UUIDs (on Ubuntu) with: ls -la /dev/disk/by-uuid/
Thank you, Graham, for that tip. I have made a note of it. I also noticed that the submitted patch (attachment 2791 ) uses HAL, which has been removed from at least some common Linux distros (Ubuntu etc.). I hope that an improved version of the submitted patch will still be added to Xfce, since: (a) the script as offered by Graham is a workaround that people shouldn't have to do, and (b) some systems (including that of my user who is affected by this) include external drives that could be re-partitioned or replaced by other drives that have a different UUID, and the script would have to be changed manually to match.
This issue is still present in XFCE 4.10 (Xubuntu 12.10). As said in comment 3, the icons are on the desktop at startup, but the volumes are not mounted (the icons are shaded out).
The following script, adapting the idea from Graph, mounts all the disk partitions that have a label: #!/bin/csh sleep 5 foreach i ( `/bin/ls /dev/disk/by-label` ) /home/local/SoftwareDownloads/thunar-volman-0.8.0/thunar-volman/thunar-volman --device-added /sys/`udevadm info -q path -n /dev/disk/by-label/$i` end This seems to do the right thing for me, but is probably dependent on having precisely the right partitions labelled. It still would be better to have these partitions/volumes mounted at startup in a better way.
I second this. Here is why I need that feature : my backup external disk is always connected to my computer, and backups are scheduled, so everything is automated, and I want to be sure backups are performed, even if I forgot to manually mount the backup disk after start up. Thanks for taking care of it.
Since nearly all other desktop environments will automount external USB drives when the user logs in, I too think this needs to be patched. I had multiple people we support confused by it this week.
-- GitLab Migration Automatic Message -- This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/xfce/thunar-volman/-/issues/1. Please create an account or use an existing account on one of our supported OAuth providers. If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev