I can confirm that this bug occurs whenever someone tries to mount an smb filesystem by using smbfs via a fstab entry (dapper). Several side effects result from that like hanging nautilus processes, missing samba shares, performance lags in nautilus. Here's a workaround: Mount the samba shares by writing the mount command(s) into /etc/rc.local like this:
mount -t smbfs -o <options> //server/share /directory/mountpoint <options> are the same stuff as in fstab: uid, gid, credentials, fmask, dmask and - if you lock rc.local away from the rest of the world - username and password. This will do the same job as an entry in fstab but it will do it after HAL has been started. Another workaround mentioned here: http://forum.ubuntuusers.de/topic/34522/?highlight=hal (sorry, it's german) may give a hint to the solution: Put this into /etc/network/interfaces: pre-up sleep 5 It seems that this is a problem of time: HAL tries to initialize, does this obviously in the background while the boot process is going on with the initialization of network devices like samba shares. Looks like samba is getting into conflict with HAL at that point. -- There's a hal error if you mount smbfs devices in fstab https://launchpad.net/bugs/49884 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
