GNOME Bugzilla – Bug 555067
Drivemount with GIO backend doesn't show cifs entries from fstab
Last modified: 2020-11-06 19:56:52 UTC
After updating to FC10 and gnome 2.24, gnome-applets 2.24, drive mount no longer displays cifs entries from fstab.
This is probably due to moving from GVFS to GIO backend
According to this: http://bugzilla.gnome.org/show_bug.cgi?id=543711#c18 the relevant plugin is needed but it is already installed
Here is a sample entry from fstab:
//192.168.2.50/public /media/DS-Public cifs users,nounix,user=XXXX,pass=YYYY,noauto 0 0
Please note that this also occurs in nautilus (cifs entries dont' appear) after moving to GIO backend in version 2.22.
I've finally gotten onto a network with SMB servers and I can confirm that cifs mounts in /etc/fstab aren't listed by the drivemount applet. No idea about the cause yet.
I can also confirm. gnome-applets 2.24 does not display cifs/smbfs/nfs user mounts.
Also note, If the mount point is inside /media, they will only be displayed in the applet *after* being manually mounted. Once mounted manually, an icon is displayed. Once unmounted the icon is removed again.
This defeats the purpose of having a disk mount applet if they must be mounted manually.
Also, for reference, other users with the same issue.
Confirmed this is happening for NFS shares on Ubuntu 8.10
Well it's been over 3 months since I reported this bug and it's worrying that the cause of it hasn't been found yet.
Just to mention that this bug in drivemount is more general since it affects nautilus also since ver. 2.22 .
Same problem with Disk Mounter 2.26.1 and NFS shares in fstab on Ubuntu 9.04
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.
If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-applets/-/issues/
Thank you for reporting this issue and we are sorry it could not be fixed.