NetworkManager crashed on login
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This occurred when logging in after a graphics driver crashed led to a forced restart.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: network-manager 0.9.8.0-0ubuntu21
ProcVersionSign
Uname: Linux 3.11.0-11-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Oct 8 20:55:02 2013
ExecutablePath: /usr/sbin/
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-10-05 (3 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131005)
IpRoute:
default via 67.194.0.1 dev eth1 proto static
67.194.0.0/17 dev eth1 proto kernel scope link src 67.194.3.55 metric 9
MarkForUpload: True
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
Signal: 6
SourcePackage: network-manager
StacktraceTop:
?? () from /lib/x86_
g_assertion_
g_assertion_
?? ()
?? ()
Title: NetworkManager crashed with SIGABRT in g_assertion_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
Wired connection 1 36cbf1bf-
MGuest 6e0c7847-
MWireless 01fe5333-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth1 802-11-wireless connected /org/freedeskto
eth0 802-3-ethernet unavailable /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.8.0 connected enabled enabled enabled enabled disabled
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1197854, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.