nm-applet crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
apt-cache policy network-manager
network-manager:
Installed: 0.9.2.0+
Candidate: 0.9.2.0+
Version table:
*** 0.9.2.0+
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: network-
ProcVersionSign
Uname: Linux 3.2.0-6-generic i686
NonfreeKernelMo
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Wed Feb 15 14:11:18 2012
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
IpRoute:
default via 192.168.0.1 dev eth1 proto static
169.254.0.0/16 dev eth1 scope link metric 1000
192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.5 metric 2
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 2012-01-29 (17 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet unavailable /org/freedeskto
eth1 802-11-wireless connected /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 enabled
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.