NetworkManager crashed with SIGABRT in g_assertion_message()

Bug #862052 reported by Till Kamppeter
40
This bug affects 4 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Happened somewhere during the night, while the system was idle.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.1.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
CrashCounter: 1
Date: Thu Sep 29 06:04:56 2011
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IpRoute:
 default via 192.168.178.1 dev eth0 proto static
 169.254.0.0/16 dev eth0 scope link metric 1000
 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.20
 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.24 metric 2
Keyfiles: Error: [Errno 2] No such file or directory
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
Signal: 6
SourcePackage: network-manager
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 nm_dns_manager_remove_ip6_config ()
 ?? ()
 ?? ()
Title: NetworkManager crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to oneiric on 2009-12-18 (649 days ago)
UserGroups:

WifiSyslog: Sep 29 08:10:17 localhost6 wpa_supplicant[1679]: WPA: Group rekeying completed with 00:24:fe:a8:02:61 [GTK=TKIP]

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :
visibility: private → public
Changed in network-manager (Ubuntu):
importance: Undecided → High
milestone: none → ubuntu-11.10
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x4a8468 "update_dns", message=0x7fd4c21826f7 "code should not be reached") at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c:1425
 update_dns (self=<optimized out>, iface=0x2385a20 "wlan0", no_caching=0, error=0x7fff85b3bfc8) at nm-dns-manager.c:624
 nm_dns_manager_remove_ip6_config (mgr=0x2393030, iface=0x2385a20 "wlan0", config=0x2441800) at nm-dns-manager.c:962
 nm_device_set_ip6_config (self=0x2410020, new_config=0x242e5f0, assumed=0, reason=<optimized out>) at nm-device.c:3144
 update_ip6_config_with_dhcp (device=0x2410020, ip6_config=0x242e5f0, reason=0x7fff85b3c0fc) at nm-device.c:1430

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):
importance: High → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

This is perhaps caused by the fix for bug 856333. After the fix for that bug reached my with the updates, I saw in the "route" output that the simple package installation did not set the metrics, so I did "sudo restart network-manager" and this made the metrics getting set. After that, while the system was sitting idle during the night, I got this crash.

Changed in network-manager (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This just looks racy, and a side-effect of the restart, nothing related to the bug that was fixed. I don't think you'd see this again, but just to be certain, it would be helpful if you could include additional information if there is a reliable way to reproduce this bug.

Thanks!

Changed in network-manager (Ubuntu):
assignee: Mathieu Trudel-Lapierre (mathieu-tl) → nobody
status: Confirmed → Incomplete
milestone: ubuntu-11.10 → none
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

It happened to me two other times (see duplicates), but it never happened to anyone else.

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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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