NetworkManager crashed with SIGSEGV in dbus_connection_unregister_object_path()

[Sune Keller]

Binary package hint: network-manager

ran "sudo invoke-rc.d dbus restart" and saw NetworkManager crash, causing among others pidgin to stop responding.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/NetworkManager
Package: network-manager 0.7~~svn20080818t061112+eni0-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/NetworkManager
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 dbus_connection_unregister_object_path ()
 ?? () from /usr/lib/libdbus-glib-1.so.2
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in dbus_connection_unregister_object_path()
Uname: Linux 2.6.26-5-generic i686
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:find_subtree_recurse (subtree=0x0, path=0x9a3bae0,
_dbus_object_tree_unregister_and_unlock (tree=0x9a3b9c8,
dbus_connection_unregister_object_path (
unregister_gobject (connection=0x9a3bc14, dead=0x9a40008)
weak_refs_notify (data=0x9a40b20)

[Jean-Paul (jeanpaul145)]

I have had this problem as well. Ironically, you "have" to send a bugreport using a nonexistent network connection (unless you do what I did, which is kill nm-applet and manually restart the NetworkManager daemon).

[Morten Siebuhr (msiebuhr)]

This happened for me while testing some switches. I set a server on one port and let my laptop do "ping -f SERVER_IP", while moving the network cable from port to port on the switch. After six or seven different ports, it seems NetworkManager became unresponsive - the process was running (as seen with 'ps aux'), though none of the nm-* programs could connect to it.

[Alexander Sack (asac)]

can you still reproduce this issue with 0.7~~svn20080908t183521+eni0-0ubuntu3 ?

[moose (snyderra)]

yep its still there. just did the update and reboot and still have to
restart network manager. see attached syslog. note there are several
restarts in there. look for the last one.

On Mon, Sep 22, 2008 at 6:19 PM, Alexander Sack <email address hidden> wrote:

> can you still reproduce this issue with
> 0.7~~svn20080908t183521+eni0-0ubuntu3 ?
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>
> --
> NetworkManager crashed with SIGSEGV in
> dbus_connection_unregister_object_path()
> https://bugs.launchpad.net/bugs/261808
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[moose (snyderra)]

Two other pieces of information.
This is also present when running alpha6 live cd.
If I boot with the net cable unplugged there are no repeating
"nm_dbus_manager_start_service()" messaged until the net cable is plugged
in, after plug in they start. It appears that it gets an ip address then
drops it, then starts spewing error messages.

On Tue, Sep 23, 2008 at 10:57 AM, Rob Snyder <email address hidden> wrote:

> yep its still there. just did the update and reboot and still have to
> restart network manager. see attached syslog. note there are several
> restarts in there. look for the last one.
>
>
> On Mon, Sep 22, 2008 at 6:19 PM, Alexander Sack <email address hidden> wrote:
>
>> can you still reproduce this issue with
>> 0.7~~svn20080908t183521+eni0-0ubuntu3 ?
>>
>> ** Changed in: network-manager (Ubuntu)
>> Status: New => Incomplete
>>
>> --
>> NetworkManager crashed with SIGSEGV in
>> dbus_connection_unregister_object_path()
>> https://bugs.launchpad.net/bugs/261808
>> You received this bug notification because you are a direct subscriber
>> of a duplicate bug.
>>
>
>

[moose (snyderra)]

I have done more testing and have found the following:
1. Tested live CD on different machine - every thing works as expected.
2. Put a 3com net card in the problem machine - everything works as
expected.

This bug report started as a follow on bug from 256919. the fix to that one
was to upgrade to a new kernel that fixed the driver. I am wondering if the
skge driver is not completely fixed, as it doesn't seem to be interacting
with network-manager nicely.
For example with both net cards in the system, I can unplug from the working
3com and plug into the marvell and then the repeating messages start,
requiring network-manager to be restarted.

here is output from lspci showing the two cards.

00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit
Ethernet Controller (rev 13)
00:0b.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone]
(rev 30)

On Tue, Sep 23, 2008 at 11:12 AM, Rob Snyder <email address hidden> wrote:

> Two other pieces of information.
> This is also present when running alpha6 live cd.
> If I boot with the net cable unplugged there are no repeating
> "nm_dbus_manager_start_service()" messaged until the net cable is plugged
> in, after plug in they start. It appears that it gets an ip address then
> drops it, then starts spewing error messages.
>
>
> On Tue, Sep 23, 2008 at 10:57 AM, Rob Snyder <email address hidden> wrote:
>
>> yep its still there. just did the update and reboot and still have to
>> restart network manager. see attached syslog. note there are several
>> restarts in there. look for the last one.
>>
>>
>> On Mon, Sep 22, 2008 at 6:19 PM, Alexander Sack <email address hidden> wrote:
>>
>>> can you still reproduce this issue with
>>> 0.7~~svn20080908t183521+eni0-0ubuntu3 ?
>>>
>>> ** Changed in: network-manager (Ubuntu)
>>> Status: New => Incomplete
>>>
>>> --
>>> NetworkManager crashed with SIGSEGV in
>>> dbus_connection_unregister_object_path()
>>> https://bugs.launchpad.net/bugs/261808
>>> You received this bug notification because you are a direct subscriber
>>> of a duplicate bug.
>>>
>>
>>
>

[moose (snyderra)]

This is still present in 8.10 beta

[moose (snyderra)]

just updated on 14 Oct. this included a kernel update to 2.6.27-7. the problem is gone. all is working now.