Bug 187249 - Kde4 kbluetooth4 crashed and caused the signal 11 (SIGSEGV)
Summary: Kde4 kbluetooth4 crashed and caused the signal 11 (SIGSEGV)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kde-bluetooth
Classification: Unmaintained
Component: kbluetoothd (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-15 20:27 UTC by Hans
Modified: 2012-05-29 15:30 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Kluetooth4 crashed (1.74 KB, application/octet-stream)
2009-03-15 20:29 UTC, Hans
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hans 2009-03-15 20:27:10 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Mandriva RPMs

After inserting the bluetooth usb stick the Kbluetooth4 crashed and I could not work with bluetooth anymore.
Comment 1 Hans 2009-03-15 20:29:52 UTC
Created attachment 32148 [details]
Kluetooth4 crashed
Comment 2 Dario Andres 2009-03-15 21:51:12 UTC
Pasted backtrace from comment 1:

Programma: KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4), signaal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb610e6d0 (LWP 9362)]
[New Thread 0xb46d2b90 (LWP 10798)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0x00000000 in ?? ()
#7  0xb6c66921 in ?? () from /usr/lib/libsolidcontrol.so.4
#8  0xb6c66d5e in Solid::Control::BluetoothManager::findBluetoothInterface ()
   from /usr/lib/libsolidcontrol.so.4
#9  0xb6c63d12 in Solid::Control::BluetoothInterface::BluetoothInterface ()
   from /usr/lib/libsolidcontrol.so.4
#10 0x080639bd in _start ()
Comment 3 Dario Andres 2009-03-15 21:52:44 UTC
This may be related to bug 172267
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? 
You need to install the "libqt4-debug", "kdebase4-workspace-debug" packages
Thanks :)
Comment 4 mc_scRAT 2009-04-20 20:40:55 UTC
got same Bug. Fedora10-KDE. 
got it after plugging-out my bluetooth adapter without quitting tray icon

backtrace:

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7fe2b00 (LWP 12348)]
[New Thread 0xb6651b90 (LWP 15994)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x007dd416 in __kernel_vsyscall ()
[Current thread is 1 (Thread 0xb7fe2b00 (LWP 12348))]

Thread 2 (Thread 0xb6651b90 (LWP 15994)):
#0  0x007dd416 in __kernel_vsyscall ()
#1  0x00bde3d1 in select () from /lib/libc.so.6
#2  0x0090a627 in ?? () from /usr/lib/libQtCore.so.4
#3  0x0083a75e in ?? () from /usr/lib/libQtCore.so.4
#4  0x00cb051f in start_thread () from /lib/libpthread.so.0
#5  0x00be604e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb7fe2b00 (LWP 12348)):
#0  0x007dd416 in __kernel_vsyscall ()
#1  0x00ba1456 in nanosleep () from /lib/libc.so.6
#2  0x00ba126e in sleep () from /lib/libc.so.6
#3  0x0731d4ba in ?? () from /usr/lib/libkdeui.so.5
#4  0x0731deec in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0x00000001 in ?? ()
#7  0x0075dcdb in Solid::Control::BluetoothInterface::~BluetoothInterface () from /usr/lib/libsolidcontrol.so.4
#8  0x08051618 in _start ()
Comment 5 Dario Andres 2009-04-25 12:54:42 UTC
Marking as NEEDSINFO.
Comment 6 Dario Andres 2009-04-25 12:55:28 UTC
@mc_scRAT: your crash may be related or not, please look at the link on comment 3 to know how to get a complete backtrace.
Thanks
Comment 7 Christoph Feck 2012-05-29 15:30:20 UTC
Closing for lack of feedback.

If you believe the issue is still present in recent KDE versions (4.7.4 or 4.8.x), please file a new bug, re-open this one, or add a comment here.