Bug 289988 - bluedevil and kded4 crash after resume from RAM
Summary: bluedevil and kded4 crash after resume from RAM
Status: RESOLVED DUPLICATE of bug 288865
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-28 08:44 UTC by ancow
Modified: 2011-12-28 12:56 UTC (History)
0 users

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 ancow 2011-12-28 08:44:51 UTC
Application: bluedevil-helper (0.1)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.3
Operating System: Linux 3.1.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (wheezy)

-- Information about the crash:
- What I was doing when the application crashed:

The crash reports for kded and bluedevil were displayed right after logging in after resuming from a suspend-to-ram. Bluetooth is and was disabled from the bluedevil interface and no bluetooth devices were anywhere in range.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Bluetooth-Dateiempfang-Hilfsprogramm (bluedevil-helper), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f9e1d3fd468 in BlueDevil::Adapter::isPowered() const () from /usr/lib/libbluedevil.so.1
#7  0x00007f9e1d3f1084 in BlueDevil::Manager::Private::findUsableAdapter() () from /usr/lib/libbluedevil.so.1
#8  0x00007f9e1d3f152c in BlueDevil::Manager::Private::_k_adapterAdded(QDBusObjectPath const&) () from /usr/lib/libbluedevil.so.1
#9  0x00007f9e1d3f3816 in BlueDevil::Manager::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libbluedevil.so.1
#10 0x00007f9e1bc7ab1a in QMetaObject::activate (sender=0xc7f9a0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff2d462430) at kernel/qobject.cpp:3278
#11 0x00007f9e1d4060e2 in ?? () from /usr/lib/libbluedevil.so.1
#12 0x00007f9e1d406464 in ?? () from /usr/lib/libbluedevil.so.1
#13 0x00007f9e1bfbf971 in QDBusConnectionPrivate::deliverCall (this=0xccd0e0, object=0xc7f9a0, msg=..., metaTypes=..., slotIdx=5) at qdbusintegrator.cpp:941
#14 0x00007f9e1bfc8eaf in QDBusCallDeliveryEvent::placeMetaCall (this=<optimized out>, object=<optimized out>) at qdbusintegrator_p.h:103
#15 0x00007f9e1bc7e6ca in QObject::event (this=0xc7f9a0, e=<optimized out>) at kernel/qobject.cpp:1217
#16 0x00007f9e1c90f9f4 in notify_helper (e=0xca7fd0, receiver=0xc7f9a0, this=0xb9beb0) at kernel/qapplication.cpp:4467
#17 QApplicationPrivate::notify_helper (this=0xb9beb0, receiver=0xc7f9a0, e=0xca7fd0) at kernel/qapplication.cpp:4439
#18 0x00007f9e1c914881 in QApplication::notify (this=0x7fff2d463130, receiver=0xc7f9a0, e=0xca7fd0) at kernel/qapplication.cpp:4346
#19 0x00007f9e1d87cae6 in KApplication::notify (this=0x7fff2d463130, receiver=0xc7f9a0, event=0xca7fd0) at ../../kdeui/kernel/kapplication.cpp:311
#20 0x00007f9e1bc67fbc in QCoreApplication::notifyInternal (this=0x7fff2d463130, receiver=0xc7f9a0, event=0xca7fd0) at kernel/qcoreapplication.cpp:731
#21 0x00007f9e1bc6b378 in sendEvent (event=0xca7fd0, receiver=0xc7f9a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#22 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xb7b320) at kernel/qcoreapplication.cpp:1372
#23 0x00007f9e1bc92663 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#24 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:277
#25 0x00007f9e184690cf in g_main_dispatch (context=0xb99ca0) at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c:2442
#26 g_main_context_dispatch (context=0xb99ca0) at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c:2998
#27 0x00007f9e184698c8 in g_main_context_iterate (context=0xb99ca0, block=<optimized out>, dispatch=1, self=<optimized out>) at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c:3076
#28 0x00007f9e18469a99 in g_main_context_iteration (context=0xb99ca0, may_block=1) at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c:3139
#29 0x00007f9e1bc92abf in QEventDispatcherGlib::processEvents (this=0xb7ca10, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#30 0x00007f9e1c9b39ce in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x00007f9e1bc671c2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#32 0x00007f9e1bc673bf in QEventLoop::exec (this=0x7fff2d4630c0, flags=...) at kernel/qeventloop.cpp:201
#33 0x00007f9e1bc6b567 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#34 0x0000000000406c89 in ?? ()
#35 0x00007f9e1b48cead in __libc_start_main (main=<optimized out>, argc=<optimized out>, ubp_av=<optimized out>, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff2d463398) at libc-start.c:228
#36 0x0000000000406cdd in _start ()

This bug may be a duplicate of or related to bug 288865.

Possible duplicates by query: bug 289713, bug 288865.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-12-28 12:56:54 UTC

*** This bug has been marked as a duplicate of bug 288865 ***