NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
just tried to set up fixed ip &dns
ProblemType: Crash
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Wed Oct 7 17:59:32 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/
Gconf:
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.11 metric 1
169.254.0.0/16 dev eth0 scope link metric 1000
default via 192.168.0.1 dev eth0 proto static
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
Package: network-manager 0.8~a~git.
PciNetwork:
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
RfKill:
SegvAnalysis:
Segfault happened at: 0x7f2860 <nm_settings_
PC (0x007f2860) ok
source "0x14(%eax)" (0x00000014) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
nm_settings_
?? () from /usr/lib/
?? ()
nm_settings_
?? ()
Title: NetworkManager crashed with SIGSEGV in nm_settings_
Uname: Linux 2.6.31-12-generic i686
UserGroups:
This crash has the same stack trace characteristics as bug #430781. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.