NetworkManager crashed with SIGSEGV in __strcmp_ssse3()

Bug #1002758 reported by Muelli
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

hm. this could well be bug 864795

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.1.90-0ubuntu5.1
ProcVersionSignature: Ubuntu 3.0.0-19.33-generic 3.0.27
Uname: Linux 3.0.0-19-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Tue May 22 10:59:43 2012
ExecutablePath: /usr/sbin/NetworkManager
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110201.2)
IpRoute:
 default via 172.31.0.1 dev eth3 proto static
 169.254.0.0/16 dev eth3 scope link metric 1000
 172.31.0.0/24 dev eth3 proto kernel scope link src 172.31.0.65 metric 1
 172.31.0.0/24 dev wlan0 proto kernel scope link src 172.31.0.63 metric 2
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f4f1301f356 <__strcmp_ssse3+22>: movlpd (%rdi),%xmm1
 PC (0x7f4f1301f356) ok
 source "(%rdi)" (0x0c0281a0) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 __strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:213
 ?? ()
 nm_dhcp_client_start_ip6 ()
 ?? ()
 nm_dhcp_manager_start_ip6 ()
Title: NetworkManager crashed with SIGSEGV in __strcmp_ssse3()
UpgradeStatus: Upgraded to oneiric on 2011-10-17 (217 days ago)
UserGroups:

Revision history for this message
Muelli (ubuntu-bugs-auftrags-killer) 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 #967426, 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.