nm-applet crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The nm-applet crashes when I try to connect to my wifi connection securised with wpa. One way to go throught this bug consists to edit
sudo gedit /etc/network/
and add the line
"
auto eth1
iface eth1 inet dhcp
wpa-ssid Livebox-0000
wpa-psk yourpassword_or_key
"
where eth1 is the name of the wifi connection.
But it is not very convenient...
Juju27
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: network-
ProcVersionSign
Uname: Linux 3.2.0-11-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Fri Jan 27 19:56:41 2012
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.1)
IpRoute:
default via 78.250.127.254 dev eth1 proto static
78.250.0.0/17 dev eth1 proto kernel scope link src 78.250.120.52 metric 2
169.254.0.0/16 dev eth1 scope link metric 1000
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
ProcCmdline: nm-applet
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=fr_LU.UTF-8
RfKill:
1: 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-27 (0 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.