NetworkManager crashed with SIGSEGV in g_object_newv()

Bug #308928 reported by Michael
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: network-manager

This happened shortly after restarting hal to get rid of duplicate entries in nm-applet. See https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/262974.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
NonfreeKernelModules: nvidia
Package: network-manager 0.7~~svn20081018t105859-0ubuntu1.8.10.1
ProcAttrCurrent: unconfined
ProcCmdline: NetworkManager
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist ()
 g_object_new () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libdbus-glib-1.so.2
 ?? ()
Title: NetworkManager crashed with SIGSEGV in g_object_newv()
Uname: Linux 2.6.27-9-generic x86_64
UserGroups:

Revision history for this message
Michael (michaeljt) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:g_object_newv () from /usr/lib/libgobject-2.0.so.0
g_object_new_valist ()
g_object_new () from /usr/lib/libgobject-2.0.so.0
dbus_g_proxy_new (connection=0xd44c98,
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Do you get the same with Karmic? Thanks in advance.

Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Michael (michaeljt) wrote :

I no longer see this bug, as it was the consequence of having to restart hal to work around a bug in DKMS. That bug is now fixed though, and the workaround is no longer needed. From my point of view this can be closed, although of course unless someone has actually fixed whatever bug caused the segfault, it is still probably lurking.

Revision history for this message
Saravanan Thirumuruganathan (saravanan-thirumuruganathan) wrote :

Hello,

I had updated to Lucid Beta 1 from Karmic. This issue occured when I booted the machine. My system is fully patched and has all the latest updates.

Revision history for this message
Saravanan Thirumuruganathan (saravanan-thirumuruganathan) wrote :

Probably my logs might have been different from Michael's - but since I said the problem is similar it did not upload my log files. Is there any way for me to collect it and upload it here ?

Also I am changing the status from Incomplete -> New .

Changed in network-manager (Ubuntu):
status: Incomplete → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Is this still an issue the latest comment here is from 2010, may you please check again and comment back? Thanks in advance.

Changed in network-manager (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Michael (michaeljt) wrote :

Not for me. Anyone who is still affected please post a comment.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.