NetworkManager crashed with SIGSEGV in g_main_context_check()

Bug #521211 reported by Tobin Davis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

Was running an installation test on Lucid daily live netbook image for dove (20100211) with network unplugged. Plugged network cable in to report crash with Ubiquity when this crash happened.

ProblemType: Crash
Architecture: armel
Date: Fri Feb 12 15:53:20 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/NetworkManager
IpRoute:
 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.252 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 192.168.0.1 dev eth0 proto static
LiveMediaBuild: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha armel+dove (20100211.1)
Package: network-manager 0.8~rc2-0ubuntu1
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-200.7-dove
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 g_main_context_check () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in g_main_context_check()
Uname: Linux 2.6.32-200-dove armv7l
UserGroups:

Revision history for this message
Tobin Davis (gruemaster) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_main_context_check () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in network-manager (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

update-notifier-common: installed version 0.93, latest version: 0.94
libudev0: installed version 151-2, latest version: 151-3
libgudev-1.0-0: installed version 1:151-2, latest version: 1:151-3
libplymouth2: installed version 0.8.0~-9ubuntu1, latest version: 0.8.0~-10

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-armel-retrace
tags: added: iso-testing
Alexander Sack (asac)
visibility: private → public
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.