Nope, it does not seem so.
As for the labelled partitions (#442130): [cite]a workaround is to specify the
partitions by /dev/sdXXX[/cite];
and here with cifs mounts, the only way to get the duplicates off is not to
specify them at all.
BTW. There is a step up in Natty: one record in fstab
dupe of bug #442130 ?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/444500
Title:
smb shares listed twice
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I have the same problem in Maverick, if I mount the share using fstab entry I
get two icons in Places (but with different icons) on of them has no umount
icon and doesn't work giving error accessing the .smbcredentials and the second
works well:
//server/sharefolder/media/sharefolder cifs
In Maverick I do still see 2 entries for my CIFS mounted devices.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/444500
Title:
smb shares listed twice
--
desktop-bugs mailing list
Thank you for taking the time to report this bug and helping to make
Ubuntu better. A new version of GVFS is available on Maverick and we are
wondering if this bug is still an issue for you with that version? Could
you please test and comment back? Thanks in advance.
** Changed in: gvfs (Ubuntu)
I have two shares mounted in /etc/fstab:
//server/alex /home/alex-server cifs
users,credentials=/home/alex/.smbcredentials,user=alex,iocharset=utf8,file_mode=0700,dir_mode=0700,uid=alex,gid=alex,auto
//server/server /home/server cifs
** Summary changed:
- [karmic] smb shares listed twice
+ smb shares listed twice
--
smb shares listed twice
https://bugs.launchpad.net/bugs/444500
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs
Several minutes after mounting (see previous message) I got messages:
DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
Thank you for your bug report. The issue is an upstream one and it would
be nice if somebody having it could send the bug the to the people
writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)
** Package changed: nautilus (Ubuntu) = gvfs (Ubuntu)
** Changed in: gvfs (Ubuntu)
