There's a hal error if you mount smbfs devices in fstab
Bug #49884 reported by
Nehos
This bug report is a duplicate of:
Bug #44874: auto smbfs mount in /etc/fstab causes hald hang at boot.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hal (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: hal
I had some smbfs partitons in fstab because I wanted them to be mounted at boot time, but first time you reboot the system, after login in GDM apears an error that says HAL CANNOT START.
I edited /etc/init.d/dbus script saying:
-befor starting umount those partitons.
-after starting mount them.
-befor stopping umount the partitions.
Changed in hal: | |
status: | Unconfirmed → Confirmed |
To post a comment you must log in.
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 forum.ubuntuuse rs.de/topic/ 34522/? highlight= hal (sorry, it's german) interfaces: pre-up sleep 5
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://
may give a hint to the solution:
Put this into /etc/network/
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.