Package: gvfs Version: 1.6.4-3 Severity: normal Tags: upstream Hi,
cifs mounts specified in /etc/fstab appear twice in the nautilus sidebar. For example # Network drives //host/share /home/user/share cifs rw,user=username,credentials=/root/.smbcredentials,iocharset=utf8,sec=ntlmv2,uid=user,gid=user,file_mode=0644,dir_mode=0755 0 0 In the nautilus sidbar clicking on the surplus item (removable drive icon) gives the error message: Unable to mount share mount: according to mtab, //host/share/ is already mounted on /home/user/share mount failed clicking on the first item (disk drive icon) opens up the folder. I've also mounted the same data share using NFS and sshfs methods. There I only see the disk drive icon as it should be so the problem is related only to cifs mounts. I don't know how to debug this problem further. I found gvfs bug reports (#442130, #444500) describing I think the same problem, but no solution offered. Thank you very much. -- System Information: Debian Release: 6.0 APT prefers squeeze-updates APT policy: (500, 'squeeze-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gvfs depends on: ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libdbus-1-3 1.2.24-4 simple interprocess messaging syst ii libexpat1 2.0.1-7 XML parsing C library - runtime li ii libgconf2-4 2.28.1-6 GNOME configuration database syste ii libgdu0 2.30.1-2 GObject based Disk Utility Library ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgnome-keyring0 2.30.1-1 GNOME keyring services library ii libudev0 164-3 libudev shared library ii x11-utils 7.5+4 X11 utilities Versions of packages gvfs recommends: ii dbus 1.2.24-4 simple interprocess messaging syst ii policykit-1-gnome 0.96-3 GNOME authentication agent for Pol Versions of packages gvfs suggests: ii gvfs-backends 1.6.4-3 userspace virtual filesystem - bac -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
