[kde] [Bug 358162] New: Segfault after removing a bluetooth USB dongle

Pastafarianist via KDE Bugzilla bugzilla_noreply at kde.org
Mon Jan 18 13:18:54 GMT 2016


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

            Bug ID: 358162
           Summary: Segfault after removing a bluetooth USB dongle
           Product: kde
           Version: unspecified
          Platform: unspecified
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: mr.pastafarianist at gmail.com

Application: bluedevil-monolithic (2.1.1)
KDE Platform Version: 4.14.8 (Compiled from sources)
Qt Version: 4.8.6
Operating System: Linux 4.1.12-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
- What I was doing when the application crashed: removed a bluetooth USB dongle

- Unusual behavior I noticed: I use this dongle to connect my phone to the PC.
It usually fails to connect when I resume the PC from suspend. Removing the
dongle and re-inserting it again solves the issue until the next suspend.

The crash can be reproduced every time.

-- Backtrace:
Application: Bluetooth (bluedevil-monolithic), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007faffc862246 in ?? () from /usr/lib64/libbluedevil.so.2
#7  0x00007faffc86149b in BlueDevil::Adapter::Private::_k_deviceRemoved(QString
const&) () from /usr/lib64/libbluedevil.so.2
#8  0x00007faffc85a688 in ?? () from /usr/lib64/libbluedevil.so.2
#9  0x00007faffbdb373a in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007faffc865bda in ?? () from /usr/lib64/libbluedevil.so.2
#11 0x00007faffc865c2d in ?? () from /usr/lib64/libbluedevil.so.2
#12 0x00007faffc865e73 in ?? () from /usr/lib64/libbluedevil.so.2
#13 0x00007faffc12a106 in ?? () from /usr/lib64/qt4/libQtDBus.so.4
#14 0x00007faffbdb7ade in QObject::event(QEvent*) () from
/usr/lib64/qt4/libQtCore.so.4
#15 0x00007faffb14254c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/qt4/libQtGui.so.4
#16 0x00007faffb148a8d in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/qt4/libQtGui.so.4
#17 0x00007faffccb156a in KApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libkdeui.so.5
#18 0x00007faffbd9f9dd in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/qt4/libQtCore.so.4
#19 0x00007faffbda2afd in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4
#20 0x00007faffbdcce5e in ?? () from /usr/lib64/qt4/libQtCore.so.4
#21 0x00007faff703a994 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#22 0x00007faff703abe8 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007faff703ac8c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#24 0x00007faffbdcc61e in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/qt4/libQtCore.so.4
#25 0x00007faffb1decd6 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#26 0x00007faffbd9e59f in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/qt4/libQtCore.so.4
#27 0x00007faffbd9e895 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/qt4/libQtCore.so.4
#28 0x00007faffbda3b39 in QCoreApplication::exec() () from
/usr/lib64/qt4/libQtCore.so.4
#29 0x00000000004048cb in ?? ()
#30 0x00007faffa8f3855 in __libc_start_main () from /lib64/libc.so.6
#31 0x000000000040491c in _start ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list