HAL crashes with generated smb.conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gsambad (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
hal (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: samba
Yesterday I installed and ran gsambad to configure my samba shares. It was a bit more complicated than expected, so I didn't complete the configuration. But from the time the new smb.conf was written, the HAL stopped working:
- Nautilus crashed constantly
- When I restarted I got a message "Failed to initialize HAL"
At first, I didn't expect that this was caused by the new smb.conf and tried reconfiguring HAL, restarting HAL and so on. Without success. After 2 hours I did a dpkg-reconfigure samba and everything was fixed.
I think it shouldn't be possible to crash the HAL via smb.conf :-)
(I'm not sure whether this is a bug in samba in HAL...)
Hardy Heron,
samba 3.0.28a-1ubuntu4.1
hal 0.5.11~
affects: | samba (Ubuntu) → gsambad (Ubuntu) |
Changed in hal (Ubuntu): | |
status: | New → Incomplete |
Do you use winbind (or likewise) on this system?
If not, I can't see any way that a problematic smb.conf *could* crash hal.