Bug 134179 - networkmanager seqfault if HAL stopped
Summary: networkmanager seqfault if HAL stopped
Status: RESOLVED DUPLICATE of bug 134187
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Network (show other bugs)
Version: Alpha 3
Hardware: Other Other
: P5 - None : Blocker (vote)
Target Milestone: ---
Assignee: Robert Love
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-17 14:19 UTC by Danny Al-Gaaf
Modified: 2005-12-08 21:43 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
strace (2.54 KB, application/octet-stream)
2005-11-17 15:15 UTC, Danny Al-Gaaf 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Danny Al-Gaaf 2005-11-17 14:19:43 UTC 
If networkmanager runs and you stop or restart HAL (e.g. for a update) the networkmanager crash with a seqfault.
Comment 1 Timo Hoenig 2005-11-17 14:20:54 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/
Comment 2 Danny Al-Gaaf 2005-11-17 14:41:07 UTC 
I 'can't' install this package. It conflicts with dhcpd.
Comment 3 Danny Al-Gaaf 2005-11-17 14:43:11 UTC 
And it segfault again!
Comment 4 Timo Hoenig 2005-11-17 14:51:39 UTC 
NetworkManager does not segfault with a 10.0 and the RPMS mentioned above.
Comment 5 Danny Al-Gaaf 2005-11-17 15:15:46 UTC 
Created attachment 57652 [details]
strace
Comment 6 Timo Hoenig 2005-11-17 15:45:50 UTC 
(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.
Comment 7 Robert Love 2005-12-08 18:05:00 UTC 
See bug #134187

*** This bug has been marked as a duplicate of 134187 ***
Comment 8 Danny Al-Gaaf 2005-12-08 21:00:26 UTC 
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.
Comment 9 Robert Love 2005-12-08 21:09:35 UTC 
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.
Comment 10 Danny Al-Gaaf 2005-12-08 21:19:18 UTC 
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.
Comment 11 Robert Love 2005-12-08 21:43:42 UTC 
There would still be a race in between that check and the part of libdbus that segfaults, though.