NetworkManager crashed with SIGSEGV

[Jānis Kangarooo]

Binary package hint: network-manager

nothing crashed but crash came up

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:

[Apport retracing service (apport)]

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,

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 603542, so it 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.