nm-applet crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
NM Applet crashes. I can go into System Settings -> Network and connect to an unsecured Wireless network there, however I cannot connect to any secured wireless networks from that interface.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: network-
ProcVersionSign
Uname: Linux 3.2.0-17-
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Fri Mar 2 21:00:18 2012
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
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.12 metric 2
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: nm-applet
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
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-dev:
DEVICE TYPE STATE DBUS-PATH
eth1 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 disabled
visibility: | private → public |
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.