NetworkManager crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
This is from Ubuntu Quantal. The other report is from an earlier version of Ubuntu
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: network-manager 0.9.6.0-0ubuntu4
ProcVersionSign
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Aug 24 07:25:41 2012
ExecutablePath: /usr/sbin/
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
IpRoute:
default via 192.168.1.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.3 metric 9
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
PciNetwork:
ProcCmdline: NetworkManager
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Signal: 6
SourcePackage: network-manager
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
g_assertion_
g_assertion_
?? ()
Title: NetworkManager crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
BeachcomberEast 248d0358-
BeachcomberCentral 1bfe5f44-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless connected /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.6.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 #1030703, 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.