NetworkManager crashed with SIGSEGV

Bug #352796 reported by josema
14
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

gh

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
Package: network-manager 0.7.1~rc3.2.gitb8fc83a7-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/NetworkManager --pid-file /var/run/NetworkManager/NetworkManager.pid
ProcEnviron: PATH=(custom, no user)
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
Title: NetworkManager crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic i686
UserGroups:

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

StacktraceTop:_dbus_data_slot_list_clear (list=0x9d7d594) at dbus-dataslot.c:334
_dbus_data_slot_list_free (list=0x9d7d594)
_dbus_pending_call_last_unref (pending=0x9d7d590)
g_hash_table_remove_node (hash_table=0x9d60750,
g_hash_table_foreach_remove_or_steal (hash_table=0x9d60750,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Alexander Sack (asac)
visibility: private → public
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
Matthias Metzger (macellarius) wrote :

For me it's solved.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

seems like this is no longer an issue

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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