bluetooth-applet crashed with SIGSEGV

[Jeff Lane ]

Binary package hint: gnome-bluetooth

This frequently occurs and always immediately after boot and initial login on my Alienware M15x. It doesn't seem to affect the usability of my Bluetooth mouse, but the crash does happen roughly 4 out of 5 reboots.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-bluetooth 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Mar 25 22:37:14 2011
ExecutablePath: /usr/bin/bluetooth-applet
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: bluetooth-applet
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1e5f589d4e: movsbl 0x0(%rbp),%eax
 PC (0x7f1e5f589d4e) ok
 source "0x0(%rbp)" (0x00000001) 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/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: bluetooth-applet crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare vboxusers
XsessionErrors:
 (polkit-gnome-authentication-agent-1:2367): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nm-applet:2396): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed
 (nautilus:2397): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

[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 #634964, 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.