Launchpad has imported 19 comments from the remote bug at https://bugzilla.xfce.org/show_bug.cgi?id=9193.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-08-09T23:07:17+00:00 Vaxon77 wrote: I have "Mount removable drives when hot-plugged" option enabled. However, thunar-volman fails to mount any removable media. I've made the following script as a workaround for the issue: cat /usr/local/bin/thunar-volman #!/bin/sh sleep 1 exec /usr/bin/thunar-volman $@ >/tmp/thunar-volman.log 2>&1 Mount succeeds if thunar-volman is started after a small delay. If I comment "#sleep 1", mount fails and the output of /tmp/thunar-volman.log looks as follows: cat /tmp/thunar-volman.log thunar-volman: Could not detect the volume corresponding to the device. /usr/bin/thunar-volman --version thunar-volman 0.8.0 (Xfce 4.10) Copyright (c) 2004-2007 Benedikt Meurer <be...@xfce.org> Copyright (c) 2010-2011 Jannis Pohlmann <jan...@xfce.org> All rights reserved. Please report bugs to <http://bugzilla.xfce.org/>. Thanks, Val. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/0 ------------------------------------------------------------------------ On 2012-08-10T13:16:39+00:00 Vaxon77 wrote: The problem seems to be in the inconsitency between thunar and thunar- volman. Thunar seems to be using UDEV events to detect device add/remove, while thunar-volman uses GVolumeMonitor to find a volume corresponding to the added device and mount it. The problem is gvolume monitor has not set-up the new device volume by the time thunar-volman is started. Obviously UDEV events are emitted first and there's no guarantee GVolumeMonitor manages to set up a volume fast enough for thunar-volman to use it. I'm not thunar expert, but probably the best way to fix it would be to use the the same event monitoring mechanism in both thunar and thunar- volman. For example, if thunar started thunar-volman based on GVolumeMonitor "volume-added" events AOT UDEV device add events, thunar- volman would detect the volume and mount it without any problems. Thanks, Val. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/1 ------------------------------------------------------------------------ On 2012-08-29T16:52:13+00:00 Mati86dl wrote: Confirm it. Inspire in thunar-volman code now try to add support to remobable devices in pragha, and I found this problem. Now I did a quick test, and adding a sleep (5) before tvm_g_volume_monitor_get_volume_for_kind, solves all the problems. ONLY A TEST!. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/2 ------------------------------------------------------------------------ On 2012-08-29T18:14:52+00:00 Mati86dl wrote: Created attachment 4608 Mount devices with a timeout of 5 seconds. Tested in Fedora 17 with xfce 4.10. Only wait 5 seconds to make sure that glib detect the volume. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/3 ------------------------------------------------------------------------ On 2012-11-01T20:13:26+00:00 Andriy Yurchuk wrote: Auto-mounting worked fine in 4.8. What has changed since then? Maybe Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/4 ------------------------------------------------------------------------ On 2013-02-27T06:06:22+00:00 Peter F. Patel-Schneider wrote: Adding a sleep at the beginning of twm_block_device_mount doesn't work for me. However, adding a sleep in main() does. Further, adding a loop inside twm_block_device_mount with a sleep and retry of the tvm_g_volume_monitor_get_volume_for_kind doesn't help at all, even when the total delay runs into several minutes, and even when a new volume monitor is created. I find this very strange - it is almost as if the contents of the volume monitor are fixed at thread invocation time and can't change thereafter. There is something about volume monitor not being thread-safe, but I don't understand just what this means. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/5 ------------------------------------------------------------------------ On 2013-04-01T18:50:58+00:00 Philipp wrote: I have the same problem in Xubuntu 12.10 with XFCE 4.10. With the workaround it seems to work now. Thanks to vaxon77 Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/6 ------------------------------------------------------------------------ On 2013-06-08T07:21:38+00:00 programmist11180 wrote: Debian Wheezy, XFCE 4.10. When gvfs 1.16 and udisks2 2.1 is installed, Thunar mounts cd/dvd only if xfburn is launched. Mounts work normal with gvfs 1.12 and udisks 1.0.4 Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/7 ------------------------------------------------------------------------ On 2013-06-29T00:12:25+00:00 Alexander wrote: (In reply to programmist11180 from comment #7) > Debian Wheezy, XFCE 4.10. When gvfs 1.16 and udisks2 2.1 is installed, > Thunar mounts cd/dvd only if xfburn is launched. Mounts work normal with > gvfs 1.12 and udisks 1.0.4 I have experienced the same problem with the software you mentioned. Also, I couldn't mount my android phone to. When I've downgraded gvfs and udisks to debian's 'stable' branch, i.e. gvfs 1.12 and udisk 1.0.4, I've got automount worked both for cd/dvd and android phone. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/8 ------------------------------------------------------------------------ On 2013-11-13T19:40:46+00:00 Peter F. Patel-Schneider wrote: Is there any further investigation of this problem? Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/9 ------------------------------------------------------------------------ On 2013-11-30T07:30:46+00:00 programmist11180 wrote: The problem remains when using gvfs of version 1.18.2-2 Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/10 ------------------------------------------------------------------------ On 2013-11-30T07:48:07+00:00 Peter F. Patel-Schneider wrote: I compiled the patch in comment 3, which appears to fix the problem, at the cost of a delay in mounting. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/11 ------------------------------------------------------------------------ On 2014-01-19T14:39:31+00:00 programmist11180 wrote: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725978 CD/DVD/ any optical disk mount can be broken by udisks2. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/12 ------------------------------------------------------------------------ On 2014-01-19T14:45:49+00:00 programmist11180 wrote: Also see https://bugs.freedesktop.org/show_bug.cgi?id=69825 Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/13 ------------------------------------------------------------------------ On 2014-02-23T14:32:16+00:00 programmist11180 wrote: A simple way to fix CD/DVD mount and others with udisks2: add to /etc/rc.local: echo 2000 > /sys/module/block/parameters/events_dfl_poll_msecs and reboot (Or, if you don't want to reboot now, you can execute this command from the root). See for more details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725978 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713877 Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/14 ------------------------------------------------------------------------ On 2014-03-03T17:15:46+00:00 Alejandro Perez wrote: I have the exact same problem, that gets fixed either with the script or the patch (setting it to 1s, instead of 5s). Please, fix this issue :) Besides, I detected that thunar needs to be running, either as a daemon or a window open. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/15 ------------------------------------------------------------------------ On 2014-04-18T10:21:28+00:00 P-willaime wrote: I'm also affected by this bug. Why nobody fix thunar-volman? The bug report is open since 2012.... Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/16 ------------------------------------------------------------------------ On 2014-04-18T10:23:34+00:00 Alejandro Perez wrote: I desisted and started using udiskie instead. Never had a problem again. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/17 ------------------------------------------------------------------------ On 2014-04-22T03:56:59+00:00 adam jvok wrote: Still a problem $ thunar-volman -V thunar-volman 0.8.0 (Xfce 4.10) $ thunar -V Thunar 1.6.3 (Xfce 4.10) Please fix. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar- volman/+bug/1312641/comments/18 ** Changed in: thunar-volman Status: Unknown => Confirmed ** Changed in: thunar-volman Importance: Unknown => Medium ** Bug watch added: Debian Bug tracker #725978 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725978 ** Bug watch added: freedesktop.org Bugzilla #69825 https://bugs.freedesktop.org/show_bug.cgi?id=69825 ** Bug watch added: Debian Bug tracker #713877 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713877 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312641 Title: Removable drives and media do not automatically mounted at boot To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1312641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
