nm-connection-editor crashed with SIGSEGV in g_slist_length() when trying to configure openVPN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The error happened when trying to configure openVPN through the network applet manager
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CRDA: Error: [Errno 2] No existe el archivo o el directorio
Date: Thu Sep 22 20:35:20 2011
ExecutablePath: /usr/bin/
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
IpRoute:
default via 192.168.2.10 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.22
Keyfiles: Error: [Errno 2] No existe el archivo o el directorio
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: /usr/bin/
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SegvAnalysis:
Segfault happened at: 0x7fb4bc744be0 <g_slist_
PC (0x7fb4bc744be0) ok
source "0x8(%rdi)" (0xaaaaaaaaaaaa
destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: network-
Stacktrace:
#0 0x00007fb4bc744be0 in g_slist_length () from /lib/x86_
No symbol table info available.
#1 0x00000000004135aa 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 admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu 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.