Description of problem: By default, when inserting i.e. a flash drive, it will appear in the Thunar device list, but not get mounted right away. There is a 'Mount removable drives when hot-plugged' as well as 'Mount removable media when inserted' in the thunar-volman-settings - not selected by default. However checking these options makes no difference to the behavior, automount does not work. I presume that it is a consequence of this that the 'Browse removable media when inserted' has no effect as well. Version-Release number of selected component (if applicable): thunar-volman-0.8.0-2.fc18.x86_64 Thunar-1.6.1-1.fc18.x86_64 xfce4-session-4.10.0-4.fc18.x86_64 gdm-3.6.2-5.fc18.x86_64 How reproducible: Always Steps to Reproduce: 1. Make a new user with default settings, log-in Xfce 2. Insert a flash drive 3. Open Thunar 4. Click the volume name, you will see that it mounts only at that point 5. Now enable the options in thunar-settings-manager 6. Repeat the actions Actual results: Same - mounting only on accessing the media. Thunar won't open with media contents if Browse... option is checked too. Expected results: Volume mounts on insertion, thunar window opens. Additional info: Related to #834144 - however with default settings, automount is not supposed to work. Also related to the upstream bug 9193 (https://bugzilla.xfce.org/show_bug.cgi?id=9193).
Did you actually enable thunar-volman in Thunar's advanced settings?
Looks like it's enabled by default.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This sure looks like XFCE bug 9193. I had this problem in Fedora 19 and Fedora 20. I applied a variant of the patch suggested in comment 3 for XFCE bug 9193, which "fixed" the problem. I don't think that I can change the version number, though.
It could be. Oddly that bug only seems to affect some small number of users. ;( Did you go with the 5 second timeout there? Does smaller still work?
That bug is timing related, so it may be dependent on a lot of things, particularly having an idle processor ready to run thunar-volman before the other setup is done. This might explain why not everyone sees it, although the bug had been very consistent for me. :-( I have had good results with a 1-second timeout, with absolutely no artifacts in over a month of use, on two separate machines. I mount external disks several times a day, most with two partitions, and the partitions always are automounted after approximately 1 second.
Well, I think it may also be hardware related... ie, some hardware takes a bit to settle. I suppose we could try the 1 second delay, but that sure seems like a nasty hack. ;(
I agree that the delay method is a nasty hack. I hesitate to recommend it as a general solution. The discussion in https://bugzilla.xfce.org/show_bug.cgi?id=9193 appears to point to a better fix, but investigating that fix is beyond my current abilities.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I believe that Thunar 1.6.7 (XFCE 4.12) no longer has this bug. (I don't think that the solution is a good one, but it did "fix" the bug.)
Alright. Please reopen if there's something further to do here.