NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
Not sure what happened. Just saw the notification.
ProblemType: Crash
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Sun Oct 11 09:26:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/
Gconf:
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
10.42.43.0/24 dev eth0 proto kernel scope link src 10.42.43.10 metric 1
169.254.0.0/16 dev eth0 scope link metric 1000
default via 10.42.43.1 dev eth0 proto static
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
pan0 no wireless extensions.
Package: network-manager 0.8~a~git.
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SegvAnalysis:
Segfault happened at: 0xc55860 <nm_settings_
PC (0x00c55860) 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-13-generic i686
UserGroups: mythtv
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 #445625, 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.