nm-applet crashed with SIGABRT in __kernel_vsyscall()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
doin nothing
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: network-
ProcVersionSign
Uname: Linux 3.2.0-6-generic i686
NonfreeKernelMo
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sat Dec 24 17:21:48 2011
DuplicateOf: https:/
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nm-applet
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
IpRoute:
default via 192.168.0.1 dev eth0 proto static
default via 192.168.0.1 dev eth0 metric 100
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.5
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
ProcCmdline: nm-applet
ProcEnviron:
PATH=(custom, 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:
__kernel_vsyscall ()
raise () from /lib/i386-
abort () from /lib/i386-
g_assertion_
g_assertion_
Title: nm-applet crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to precise on 2011-12-14 (11 days ago)
UserGroups: adm admin audio cdrom dialout fax lpadmin netdev plugdev sambashare
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
Wired connection a5d95713-
9zeb b0ce087c-
Ifupdown (eth0) 681b428f-
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.