Regression: USB removable storage devices listed in fstab no longer show in "Computer"

Bug #229370 reported by Oded Arbel
6
Affects Status Importance Assigned to Milestone
gvfs
Fix Released
Medium
gvfs (Debian)
Fix Released
Unknown
gvfs (Ubuntu)
Triaged
Low
Unassigned

Bug Description

On my system I have an external hard drive connected through USB, that has an entry in /etc/fstab setup so that it always mounts in a specified location. It is setup with "users,noauto" so that users can mount it - as it has a FAT32 file system, the mounting user has full access to the drive for the duration of the mount to the exclusion of other users.

In Gutsy (7.10) this setup was very useful - users had an icon for the drive under "Places"->"Computer" or on their desktop and could mount and unmount the drive easily. Since the upgrade to Hardy the device no longer appears in either "Computer" or desktops. After commenting out the fstab entry and re-logging in, the drive now appears but when accessing it it mounts under /media/PRODUCT-NAME instead of where I need it to go.

Revision history for this message
jtniehof (jtniehof) wrote :

I have the same symptoms in 9.10, nautilus version 2.28.1-0ubuntu3
(Changing package to nautilus because the symptom manifests there.)

affects: hal (Ubuntu) → nautilus (Ubuntu)
Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Sense Egbert Hofstede (sense) wrote :

Thank you for helping with making Ubuntu better by reporting this bug.
Nautilus gets its information for the devices from Gvfs, which uses DeviceKit. This is most likely a bug in one of the two. However, in order to determine this we first need some more information.
Could you please provide the output of the following commands, attached in separate attachments -- the output is too long for comments.
gvfs-mount -li
devkit-disks --dump
cat /etc/fstab
cat /proc/self/mountinfo

Thanks in advance

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Sense Egbert Hofstede (sense) wrote :

I forgot to mention that when executing those commands you need to have the affected device(s) connected to your system.

Revision history for this message
jtniehof (jtniehof) wrote :
Revision history for this message
jtniehof (jtniehof) wrote :
Revision history for this message
jtniehof (jtniehof) wrote :
Revision history for this message
jtniehof (jtniehof) wrote :
Revision history for this message
jtniehof (jtniehof) wrote :

Logs are attached. Looks like the disk shows up in devkit but not gvfs, so changing the package. Removing the entry from fstab makes it show up in Places; no need to unplug/replug the drive. If I re-add the drive to fstab, without unplugging/replugging the drive, it no longer has an entry in places.

Also found upstream bugs, linking.

affects: nautilus (Ubuntu) → gvfs (Ubuntu)
Changed in gvfs (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Sense Egbert Hofstede (sense) wrote :

Thank you for your input! However, the bugs you've assigned are actually bugs that were already fixed. It could be a bug in the patch that solved GNOME Bug #536292, I'll ask in that bug report for more information.

Changed in gvfs (Ubuntu):
status: Confirmed → Triaged
Changed in gvfs (Debian):
status: Unknown → Confirmed
Changed in gvfs:
importance: Unknown → Medium
status: Unknown → Fix Released
Changed in gvfs (Debian):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.