nm-connection-editor crashed with SIGSEGV in g_slist_length()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crashed right after login, after I'd clicked on nm applet icon.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: network-
ProcVersionSign
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelMo
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CRDA: Error: [Errno 2] Adresár alebo súbor neexistuje
Date: Mon Mar 12 20:34:39 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120217)
IpRoute:
default via 192.168.1.1 dev eth1 proto static
169.254.0.0/16 dev eth1 scope link metric 1000
192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.6 metric 2
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f69b5bade90 <g_slist_
PC (0x7f69b5bade90) ok
source "0x8(%rdi)" (0xaaaaaaaaaaaa
destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: network-
Stacktrace:
#0 0x00007f69b5bade90 in g_slist_length () from /lib/x86_
No symbol table info available.
#1 0x0000000000410eca in _start ()
No symbol table info available.
StacktraceTop:
g_slist_length () from /lib/x86_
_start ()
Title: nm-connection-
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
Wired connection 1 83f60220-
microcomp f7e959ae-
zabka-wifi d67ad6df-
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
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 #848332, 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.