HAL crashes with generated smb.conf

Bug #239947 reported by Daniel Fett on 2008-06-14
6
Affects Status Importance Assigned to Milestone
gsambad (Ubuntu)
Undecided
Unassigned
hal (Ubuntu)
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~rc2-1ubuntu8.1

Daniel Fett (fett-ubuntu) wrote :
Steve Langasek (vorlon) wrote :

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.

Changed in samba:
status: New → Incomplete
Daniel Fett (fett-ubuntu) wrote :

Indeed, winbind is installed and running. I'm not sure why it is installed, but it is.

Chuck Short (zulcss) wrote :

Hi,

I was wondering if this is still a problem for you?

Thanks
chuck

Chuck Short (zulcss) on 2009-11-23
affects: samba (Ubuntu) → gsambad (Ubuntu)
Changed in hal (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for gsambad (Ubuntu) because there has been no activity for 60 days.]

Changed in gsambad (Ubuntu):
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

[Expired for hal (Ubuntu) because there has been no activity for 60 days.]

Changed in hal (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers