Public bug reported:
Binary package hint: samba-common
For years, I have mounted a samba share located on my server by using
fstab entries, such as:
//serverip/share /local/mount/point smbfs
username=myuser,password=mypassword,user,rw,auto,fmask=0777,dmask=0777,uid=myuser,gid=mygroup
0 0
This works fine on other linux distributions and it worked fine in
Feisty as well. However, in Gutsy, this causes a hang when first
logging into GNOME. I can log in to GDM, no problem, but then as GNOME
is loading, things slow down and the wallpaper I use, which is on this
samba share, does not load. The nautilus desktop remains black.
Eventually, I can access the desktop (sans wallpaper) and the share is
not mounted. I tried changing the /etc/fstab line to use "cifs" since I
know smbfs is deprecated and there is no difference.
When I comment out that line in /etc/fstab and reboot, everything comes
right up nice and quick. I can then manually uncomment that line in
/etc/fstab, run "sudo mount -a" and the share mounts fine.
So, Samba mounting via /etc/fstab works in general when done manually,
but it is has problems mounting at boot when this line is enabled in
/etc/fstab
Possibly related, possibly not: I see network manager errors when I log
out of GNOME and GDM. Perhaps network manager is not coming up in time
for the samba share to mount? Just a guess. I am thinking about
removing network manager and manually setting a static ip in
/etc/network/interfaces to see if that changes anything. This is a
desktop system that does not go anywhere so I don't really need the
autoconfiguration capabilities of network-manager.
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Binary package hint: samba-common
For years, I have mounted a samba share located on my server by using
fstab entries, such as:
//serverip/share /local/mount/point smbfs
username=myuser,password=mypassword,user,rw,auto,fmask=0777,dmask=0777,uid=myuser,gid=mygroup
0 0
This works fine on other linux distributions and it worked fine in
Feisty as well. However, in Gutsy, this causes a hang when first
logging into GNOME. I can log in to GDM, no problem, but then as GNOME
is loading, things slow down and the wallpaper I use, which is on this
samba share, does not load. The nautilus desktop remains black.
Eventually, I can access the desktop (sans wallpaper) and the share is
not mounted. I tried changing the /etc/fstab line to use "cifs" since I
know smbfs is deprecated and there is no difference.
When I comment out that line in /etc/fstab and reboot, everything comes
right up nice and quick. I can then manually uncomment that line in
- /etc/fstab, run "sudo mount-a" and the share mounts fine.
+ /etc/fstab, run "sudo mount -a" and the share mounts fine.
So, Samba mounting via /etc/fstab works in general when done manually,
but it is has problems mounting at boot when this line is enabled in
/etc/fstab
Possibly related, possibly not: I see network manager errors when I log
out of GNOME and GDM. Perhaps network manager is not coming up in time
for the samba share to mount? Just a guess. I am thinking about
removing network manager and manually setting a static ip in
/etc/network/interfaces to see if that changes anything. This is a
desktop system that does not go anywhere so I don't really need the
autoconfiguration capabilities of network-manager.
--
samba/smb/cifs shares in /etc/fstab do not auto-mount on boot
https://bugs.launchpad.net/bugs/163174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
