nm-applet crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
néant...
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: network-
ProcVersionSign
Uname: Linux 3.2.0-12-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sun Feb 5 12:35:02 2012
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback mtu 1400
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
IpRoute:
default via 192.168.1.1 dev eth0 proto static
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.198 metric 1
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
ProcCmdline: nm-applet
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Signal: 6
SourcePackage: network-
StacktraceTop:
raise () from /lib/i386-
abort () from /lib/i386-
g_assertion_
g_assertion_
nm_utils_
Title: nm-applet crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2011-12-25 (41 days ago)
UserGroups: adm lpadmin sambashare sudo
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
Auto SFR_E710 95ea7d07-
SFR_E710 7faa93a6-
SFR WiFi Public 9126253c-
Ethernet automatique f326f61b-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet connected /org/freedeskto
eth1 802-11-wireless connecting (getting IP configuration) /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.3.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 #908380, 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.