NetworkManager crashed with SIGSEGV in nm_dhcp_dhclient_escape_duid()

Bug #1158720 reported by Rūdolfs Mazurs
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

When connected to WPA network, shortly established connection and then died, respawned and conntected again, died and so on. During the established connection, it managed to exchange some ping packets.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: network-manager 0.9.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Fri Mar 22 12:56:16 2013
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-01-31 (49 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130131)
IpRoute:
 default via 10.0.0.5 dev wlan0 proto static
 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.179 metric 9
 169.254.0.0/16 dev wlan0 scope link metric 1000
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
 WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=lv_LV.UTF-8
SegvAnalysis:
 Segfault happened at: 0x483549 <nm_dhcp_dhclient_escape_duid+9>: mov 0x8(%rdi),%eax
 PC (0x00483549) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 nm_dhcp_dhclient_escape_duid ()
 ?? ()
 nm_dhcp_client_start_ip6 ()
 ?? ()
 nm_dhcp_manager_start_ip6 ()
Title: NetworkManager crashed with SIGSEGV in nm_dhcp_dhclient_escape_duid()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-03-18T08:57:37.933902
nmcli-con:
 Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9:
 ** (process:7014): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files
 Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
nmcli-dev:
 Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 9:
 ** (process:7011): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Message did not receive a reply (timeout by message bus)
 Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.0 connecting enabled enabled enabled enabled disabled

Revision history for this message
Rūdolfs Mazurs (rudolfs-mazurs) 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 this software better. This particular crash has already been reported and is a duplicate of bug #1153342, 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.

information type: 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.