NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()

Bug #445625 reported by steve_freeman
114
This bug affects 23 people
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/NetworkManager
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.20091005t192303.1d28ad1-0ubuntu2
PciNetwork:

ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-12.40-generic
RfKill:

SegvAnalysis:
 Segfault happened at: 0x7f2860 <nm_settings_connection_interface_emit_updated+48>: mov 0x14(%eax),%edx
 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_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-12-generic i686
UserGroups:

Revision history for this message
steve_freeman (freemansteve) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

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.

tags: added: regression-retracer
tags: removed: need-i386-retrace
Revision history for this message
Alexander Sack (asac) wrote :

can you reproduce this issue? If so, please verify that its fixed in latest trunk dailies. just enable our PPA and upgrade: https://edge.launchpad.net/~network-manager/+archive/trunk

visibility: private → public
Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Interlith (jason-interlith-deactivatedaccount) wrote : Re: [Bug 445625] Re: NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()

Downloaded updates, problem seems to be fixed. I will test some more but
I consider this closed.

Thank you

Jason

Alexander Sack wrote:
> can you reproduce this issue? If so, please verify that its fixed in
> latest trunk dailies. just enable our PPA and upgrade:
> https://edge.launchpad.net/~network-manager/+archive/trunk
>
> ** Attachment removed: "CoreDump.gz"
> http://launchpadlibrarian.net/33239376/CoreDump.gz
>
> ** Visibility changed to: Public
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>
>

Revision history for this message
lakiu (lakiu-deactivatedaccount-deactivatedaccount) wrote :

Every time I try to change any setting in Network Manager, it crashes. Both on my desktop and sub-notebook.

My systems are up to date.

Changed in network-manager (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
technoshaun (shaun-marolf) wrote :

Same issue editing a connection causes a crash

Revision history for this message
lakiu (lakiu-deactivatedaccount-deactivatedaccount) wrote :

Even after adding daily trunk repository and updating network manager, it still crashes.

Revision history for this message
lakiu (lakiu-deactivatedaccount-deactivatedaccount) wrote :

Version 0.9 from latest trunk dailies fixes the issue for me.
FInally!

Changed in network-manager (Ubuntu):
status: Confirmed → Fix Released
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.