kbluetooth4 crashed with SIGSEGV in Solid::Control::BluetoothManager::findBluetoothInterface()

Bug #268821 reported by Craig Magina
198
This bug affects 7 people
Affects Status Importance Assigned to Milestone
kdebluetooth (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: kdebluetooth

I had updated my machine, logged out, restarted X and then logged back in. The apport icon was in the taskbar and here we are. The kbluetooth4 app is still running, as I see the icon in the taskbar and I am able to interact with it.

ProblemType: Crash
Architecture: amd64
Disassembly: 0x0:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/kbluetooth4
Package: kdebluetooth 1:0.2-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: kbluetooth4
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdebluetooth
Stacktrace:
 #0 0x0000000000000000 in ?? ()
 #1 0x00007f7e30397cf7 in ?? () from /usr/lib/libsolidcontrol.so.4
 #2 0x00007f7e30398085 in Solid::Control::BluetoothManager::findBluetoothInterface () from /usr/lib/libsolidcontrol.so.4
 #3 0x00007f7e3039523b in Solid::Control::BluetoothInterface::BluetoothInterface () from /usr/lib/libsolidcontrol.so.4
 #4 0x000000000041d23d in _start ()
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libsolidcontrol.so.4
 Solid::Control::BluetoothManager::findBluetoothInterface () from /usr/lib/libsolidcontrol.so.4
 Solid::Control::BluetoothInterface::BluetoothInterface () from /usr/lib/libsolidcontrol.so.4
 _start ()
Title: kbluetooth4 crashed with SIGSEGV in Solid::Control::BluetoothManager::findBluetoothInterface()
Uname: Linux 2.6.27-2-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
Craig Magina (craig.magina) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface (this=0xc8d190,
Solid::Control::BluetoothManager::findBluetoothInterface (this=0xc8d0c0, ubi=@0x7fff3a8cca30)
BluetoothInterface (this=0xf837d0, ubi=@0x7fff3a8cca30)
_start ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Is this reproducible? Has this happened again lately?

Changed in kdebluetooth:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pascal d'Hermilly (pascal-tipisoft) wrote :

yes, just happened to me upon startup. Fully updated.
see bug 273753 for LOTS of debug information

Changed in kdebluetooth:
status: Incomplete → Confirmed
Revision history for this message
Martin Nowack (martin-nowack) wrote :

This happened for me too with a fully updated system. After using the killswitch on a T60 to disable wireless and switch on again it kdebluetooth4 segaulted.

Revision history for this message
Tore Anderson (toreanderson) wrote :

Happened to me today with a fully updated Intrepid.

Tore

Revision history for this message
ThyMythos (thymythos) wrote :

Same here...

Revision history for this message
Reinhard (enterldestodes) wrote :

I assume that my bluetooth stuff always crashes when I suspend the system while bluetooth is being actively used, in my case as a modem, using pon for the connection over bluetooth/umts mobile.

Revision history for this message
Salze (stefan-sarzio) wrote :

I've just had that crash, too. I'm transfering some videos from my mobile to the notebook. As far as I can tell the transfer continues as normal and I can see no real problem.

I'm using Intrepid beta. Launchpad says that debugging information have been added automatically. Is that also true when subscribing to an existing bug, or just if I had chosen to open a new one?

Revision history for this message
Craig Magina (craig.magina) wrote :

It crashed for me when waking up from suspension. There had been a mouse attached when it went to sleep.

Revision history for this message
Matt Neilson (ichthyoboy) wrote :

I had the same crash upon wake from suspend.

Revision history for this message
Boris Rybalkin (ribalkin) wrote :

I've just restarted X ctrl+alt+backspace and I see that message.
Ubuntu Intrepid 64.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fixed with kdebluetooth 0.3 in Jaunty. The fixed version will be making its way into Intrepid soon.

Changed in kdebluetooth:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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