network manager crashed when changing IP to static IP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I opened network manager and went to change the configuration for "Wired connection 1". I changed the name of it to "Wired connection" and then changed it from DHCP to a static IP. Once I clicked "Save" network manager crashed.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-10-generic i686
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Sep 6 20:44:40 2011
ExecutablePath: /usr/sbin/
Gconf:
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
IpRoute:
default via 192.168.1.1 dev eth0 proto static
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.3
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
Keyfiles: Error: [Errno 2] No such file or directory
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SegvAnalysis:
Segfault happened at: 0x1446f2 <g_type_
PC (0x001446f2) ok
source "(%edx)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
destination "%ecx" ok
SegvReason: reading 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.