|
Bugzilla – Full Text Bug Listing |
| Summary: | networkmanager seqfault if HAL stopped | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Danny Al-Gaaf <dalgaaf> |
| Component: | Network | Assignee: | Robert Love <rml> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Blocker | ||
| Priority: | P5 - None | ||
| Version: | Alpha 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | strace | ||
|
Description
Danny Al-Gaaf
2005-11-17 14:19:43 UTC
Danny, can you please try with the updated packages which can be found at [1] and report if you still see NetworkManager segfaulting. [1] http://primates.ximian.com/~rml/networkmanager/RPMS/i386/ I 'can't' install this package. It conflicts with dhcpd. And it segfault again! NetworkManager does not segfault with a 10.0 and the RPMS mentioned above. Created attachment 57652 [details]
strace
(In reply to comment #4) > NetworkManager does not segfault with a 10.0 and the RPMS mentioned above. This is wrong. HAL crashed and remained in state D. With a sane HAL, NM does crash on 10.0, too. See bug #134187 *** This bug has been marked as a duplicate of 134187 *** Are you sure that this is a problem with dbus? This happen if you stop only HAL and also other HAL using applications survive this. I believe the uniqueness of NM is that it sends messages _to_ HAL, and thus libdbus to segfaults. Applications that just sit and wait for messages from HAL are fine, because HAL restarting results in simply nothing happening. In this case NM should maybe check if dbus or hal is running (not sure, but IMO there is a message if dbus stop) befor send a message. There would still be a race in between that check and the part of libdbus that segfaults, though. |