bluetooth-applet crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()

[Arjen Raateland]

Binary package hint: gnome-bluetooth

I wasn't doing anything related to Bluetooth; I started Ubuntu 11.04 from a USB stick which I have been updating before restarting it. Never have used Bluetooth.
I want the wireless card to work; it still doesn't; very frustrating as it sees all kinds of WLAN's except my own. My other wireless devices work fine and so did this notebook with 10.10 and the old STA driver, except at a low speed of 2Mb/s. I installed the new driver, but it exhibited the same behaviour as above in 11.04.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-bluetooth 2.91.2.is.2.32.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Tue Mar 15 21:10:59 2011
ExecutablePath: /usr/bin/bluetooth-applet
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110315)
ProcCmdline: bluetooth-applet
ProcEnviron:
 LANGUAGE=nl_NL:en
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x42bd9b: mov 0x8(%eax),%eax
 PC (0x0042bd9b) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /usr/lib/libdbusmenu-gtk.so.3
 ?? () from /usr/lib/libdbusmenu-gtk.so.3
 g_cclosure_marshal_VOID__PARAM () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: bluetooth-applet crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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