Bug 192994 - kde crashes due to kde4 bluetooth framework crash
Summary: kde crashes due to kde4 bluetooth framework crash
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kde-bluetooth
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Tom Patzig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-17 13:35 UTC by baankrishna
Modified: 2018-09-04 18:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description baankrishna 2009-05-17 13:35:02 UTC
Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    Ubuntu Packages

The application KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4) crashed and caused the signal 11 (SIGSEGV) see logfile :

Cette pile des appels apparaît être inutilisable.
C'est probablement dû au fait que votre paquetage a été construit d'une manière qui empêche de créer des piles d'appels corrects, ou que le cadre de pile a été sérieusement corrompu dans l'incident.

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

Thread 1 (Thread 0xb6024920 (LWP 3629)):
#0  0xb80b4430 in __kernel_vsyscall ()
#1  0xb6739780 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb67395be in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7cf28b2 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb7cf3274 in KCrash::setApplicationName () from /usr/lib/libkdeui.so.5
#5  0x00000011 in ?? ()
#6  <signal handler called>
#7  0x00000028 in ?? ()
#8  0xb7575c43 in ?? () from /usr/lib/libQtDBus.so.4
#9  0xb7576501 in ?? () from /usr/lib/libQtDBus.so.4
#10 0xb75769fa in ?? () from /usr/lib/libQtDBus.so.4
#11 0xb746c3a0 in QObject::event () from /usr/lib/libQtCore.so.4
#12 0xb745b3db in QCoreApplication::event () from /usr/lib/libQtCore.so.4
#13 0xb6a67379 in QApplication::event () from /usr/lib/libQtGui.so.4
#14 0xb6a63e9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#15 0xb6a6c19e in QApplication::notify () from /usr/lib/libQtGui.so.4
#16 0xb7c8294d in KApplication::commitData () from /usr/lib/libkdeui.so.5
#17 0xbfccff60 in ?? ()
#18 0xb745ba3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#19 0xb745c695 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#20 0xb745c88d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#21 0xb74877ef in ?? () from /usr/lib/libQtCore.so.4
#22 0xb638eb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb63920eb in ?? () from /usr/lib/libglib-2.0.so.0
#24 0xb6392268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0xb7487438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#26 0xb6b05365 in ?? () from /usr/lib/libQtGui.so.4
#27 0xb745a06a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#28 0xb745a4aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#29 0xb757999c in ?? () from /usr/lib/libQtDBus.so.4
#30 0xb7563551 in QDBusConnection::call () from /usr/lib/libQtDBus.so.4
#31 0xb7581f3b in QDBusAbstractInterface::callWithArgumentList () from /usr/lib/libQtDBus.so.4
#32 0xb7585e8d in QDBusAbstractInterface::call () from /usr/lib/libQtDBus.so.4
#33 0x08066ce3 in _start ()
#0  0xb80b4430 in __kernel_vsyscall ()
Comment 1 Dario Andres 2009-05-17 16:32:02 UTC
If you experience this regularly, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks
Comment 2 Dario Andres 2009-06-26 15:59:43 UTC
Marking as NEEDSINFO
Comment 3 Andrew Crouthamel 2018-09-04 18:10:56 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.