NetworkManager crashed with SIGSEGV in g_type_instance_get_private() switching from 1 cabled network configuration to the second cabled network config. After disabling the autoconnect feature
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu oneiric (development branch)
Release: 11.10
network-manager:
Geïnstalleerd: 0.9.0-0ubuntu3
Kandidaat: 0.9.0-0ubuntu3
Versietabel:
*** 0.9.0-0ubuntu3 0
500 http://
100 /var/lib/
It should have disabled network connection 1 and switch to network connection 2.
The application created an error pop up
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.0-0ubuntu3
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CRDA: Error: [Errno 2] Bestand of map bestaat niet
Date: Tue Sep 13 23:09:08 2011
ExecutablePath: /usr/sbin/
Gconf:
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
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.105
IwConfig:
lo no wireless extensions.
eth1 no wireless extensions.
eth0 no wireless extensions.
Keyfiles: Error: [Errno 2] Bestand of map bestaat niet
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
RfKill:
SegvAnalysis:
Segfault happened at: 0x7fd763b87b41 <g_type_
PC (0x7fd763b87b41) ok
source "$0x0" ok
destination "(%rdi)" (0xaaaaaaaaaaaa
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
g_type_
nm_agent_
?? ()
?? ()
?? ()
Title: NetworkManager crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
mtime.conffile.
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 #797868, 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.