NetworkManager crashed with SIGABRT in g_assertion_message()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
no se cual es el error por favor ayudenme
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: network-manager 0.9.8.0-0ubuntu18
ProcVersionSign
Uname: Linux 3.10.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
CRDA:
country CO:
(2402 - 2472 @ 40), (3, 27)
(5170 - 5250 @ 40), (3, 17)
(5250 - 5330 @ 40), (3, 23), DFS
(5735 - 5835 @ 40), (3, 30)
Date: Mon Aug 26 08:42:20 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-05-30 (87 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IpRoute:
default via 172.31.1.6 dev wlan0 proto static
172.31.0.0/16 dev wlan0 proto kernel scope link src 172.31.242.77 metric 9
MarkForUpload: True
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron:
LANGUAGE=es_CO:es
TERM=linux
PATH=(custom, no user)
LANG=es_CO.UTF-8
Signal: 6
SourcePackage: network-manager
StacktraceTop:
?? () from /lib/x86_
g_assertion_
g_assertion_
?? ()
?? ()
Title: NetworkManager crashed with SIGABRT in g_assertion_
UpgradeStatus: Upgraded to saucy on 2013-06-03 (84 days ago)
UserGroups:
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless connected /org/freedeskto
wlan1 802-11-wireless disconnected /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.