bluetooth-applet crashed with SIGSEGV

[Steve Langasek]

Binary package hint: gnome-bluetooth

bluetooth-applet has been crashing regularly for me since before the maverick release, but it's only after release that the stack has been stable enough for me to be able to report it without apport giving me an "out-of-date packages" error. I'm not sure what the trigger is for this crash; it might be related to suspend/resume.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-bluetooth 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Wed Oct 13 20:21:24 2010
ExecutablePath: /usr/bin/bluetooth-applet
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: bluetooth-applet
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa2df1ccd4e: movsbl 0x0(%rbp),%eax
 PC (0x7fa2df1ccd4e) 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 libvirtd lpadmin plugdev sambashare src
XsessionErrors:
 (polkit-gnome-authentication-agent-1:2838): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2863): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (npviewer.bin:4190): Gdk-WARNING **: XID collision, trouble ahead

[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.