nm-applet crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
New install of Ubuntu (12.04 LTS) on Centrinio notebook. On firt access of System Settings -> Network -> Wireless, I seelcted my WAP SSID and clicked on Configure. I got a "nm-applet" closed unexpectedly.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: network-
ProcVersionSign
Uname: Linux 3.2.0-15-
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Tue Feb 14 17:37:49 2012
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
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.103 metric 1
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
8417group a7bdcea4-
Wired connection 1 ee75778d-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth1 802-11-wireless disconnected /org/freedeskto
eth0 802-3-ethernet 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 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.