NetworkManager crashed with SIGSEGV in nm_ip4_config_diff()

Bug #909099 reported by Muelli on 2011-12-27
This bug affects 3 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)

Bug Description

dunno, didn't do anything special

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Dec 27 19:14:16 2011
ExecutablePath: /usr/sbin/NetworkManager

InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110201.2)
 default via dev wlan0 proto static dev wlan0 scope link metric 1000 dev wlan0 proto kernel scope link src metric 2
Keyfiles: Error: [Errno 2] No such file or directory
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
 Segfault happened at: 0x44274d <nm_ip4_config_diff+173>: mov 0x8(%rbp),%rdi
 PC (0x0044274d) ok
 source "0x8(%rbp)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
 nm_ip4_config_diff ()
 ?? ()
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/
Title: NetworkManager crashed with SIGSEGV in nm_ip4_config_diff()
UpgradeStatus: Upgraded to oneiric on 2011-10-17 (71 days ago)

visibility: private → public

 nm_ip4_config_diff (a=<optimized out>, b=0x8a2580) at nm-ip4-config.c:753
 nm_device_set_ip4_config (self=0x808390, new_config=0x8a2580, assumed=0, reason=<optimized out>) at nm-device.c:3032
 nm_device_activate_stage5_ip_config_commit (user_data=<optimized out>) at nm-device.c:2642
 nm_device_activate_stage4_ip6_config_get (user_data=<optimized out>) at nm-device.c:2339
 g_timeout_source_new_seconds (interval=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3969

Changed in network-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers