NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()

Bug #432101 reported by Shane Synan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

I edited the name for my Ethernet (eth0 interface) in the connection editor, and after clicking Apply and providing credentials, the Apport icon appeared in the taskbar.
The changed name saved, but I had to close and reopen the Edit Connections window to continue editing anything since a duplicate of "Home Ethernet" appeared.

ProblemType: Crash
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Thu Sep 17 15:20:06 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 10.0.2.2 dev eth0 proto static
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Package: network-manager 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
RfKill:

SegvAnalysis:
 Segfault happened at: 0xf903c0 <nm_settings_connection_interface_emit_updated+48>: mov 0x14(%eax),%edx
 PC (0x00f903c0) 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_connection_interface_emit_updated ()
 ?? () from /usr/lib/libnm-glib.so.2
 ?? ()
 nm_settings_connection_interface_update ()
 ?? ()
Title: NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()
Uname: Linux 2.6.31-10-generic i686
UserGroups:

Revision history for this message
Shane Synan (digitalcircuit) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #430781, 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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.