NetworkManager crashed with SIGSEGV in get_active_ap called from nm_device_wifi_periodic_update

Bug #603542 reported by Jānis Kangarooo
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: network-manager

i had vlc open paused DVD video.
then i was away for few minutes and when i came back i got 5 crash reports.
in NM-Aplet i have networks 1 in 1 out
all 5 crashes: bug 603541 bug 603542 bug 603540 bug 603539 bug 603544

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: network-manager 0.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic i686
Architecture: i386
CRDA:
 country DE:
  (2400 - 2483 @ 40), (N/A, 20)
  (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
  (5470 - 5725 @ 40), (N/A, 26), NO-OUTDOOR, DFS
Date: Fri Jul 9 13:37:53 2010
Disassembly: => 0x30: Cannot access memory at address 0x30
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
IpRoute:

Keyfiles: Error: [Errno 2] No such file or directory
ProcCmdline: NetworkManager
ProcCwd: /
ProcEnviron: PATH=(custom, no user)
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SegvAnalysis:
 Segfault happened at: 0x30: Cannot access memory at address 0x30
 PC (0x00000030) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: network-manager
Stacktrace:
 #0 0x00000030 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf95f9a9
StacktraceTop: ?? ()
Title: NetworkManager crashed with SIGSEGV
UserGroups:

Revision history for this message
Jānis Kangarooo (kangarooo) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 get_active_ap (self=<value optimized out>,
 periodic_update (self=0x9c6f0c0) at nm-device-wifi.c:977
 nm_device_wifi_periodic_update (data=0x9c6f0c0)
 g_timeout_dispatch (source=0x9c6e130, callback=0xbf95083a,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in network-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Charlie Kravetz (cjkgeek) wrote : Re: NetworkManager crashed with SIGSEGV

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in network-manager (Ubuntu):
status: New → Triaged
Thomas Hood (jdthood)
summary: - NetworkManager crashed with SIGSEGV
+ NetworkManager crashed with SIGSEGV in get_active_ap called from
+ nm_device_wifi_periodic_update
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.