And is your share read-only? That's the issue I'm experiencing with autofs. I'd appreciate it if you could confirm this bug if so.
However, I don't think anyone is now tracking this bug. I added the "affects project" for autofs too late after the relevant gvfs issues were fixed. Combined with this bug report : https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/211631 which outlines how Karmic is unable to shutdown/restart gracefully when samba shares are specified in /etc/fstab, we now have the depressing situation whereby Karmic is unable to automatically create shares to samba. And this bug : https://bugs.edge.launchpad.net/gnome-mount/+bug/388444 which highlights that gvfs shares aren't automatically mounted appears to be dead too. I don't consider gvfs in its current state as much use for a networked PC. My only option at the moment is to consider abandoning samba and implementing NFS instead, although that's not an option I can take at my workplace. I only have Karmic on one of my boxes. If I ever decide to install it beyond that, I'll probably raise additional bugs on this issue. For the moment, I've lost motivation. -- smb: Error while copying file, "Invalid argument" https://bugs.launchpad.net/bugs/393012 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
