MASTER top-crash - NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()

Bug #435029 reported by Alvin Thompson
320
This bug affects 56 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
High
Alexander Sack

Bug Description

Binary package hint: network-manager

updating system remotely

ProblemType: Crash
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Sep 22 12:14:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.100 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 10.0.0.1 dev wlan0 proto static
NonfreeKernelModules: nvidia
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
SegvAnalysis:
 Segfault happened at: 0x7f91d91fdb26 <nm_settings_connection_interface_emit_updated+38>: cmpq $0x0,0x28(%rax)
 PC (0x7f91d91fdb26) ok
 source "$0x0" ok
 destination "0x28(%rax)" (0x00000028) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 nm_settings_connection_interface_emit_updated ()
 ?? () from /usr/lib/libnm-glib.so.2
 ?? ()
 ?? ()
 ?? () from /usr/lib/libpolkit-gobject-1.so.0
Title: NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups:

Revision history for this message
Alvin Thompson (alvint-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:nm_settings_connection_interface_emit_updated (
update (connection=0x2, callback=0, user_data=0x0)
update (connection=0x9b8140,
pk_update_cb (object=<value optimized out>,
generic_async_callback (source_object=0x9af0f0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in network-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Alexander Sack (asac) wrote : Re: NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()

could you please check whether its fixed in latest trunk builds available here: https://edge.launchpad.net/~network-manager/+archive/trunk

thanks!

visibility: private → public
Revision history for this message
Peter B P (peterbp) wrote :

Just tested it - I can assign a DHCP-ID fine, with no crashes and the assigned name persists after startup, so I think it is fixed.

Thanks!

Alexander Sack (asac)
Changed in network-manager (Ubuntu):
assignee: nobody → Alexander Sack (asac)
status: New → Triaged
summary: - NetworkManager crashed with SIGSEGV in
+ MASTER top-crash - NetworkManager crashed with SIGSEGV in
nm_settings_connection_interface_emit_updated()
Changed in network-manager (Ubuntu):
milestone: none → ubuntu-9.10
Revision history for this message
Mike Waters (mikewatersaz) wrote :

ubuntu - 9.10 32bit crashes on altering LAN connection

Revision history for this message
Alexander Sack (asac) wrote :

fixed upstream: 72a98c5b29ef53c054bffc53ee89b9d3b35a520b

Please check the daily ppa builds which already should have this commit: https://edge.launchpad.net/~network-manager/+archive/trunk (well, once todays i386 build has finished).

Changed in network-manager (Ubuntu):
status: Triaged → Fix Committed
importance: Medium → High
Revision history for this message
Jonas Alves (jonasfa) wrote :

NetworkManager crashed after changing "Auto eth0" config to manual

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 435029] Re: MASTER top-crash - NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()

On Fri, Oct 09, 2009 at 06:45:23AM -0000, Jonas Alves wrote:
> NetworkManager crashed after changing "Auto eth0" config to manual

If you can reproduce, consider to verify that this is fixed in latest dailies.

https://edge.launchpad.net/~network-manager/+archive/trunk

Thanks!

 - Alexander

gnufreex (gnufreex)
Changed in network-manager (Ubuntu):
status: Fix Committed → Confirmed
Revision history for this message
Anmar Oueja (anmar) wrote :

I changed my wired connection settings from DHCP to manual. All values where correct. Upon saving the values, NM crashed.

Revision history for this message
Alexander Sack (asac) wrote :

please dont switch thins bug back to confirmed unless you have a crash with exact this backtrace using the latest daily builds.

Changed in network-manager (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package network-manager - 0.8~a~git.20091013t193206.679d548-0ubuntu1

---------------
network-manager (0.8~a~git.20091013t193206.679d548-0ubuntu1) karmic; urgency=low

  * upstream snapshot 2009-10-13 19:32:06 (GMT)
    + 679d548e09a0b58815ca62989627d00e7b8c7d96
    - ppp: add minimal debugging output to the ppp plugin
    - system-settings: fix crash saving default wired connections to backing storage (LP: #435029)
    - sharing: fix sharing after 715ddd2045cf786e6c80e6d3d8617fe70ad24552 (LP: #444756)
    - vpn: clear secrets when the connection fails
  * drop iptables-dev dependency and explicitly set
    --with-iptables=/sbin/iptables for configure
    - update debian/control
    - update debian/rules
  * fix LP: #366525 - network-manager should recommend iptables
    - update debian/control

 -- Alexander Sack <email address hidden> Thu, 15 Oct 2009 00:16:15 +0200

Changed in network-manager (Ubuntu):
status: Fix Committed → Fix Released
Changed in network-manager (Ubuntu):
status: Fix Released → Fix Committed
Revision history for this message
Alexander Sack (asac) wrote :

please stop messing with bug status.

Changed in network-manager (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.