gvfsd-trash probes devices not in /run/media, keeping the device busy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs |
Unknown
|
Medium
|
|||
gvfs (Ubuntu) |
Incomplete
|
Low
|
Unassigned |
Bug Description
Right now, if you mount a loop device on Ubuntu Precise, gvfs-gdu-
Ubuntu has a setting which should disable this automount behavior, but it doesn't work: I tried setting System Settings -> Details -> Removable Media -> Never prompt or start programs on media insertion, but gvfs-gdu-
With the attached script (gvfs-test.sh), it fails with the following message:
+ sudo bash -c 'mount /dev/loop0 /tmp/tmp.
umount: /tmp/tmp.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
Killing gvfs-gdu-
There are two related bugs here:
1) gvfs-gdu-
2) It should be possible to disable the automount behavior of gvfs-gdu-
Changed in gvfs (Ubuntu): | |
status: | New → Confirmed |
Changed in gvfs (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in gvfs: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in gvfs: | |
status: | New → Unknown |
Changed in gvfs (Ubuntu): | |
status: | Triaged → Incomplete |
assignee: | Martin Pitt (pitti) → nobody |
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.