Application: bluedevil-wizard (0.1) KDE Platform Version: 4.7.97 (4.8 RC2 (4.7.97) Qt Version: 4.7.4 Operating System: Linux 3.2.0-8-generic i686 Distribution: Ubuntu precise (development branch) -- Information about the crash: - What I was doing when the application crashed: just waking the PC. Conf: kubuntu 12.04 Alpha1 updated dayling incl. KDE 4.8 -- Backtrace: Application: Assistant Bluetooth (bluedevil-wizard), signal: Segmentation fault [Current thread is 1 (Thread 0xb772e930 (LWP 13806))] Thread 2 (Thread 0xb56b8b70 (LWP 13807)): #0 0x074fad10 in __GI_clock_gettime (clock_id=1, tp=0xb56b8038) at ../sysdeps/unix/clock_gettime.c:116 #1 0x00897565 in do_gettime (frac=0xb56b8030, sec=0xb56b8028) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x0096a116 in QTimerInfoList::updateCurrentTime (this=0x89df00c) at kernel/qeventdispatcher_unix.cpp:339 #4 0x0096a46a in QTimerInfoList::timerWait (this=0x89df00c, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x00968cb3 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb56b813c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x00968d4d in timerSourcePrepare (source=0x89defd8, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169 #7 0x06827ff2 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x068287ff in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x06828a51 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0x00969797 in QEventDispatcherGlib::processEvents (this=0x89df080, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0x00939fad in QEventLoop::processEvents (this=0xb56b82b0, flags=...) at kernel/qeventloop.cpp:149 #12 0x0093a1f1 in QEventLoop::exec (this=0xb56b82b0, flags=...) at kernel/qeventloop.cpp:201 #13 0x0083d69b in QThread::exec (this=0x89cf050) at thread/qthread.cpp:498 #14 0x0091abfd in QInotifyFileSystemWatcherEngine::run (this=0x89cf050) at io/qfilesystemwatcher_inotify.cpp:248 #15 0x00840543 in QThreadPrivate::start (arg=0x89cf050) at thread/qthread_unix.cpp:331 #16 0x00ef5d31 in start_thread (arg=0xb56b8b70) at pthread_create.c:304 #17 0x00e4511e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb772e930 (LWP 13806)): [KCrash Handler] #7 0x007be2dd in BlueDevil::Adapter::isPowered() const () from /usr/lib/libbluedevil.so.1 #8 0x007b0d4f in BlueDevil::Manager::Private::findUsableAdapter() () from /usr/lib/libbluedevil.so.1 #9 0x007b1269 in BlueDevil::Manager::Private::_k_adapterAdded(QDBusObjectPath const&) () from /usr/lib/libbluedevil.so.1 #10 0x007b3796 in BlueDevil::Manager::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libbluedevil.so.1 #11 0x009417dd in metacall (argv=0xbfdd8238, idx=9, cl=QMetaObject::InvokeMetaMethod, object=0x883b5e8) at kernel/qmetaobject.cpp:237 #12 QMetaObject::metacall (object=0x883b5e8, cl=QMetaObject::InvokeMetaMethod, idx=9, argv=0xbfdd8238) at kernel/qmetaobject.cpp:232 #13 0x009506ca in QMetaObject::activate (sender=0x88898e8, m=0x7dda58, local_signal_index=0, argv=0xbfdd8238) at kernel/qobject.cpp:3278 #14 0x007c7ad5 in ?? () from /usr/lib/libbluedevil.so.1 #15 0x007c7ed7 in ?? () from /usr/lib/libbluedevil.so.1 #16 0x00567957 in QDBusConnectionPrivate::deliverCall (this=0x8882598, object=0x88898e8, msg=..., metaTypes=..., slotIdx=0) at qdbusintegrator.cpp:942 #17 0x005717f6 in QDBusCallDeliveryEvent::placeMetaCall (this=0x8aa14e8, object=0x88898e8) at qdbusintegrator_p.h:103 #18 0x009537b2 in QObject::event (this=0x88898e8, e=0x8aa14e8) at kernel/qobject.cpp:1217 #19 0x010430d4 in notify_helper (e=0x8aa14e8, receiver=0x88898e8, this=0x8782980) at kernel/qapplication.cpp:4486 #20 QApplicationPrivate::notify_helper (this=0x8782980, receiver=0x88898e8, e=0x8aa14e8) at kernel/qapplication.cpp:4458 #21 0x01048483 in QApplication::notify (this=0x8aa14e8, receiver=0x88898e8, e=0x8aa14e8) at kernel/qapplication.cpp:3886 #22 0x002f8021 in KApplication::notify (this=0xbfdd8ac0, receiver=0x88898e8, event=0x8aa14e8) at ../../kdeui/kernel/kapplication.cpp:311 #23 0x0093af6e in QCoreApplication::notifyInternal (this=0xbfdd8ac0, receiver=0x88898e8, event=0x8aa14e8) at kernel/qcoreapplication.cpp:787 #24 0x0093ebf3 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8769ca8) at kernel/qcoreapplication.cpp:1428 #26 0x0093ed4c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1321 #27 0x00969304 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #28 postEventSourceDispatch (s=0x877f060) at kernel/qeventdispatcher_glib.cpp:277 #29 0x0682856a in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #30 0x06828975 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #31 0x06828a51 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #32 0x0096973a in QEventDispatcherGlib::processEvents (this=0x876a9d0, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #33 0x010fb1ba in QGuiEventDispatcherGlib::processEvents (this=0x876a9d0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #34 0x00939fad in QEventLoop::processEvents (this=0xbfdd8a24, flags=...) at kernel/qeventloop.cpp:149 #35 0x0093a1f1 in QEventLoop::exec (this=0xbfdd8a24, flags=...) at kernel/qeventloop.cpp:201 #36 0x0093edfd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #37 0x01040c74 in QApplication::exec () at kernel/qapplication.cpp:3760 #38 0x0804f2cb in ?? () #39 0x00d8c113 in __libc_start_main (main=0x804ee70, argc=1, ubp_av=0xbfdd8c04, init=0x805e510 <__libc_csu_init>, fini=0x805e580 <__libc_csu_fini>, rtld_fini=0xa98bc0, stack_end=0xbfdd8bfc) at libc-start.c:226 #40 0x0804f329 in _start () This bug may be a duplicate of or related to bug 288865. Possible duplicates by query: bug 289988, bug 289713, bug 288865. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 288865 ***