NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()

Bug #448775 reported by marquentein
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 tried to set MTU size to 9000 in Network Manager for eth0.

Yes in advance: My network is fully geared towards jumbo frames, and it worked flawlessly in 9.04

ProblemType: Crash
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Sun Oct 11 17:15:52 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 172.27.100.0/27 dev eth0 proto kernel scope link src 172.27.100.26 metric 1
 172.27.100.0/27 dev wlan0 proto kernel scope link src 172.27.100.27 metric 2
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 172.27.100.1 dev eth0 proto static
NonfreeKernelModules: nvidia
Package: network-manager 0.8~a~git.20091005t192303.1d28ad1-0ubuntu2
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SegvAnalysis:
 Segfault happened at: 0x7f3552ae1e96 <nm_settings_connection_interface_emit_updated+38>: cmpq $0x0,0x28(%rax)
 PC (0x7f3552ae1e96) 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-13-generic x86_64
UserGroups:

Revision history for this message
marquentein (marquentein) 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 #435029, 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-amd64-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.