nm-applet crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
the applet has disappeared from the panel even though the network is functioning
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: network-
ProcVersionSign
Uname: Linux 3.2.0-17-generic i686
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Thu Mar 1 11:07:49 2012
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
IpRoute:
default via 192.168.0.254 dev eth3 proto static
169.254.0.0/16 dev eth3 scope link metric 1000
192.168.0.0/24 dev eth3 proto kernel scope link src 192.168.0.5 metric 2
239.255.255.0/24 via 192.168.0.254 dev eth3
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
ProcCmdline: nm-applet
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
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-02-21 (8 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
NO3 64cc268b-
Wired connection 1 90f937b0-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth3 802-11-wireless connected /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.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.