NetworkManager crashed with SIGSEGV in g_datalist_id_set_data_full()

Bug #278574 reported by dwp0980
6
Affects Status Importance Assigned to Milestone
NetworkManager
Invalid
Undecided
Unassigned
network-manager (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: network-manager

Crash on startup

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Disassembly: 0xc2:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
NonfreeKernelModules: nvidia
Package: network-manager 0.7~~svn20080928t225540+eni0-0ubuntu2
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:
 ?? ()
 g_datalist_id_set_data_full ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in g_datalist_id_set_data_full()
Uname: Linux 2.6.27-4-generic i686
UserGroups:

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

StacktraceTop:?? ()
IA__g_datalist_id_set_data_full (datalist=0x907d2f0,
g_object_real_dispose (object=0x907d2e8)
dbus_g_proxy_dispose (object=0x907d2e8) at dbus-gproxy.c:1485
IA__g_object_unref (_object=0x907d2e8)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Alexander Sack (asac) wrote :

appears to be leaked/not-cancelled callback in nm-supplicant-interface.c:411. apparently multi calls can be added, but only one will be remembered/removed.

Fix should track calls in a GSList and instead of removing just info->call, remove all active calls in that list. When a call succeeds it should be removed from GSList too.

Changed in network-manager:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Thomas Hood (jdthood) wrote :

Has anyone seen this bug in Precise or Quantal?

Changed in network-manager (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

This bug was marked Incomplete some time ago and was supposed to autoclose after 90 days. I'm going to close it manually due to no activity (and likely the issue has gone away/been fixed).

Changed in network-manager (Ubuntu):
status: Incomplete → Invalid
Changed in network-manager:
status: New → Invalid
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.