gnome-control-center crashed with SIGSEGV in dbus_connection_dispatch()

Bug #913532 reported by bnw
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
New
Undecided
Unassigned

Bug Description

While trying to connect to bluetooth headset (Nokia BH905i), the bluetooth settings manager first refused to connect, then became unresponsive and finally crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-bluetooth 3.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Sun Jan 8 21:21:30 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120107)
ProcCmdline: gnome-control-center bluetooth
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f943e1a4f0b: mov 0x8(%rax),%rdi
 PC (0x7f943e1a4f0b) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /usr/lib/libgnome-bluetooth.so.8
 ?? () from /usr/lib/control-center-1/panels/libbluetooth.so
 ?? () from /usr/lib/control-center-1/panels/libbluetooth.so
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: gnome-control-center crashed with SIGSEGV in dbus_connection_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
bnw (1i1g6) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

visibility: private → public
visibility: private → public
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.