NetworkManager crashed with SIGABRT in _g_log_abort()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
on gnome-shell session startup I got this crash reported by apport, anyway this doesn't affect the connection, I only get the error dialog window that asks me if I want to report this issue.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: network-manager 0.9.8.0-0ubuntu22 [modified: usr/bin/nm-online usr/bin/nm-tool usr/bin/nmcli usr/lib/
ProcVersionSign
Uname: Linux 3.11.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Tue Feb 18 06:06:02 2014
ExecutablePath: /usr/sbin/
IpRoute:
default via 192.168.2.1 dev eth0 proto static
192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.103 metric 9
MarkForUpload: True
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=it_IT.UTF-8
Signal: 6
SourcePackage: network-manager
StacktraceTop:
?? () from /lib/x86_
g_assertion_
g_assertion_
nm_manager_new ()
main ()
Title: NetworkManager crashed with SIGABRT in g_assertion_
UpgradeStatus: Upgraded to saucy on 2013-10-17 (127 days ago)
UserGroups:
mtime.conffile.
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-11-wireless connected /org/freedeskto
em1 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 bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.
I'm going to close this bug report as their is nothing else we can do with this old report in a now unsupported version of Ubuntu. If you still have this issue on Ubuntu 14.04 or higher, please do reopen or report a new bug.