Ubuntu
gnome-bluetooth package

[maverick] [Macbook 6,1] bluetooth-applet crashed with SIGSEGV in dbusmenu_menuitem_property_set_value()

Bug #608661 reported by Delan Azabani on 2010-07-22

This bug report is a duplicate of: Bug #640289: bluetooth-applet crashed with SIGSEGV in g_type_check_instance_is_a() after pairing with a bluetooth device. Edit Remove

This bug affects 7 people

Affects		Status	Importance	Assigned to	Milestone
	gnome-bluetooth (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: gnome-bluetooth

bluetooth-applet segfaults when turning off bluetooth on a Macbook 6,1 but it turns off successfully (as observed when running bluetooth-applet to relaunch)

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-bluetooth 2.30.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-9.14-generic 2.6.35-rc5
Uname: Linux 2.6.35-9-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Thu Jul 22 18:42:57 2010
ExecutablePath: /usr/bin/bluetooth-applet
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: bluetooth-applet
ProcEnviron:
LANG=en_AU.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fbf9dc6088e <dbusmenu_menuitem_property_set_value+62>: cmp (%rdx),%rax
PC (0x7fbf9dc6088e) ok
source "(%rdx)" (0x0000000a) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
dbusmenu_menuitem_property_set_value ()
dbusmenu_menuitem_property_set_bool ()
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist ()
Title: bluetooth-applet crashed with SIGSEGV in dbusmenu_menuitem_property_set_value()
UserGroups:

Tags:

Revision history for this message

Delan Azabani (azabani) wrote on 2010-07-22:

Dependencies.txt Edit (4.5 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (34.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (768 bytes, text/plain; charset="utf-8")
Registers.txt Edit (804 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.9 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.9 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2010-07-23:

StacktraceTop:
dbusmenu_menuitem_child_add_position (mi=0xb0f800,
?? ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2010-07-23: Stacktrace.txt

Stacktrace.txt Edit (384 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2010-07-23: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (411 bytes, text/plain)

Changed in gnome-bluetooth (Ubuntu):
status:	New → Invalid

Revision history for this message

Apport retracing service (apport) wrote on 2010-07-23: 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:

libgtk2.0-common: installed version 2.21.2-0ubuntu5, latest version: 2.21.2-0ubuntu6
ifupdown: installed version 0.6.10ubuntu1, latest version: 0.6.10ubuntu2
libdbusmenu-gtk1: installed version 0.3.6-0ubuntu1, latest version: 0.3.7-0ubuntu1
libgtk2.0-0: installed version 2.21.2-0ubuntu5, latest version: 2.21.2-0ubuntu6
libdbusmenu-glib1: installed version 0.3.6-0ubuntu1, latest version: 0.3.7-0ubuntu1

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

Revision history for this message

Oded Arbel (oded-geek) wrote on 2010-08-04:

I have this issue with a fully up to date Maverick installation - how can I provide more information to this bug? (it appears the apport report that was generated on my machine was not attached here).