[Bug 188181] New: Bluetooth daemon segfaults when hitting WLAN/Bluetooth kill switch

[Rob Loefman]

https://bugs.kde.org/show_bug.cgi?id=188181

           Summary: Bluetooth daemon segfaults when hitting WLAN/Bluetooth
                    kill switch
           Product: kde
           Version: unspecified
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: rolofman at cubical.fi


Version:            (using KDE 4.1.4)
OS:                Linux
Installed from:    Ubuntu Packages

This happens on a
-FujitsuSiemens E series Lifebook laptop.
-Linux laptop 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686
GNU/Linux  
-Ubuntu 8.10


A Fatal Error Occurred
The application KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4)
crashed and caused the signal 11 (SIGSEGV).
Please help us improve the software you use by filing a report at
http://bugs.kde.org. Useful details include how to reproduce the error,
documents that were loaded, etc.


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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb62026c0 (LWP 8891)]
0xb8089430 in __kernel_vsyscall ()
[Current thread is 0 (process 8891)]

Thread 1 (Thread 0xb62026c0 (LWP 8891)):
#0  0xb8089430 in __kernel_vsyscall ()
#1  0xb6ac7f10 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb6ac7d4e in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7cab612 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb7cac014 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0x0943061e in ?? ()
#7  0xb6cd8156 in ?? () from /usr/lib/libQtDBus.so.4
#8  0xb6cd89b1 in ?? () from /usr/lib/libQtDBus.so.4
#9  0xb6cd8eaa in ?? () from /usr/lib/libQtDBus.so.4
#10 0xb777d771 in QObject::event () from /usr/lib/libQtCore.so.4
#11 0xb776d7cb in QCoreApplication::event () from /usr/lib/libQtCore.so.4
#12 0xb6e64206 in QApplication::event () from /usr/lib/libQtGui.so.4
#13 0xb6e5e8ec in QApplicationPrivate::notify_helper () from
/usr/lib/libQtGui.so.4
#14 0xb6e6672e in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb7c3dd1d in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0xb776de61 in QCoreApplication::notifyInternal () from
/usr/lib/libQtCore.so.4
#17 0xb776eae5 in QCoreApplicationPrivate::sendPostedEvents () from
/usr/lib/libQtCore.so.4
#18 0xb776ecdd in QCoreApplication::sendPostedEvents () from
/usr/lib/libQtCore.so.4
#19 0xb779882f in ?? () from /usr/lib/libQtCore.so.4
#20 0xb65834e8 in IA__g_main_context_dispatch (context=0x92d2290) at
gmain.c:2144
#21 0xb6586b93 in g_main_context_iterate (context=0x92d2290, block=1,
dispatch=1, self=0x92c9b70) at gmain.c:2778
#22 0xb6586d51 in IA__g_main_context_iteration (context=0x92d2290, may_block=1)
at gmain.c:2841
#23 0xb7798478 in QEventDispatcherGlib::processEvents () from
/usr/lib/libQtCore.so.4
#24 0xb6ef8ea5 in ?? () from /usr/lib/libQtGui.so.4
#25 0xb776c52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#26 0xb776c6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#27 0xb6cdb52b in ?? () from /usr/lib/libQtDBus.so.4
#28 0xb6cc5a31 in QDBusConnection::call () from /usr/lib/libQtDBus.so.4
#29 0xb6ce4dab in QDBusAbstractInterface::callWithArgumentList () from
/usr/lib/libQtDBus.so.4
#30 0xb6ce6c5d in QDBusAbstractInterface::call () from /usr/lib/libQtDBus.so.4
#31 0x08065f63 in _start ()
#0  0xb8089430 in __kernel_vsyscall ()

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.