bluetooth-applet crashed with SIGSEGV in g_type_check_instance_is_a()

Bug #636502 reported by Uphaar Agrawalla
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-bluetooth

Crashed as soon as i paired my headset with the laptop.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-bluetooth 2.31.6-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Sep 12 18:03:48 2010
ExecutablePath: /usr/bin/bluetooth-applet
ProcCmdline: bluetooth-applet
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb2d797b8e8 <g_type_check_instance_is_a+184>: testb $0x4,0x16(%rdx)
 PC (0x7fb2d797b8e8) ok
 source "$0x4" ok
 destination "0x16(%rdx)" (0x6353636962617256) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 g_type_check_instance_is_a () from /usr/lib/libgobject-2.0.so.0
 dbusmenu_menuitem_property_get () from /usr/lib/libdbusmenu-glib.so.1
 ?? ()
 ?? () from /usr/lib/libappindicator.so.1
 ?? ()
Title: bluetooth-applet crashed with SIGSEGV in g_type_check_instance_is_a()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Uphaar Agrawalla (uphaar) wrote :
visibility: private → public
Revision history for this message
Uphaar Agrawalla (uphaar) wrote :

Possible duplicate of bug 625944 or bug 606597.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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 gnome-bluetooth (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libavahi-common3: installed version 0.6.27-2ubuntu1, latest version: 0.6.27-2ubuntu3
udev: installed version 161+git20100827-1, latest version: 162-1
gnome-bluetooth: installed version 2.31.6-0ubuntu3, latest version: 2.31.90-0ubuntu1
libudev0: installed version 161+git20100827-1, latest version: 162-1
libavahi-client3: installed version 0.6.27-2ubuntu1, latest version: 0.6.27-2ubuntu3
libgdk-pixbuf2.0-0: installed version 2.21.6-2ubuntu5, latest version: 2.21.7-1ubuntu3
obex-data-server: installed version 0.4.5-1, latest version: 0.4.5-1build1
libgnome-bluetooth8: installed version 2.31.6-0ubuntu3, latest version: 2.31.90-0ubuntu1
initramfs-tools-bin: installed version 0.98.1ubuntu1, latest version: 0.98.1ubuntu3
initramfs-tools: installed version 0.98.1ubuntu1, latest version: 0.98.1ubuntu3
libavahi-common-data: installed version 0.6.27-2ubuntu1, latest version: 0.6.27-2ubuntu3

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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