Application: bluedevil-input (2.0.0) KDE Platform Version: 4.11.3 Qt Version: 4.8.5 Operating System: Linux 3.11.7-300.fc20.x86_64 x86_64 Distribution: "Fedora release 20 (Heisenbug)" -- Information about the crash: Right-click on the bluetooth icon on system tray, select (already configured earlier) entry for Logitech Bluetooth Mouse M55db and select "Connect" from submenu Crash dialog appears. The crash can be reproduced every time. -- Backtrace: Application: Bluetooth Input Helper (bluedevil-input), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [KCrash Handler] #6 BlueDevil::Device::UUIDs (this=this@entry=0x0) at /usr/src/debug/libbluedevil-2.0/bluedevil/bluedevildevice.cpp:218 #7 0x00000000004043c4 in InputHelper::InputHelper (this=0x2030340, address=...) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/input/helper/inputhelper.cpp:42 #8 0x0000000000403d01 in main (argc=2, argv=0x7fffd387e628) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/input/helper/main.cpp:49 Reported using DrKonqi
*** Bug 326138 has been marked as a duplicate of this bug. ***
Created attachment 83687 [details] New crash information added by DrKonqi bluedevil-input (2.0.0) on KDE Platform 4.11.2 using Qt 4.8.5 Right-click on the bluetooth icon on system tray, select (already configured earlier) entry for V470 Cordless Laser Mouse for Bluetooth - Logitech and select "Connect" from submenu Crash dialog appears. -- Backtrace (Reduced): #5 BlueDevil::Device::UUIDs (this=this@entry=0x0) at /usr/src/debug/libbluedevil/bluedevil/bluedevildevice.cpp:218 #6 0x0000000000404621 in InputHelper::InputHelper (this=0x2181a40, address=...) at /usr/src/debug/bluedevil/src/actionplugins/input/helper/inputhelper.cpp:42 #7 0x0000000000403ffe in main (argc=2, argv=0x7fffce5030b8) at /usr/src/debug/bluedevil/src/actionplugins/input/helper/main.cpp:49
Created attachment 83747 [details] New crash information added by DrKonqi bluedevil-input (2.0.0) on KDE Platform 4.11.2 using Qt 4.8.5 - What I was doing when the application crashed: right click on bluetooth device BT mouse which was already configured. I receive the crash. The same happens with BT keyboard or other BT devices. -- Backtrace (Reduced): #5 BlueDevil::Device::UUIDs (this=this@entry=0x0) at /usr/src/debug/libbluedevil/bluedevil/bluedevildevice.cpp:218 #6 0x0000000000404621 in InputHelper::InputHelper (this=0x17dd7b0, address=...) at /usr/src/debug/bluedevil/src/actionplugins/input/helper/inputhelper.cpp:42 #7 0x0000000000403ffe in main (argc=2, argv=0x7fff5416d668) at /usr/src/debug/bluedevil/src/actionplugins/input/helper/main.cpp:49
Created attachment 83801 [details] New crash information added by DrKonqi bluedevil-input (2.0.0) on KDE Platform 4.11.2 using Qt 4.8.5 - What I was doing when the application crashed: This only happened after a return from a laptop suspend. Before the travel mouse (logitec) connects automatically at login. After the suspend it's no longer connected and trying to connect it manually leads to the crash. -- Backtrace (Reduced): #5 0x00007f527be5b68b in BlueDevil::Device::UUIDs() () from /usr/lib64/libbluedevil.so.2 #6 0x0000000000404621 in InputHelper::InputHelper (this=0x1f2c530, address=...) at /usr/src/debug/bluedevil/src/actionplugins/input/helper/inputhelper.cpp:42 #7 0x0000000000403ffe in main (argc=2, argv=0x7fff707e7ce8) at /usr/src/debug/bluedevil/src/actionplugins/input/helper/main.cpp:49
*** Bug 328159 has been marked as a duplicate of this bug. ***
Same problem on OpenSuse 13.1 openSUSE 13.1 (i586) VERSION = 13.1 CODENAME = Bottle KDE "Bluetooth Device Wizard" always crashes on adding a Logitech Bluetooth Mouse M-RCQ142 and the connection LED on the mouse continuing flashing. After reopen "Add device" in the taskbar I can see a device "Bluetooth Laser Travel Mouse", but mouse does not work anyway. That's the crash report: Application: KDE-Dienst (kded4), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xb547f740 (LWP 1087))] Thread 5 (Thread 0xae320b40 (LWP 1093)): #0 0xb7778424 in __kernel_vsyscall () #1 0xb5fb1e3b in poll () from /lib/libc.so.6 #2 0xb597b98b in g_poll () from /usr/lib/libglib-2.0.so.0 #3 0xb596caf8 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb596cc38 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb6dfd60f in QEventDispatcherGlib::processEvents (this=0xada00468, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0xb6dcca03 in QEventLoop::processEvents (this=this@entry=0xae320258, flags=...) at kernel/qeventloop.cpp:149 #7 0xb6dccd29 in QEventLoop::exec (this=this@entry=0xae320258, flags=...) at kernel/qeventloop.cpp:204 #8 0xb6cbb30d in QThread::exec (this=this@entry=0x8f2f5a0) at thread/qthread.cpp:536 #9 0xb6dace14 in QInotifyFileSystemWatcherEngine::run (this=0x8f2f5a0) at io/qfilesystemwatcher_inotify.cpp:256 #10 0xb6cbdc5f in QThreadPrivate::start (arg=0x8f2f5a0) at thread/qthread_unix.cpp:338 #11 0xb6c3a07a in start_thread () from /lib/libpthread.so.0 #12 0xb5fbd80e in clone () from /lib/libc.so.6 Thread 4 (Thread 0xabbc1b40 (LWP 1152)): #0 0xb596c970 in ?? () from /usr/lib/libglib-2.0.so.0 #1 0xb596cfdb in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #2 0xabc99fca in ?? () from /usr/lib/libgio-2.0.so.0 #3 0xb5992d5a in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb6c3a07a in start_thread () from /lib/libpthread.so.0 #5 0xb5fbd80e in clone () from /lib/libc.so.6 Thread 3 (Thread 0xab3b4b40 (LWP 1154)): #0 0xb6c3c37a in pthread_mutex_lock () from /lib/libpthread.so.0 #1 0xb59afc60 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 #2 0xb596bf99 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #3 0xb596c9ef in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb596cc38 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb6dfd60f in QEventDispatcherGlib::processEvents (this=0xad002110, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0xb6dcca03 in QEventLoop::processEvents (this=this@entry=0xab3b4268, flags=...) at kernel/qeventloop.cpp:149 #7 0xb6dccd29 in QEventLoop::exec (this=this@entry=0xab3b4268, flags=...) at kernel/qeventloop.cpp:204 #8 0xb6cbb30d in QThread::exec (this=0x8f1a358) at thread/qthread.cpp:536 #9 0xae5a2e97 in KCupsConnection::run() () from /usr/lib/libkcupslib.so #10 0xb6cbdc5f in QThreadPrivate::start (arg=0x8f1a358) at thread/qthread_unix.cpp:338 #11 0xb6c3a07a in start_thread () from /lib/libpthread.so.0 #12 0xb5fbd80e in clone () from /lib/libc.so.6 Thread 2 (Thread 0xaabb3b40 (LWP 1155)): #0 0xb6c3d35d in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0 #1 0xb59afca0 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #2 0xb596c512 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0xb596ca8a in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb596cc38 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb6dfd60f in QEventDispatcherGlib::processEvents (this=0xada022e8, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0xb6dcca03 in QEventLoop::processEvents (this=this@entry=0xaabb3288, flags=...) at kernel/qeventloop.cpp:149 #7 0xb6dccd29 in QEventLoop::exec (this=this@entry=0xaabb3288, flags=...) at kernel/qeventloop.cpp:204 #8 0xb6cbb30d in QThread::exec (this=this@entry=0x8f16118) at thread/qthread.cpp:536 #9 0xb6cbb45b in QThread::run (this=0x8f16118) at thread/qthread.cpp:603 #10 0xb6cbdc5f in QThreadPrivate::start (arg=0x8f16118) at thread/qthread_unix.cpp:338 #11 0xb6c3a07a in start_thread () from /lib/libpthread.so.0 #12 0xb5fbd80e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb547f740 (LWP 1087)): [KCrash Handler] #7 QDBusAbstractInterfacePrivate::canMakeCalls (this=0x8de9d68) at qdbusabstractinterface.cpp:114 #8 0xb5b42b60 in QDBusAbstractInterface::asyncCallWithArgumentList (this=0x8f1a228, method=..., args=...) at qdbusabstractinterface.cpp:495 #9 0xae5f0eb3 in RegisterAgent (capability=..., agent=..., this=<optimized out>) at /usr/src/debug/libbluedevil/build/bluedevil/bluezagentmanager1.h:43 #10 BlueDevil::Manager::registerAgent (this=0x8f1a238, agentPath=..., registerCapability=registerCapability@entry=BlueDevil::Manager::DisplayYesNo) at /usr/src/debug/libbluedevil/bluedevil/bluedevilmanager.cpp:186 #11 0xae3d18a1 in BluezAgent::BluezAgent (this=0x9412358, parent=0x90f17a0) at /usr/src/debug/bluedevil/src/daemon/kded/bluezagent.cpp:41 #12 0xae3cdb24 in BlueDevilDaemon::onlineMode (this=this@entry=0x8f1cbd8) at /usr/src/debug/bluedevil/src/daemon/kded/BlueDevilDaemon.cpp:203 #13 0xae3ce5ed in BlueDevilDaemon::usableAdapterChanged (this=0x8f1cbd8, adapter=0x8e56f60) at /usr/src/debug/bluedevil/src/daemon/kded/BlueDevilDaemon.cpp:296 #14 0xae3cab04 in BlueDevilDaemon::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=0xbfac9088, _c=<optimized out>) at /usr/src/debug/bluedevil/build/src/daemon/kded/moc_BlueDevilDaemon.cpp:70 #15 0xb6de2c55 in QMetaObject::activate (sender=sender@entry=0x8f1a238, m=m@entry=0xae60fb98 <BlueDevil::Manager::staticMetaObject>, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0xbfac9088) at kernel/qobject.cpp:3556 #16 0xae5f02c5 in BlueDevil::Manager::usableAdapterChanged (this=0x8f1a238, _t1=0x8e56f60) at /usr/src/debug/libbluedevil/build/bluedevil/bluedevilmanager.moc:175 #17 0xae5f202c in BlueDevil::Manager::Private::_k_interfacesAdded (this=0x8f0aa70, objectPath=..., interfaces=...) at /usr/src/debug/libbluedevil/bluedevil/bluedevilmanager.cpp:211 #18 0xae5f56fd in BlueDevil::Manager::qt_static_metacall (_o=_o@entry=0x8f1a238, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfac9234) at /usr/src/debug/libbluedevil/build/bluedevil/bluedevilmanager.moc:84 #19 0xb6de2c55 in QMetaObject::activate (sender=sender@entry=0x8e84a08, m=m@entry=0xae60fcf8 <OrgFreedesktopDBusObjectManagerInterface::staticMetaObject>, local_signal_index=0, argv=0xbfac9234) at kernel/qobject.cpp:3556 #20 0xae6014fd in InterfacesRemoved (_t2=..., _t1=..., this=<optimized out>) at /usr/src/debug/libbluedevil/build/bluedevil/dbusobjectmanager.moc:116 #21 OrgFreedesktopDBusObjectManagerInterface::qt_static_metacall (_o=0x8e84a08, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfac934c) at /usr/src/debug/libbluedevil/build/bluedevil/dbusobjectmanager.moc:58 #22 0xae6019cc in OrgFreedesktopDBusObjectManagerInterface::qt_metacall (this=0x8e84a08, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfac934c) at /usr/src/debug/libbluedevil/build/bluedevil/dbusobjectmanager.moc:99 #23 0xb5b33dec in QDBusConnectionPrivate::deliverCall (this=0x8f11a88, object=object@entry=0x8e84a08, msg=..., metaTypes=..., slotIdx=5) at qdbusintegrator.cpp:951 #24 0xb5b3cf5d in QDBusCallDeliveryEvent::placeMetaCall (this=0x8f1b440, object=0x8e84a08) at qdbusintegrator_p.h:103 #25 0xb6de72bb in QObject::event (this=0x8e84a08, e=0x8f1b440) at kernel/qobject.cpp:1203 #26 0xb62b94b4 in QApplicationPrivate::notify_helper (this=0x8dadd60, receiver=0x8e84a08, e=0x8f1b440) at kernel/qapplication.cpp:4562 #27 0xb62bfee3 in QApplication::notify (this=0xbfac99fc, receiver=receiver@entry=0x8e84a08, e=e@entry=0x8f1b440) at kernel/qapplication.cpp:4348 #28 0xb751ecb4 in KApplication::notify (this=0xbfac99fc, receiver=0x8e84a08, event=0x8f1b440) at /usr/src/debug/kdelibs-4.11.2/kdeui/kernel/kapplication.cpp:311 #29 0xb6dcdfba in QCoreApplication::notifyInternal (this=0xbfac99fc, receiver=receiver@entry=0x8e84a08, event=event@entry=0x8f1b440) at kernel/qcoreapplication.cpp:949 #30 0xb6dd12e5 in sendEvent (event=0x8f1b440, receiver=0x8e84a08) at kernel/qcoreapplication.h:231 #31 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x8d4bf80) at kernel/qcoreapplication.cpp:1573 #32 0xb6dd180c in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1466 #33 0xb6dfde0e in sendPostedEvents () at kernel/qcoreapplication.h:236 #34 postEventSourceDispatch (s=0x8daf200) at kernel/qeventdispatcher_glib.cpp:280 #35 0xb596c7ce in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #36 0xb596cb78 in ?? () from /usr/lib/libglib-2.0.so.0 #37 0xb596cc38 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #38 0xb6dfd5ef in QEventDispatcherGlib::processEvents (this=this@entry=0x8d4fe00, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #39 0xb636951e in QGuiEventDispatcherGlib::processEvents (this=0x8d4fe00, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #40 0xb6dcca03 in QEventLoop::processEvents (this=this@entry=0xbfac9918, flags=...) at kernel/qeventloop.cpp:149 #41 0xb6dccd29 in QEventLoop::exec (this=this@entry=0xbfac9918, flags=...) at kernel/qeventloop.cpp:204 #42 0xb6dd24fe in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221 #43 0xb62b7944 in QApplication::exec () at kernel/qapplication.cpp:3823 #44 0xb5307d53 in kdemain (argc=1, argv=0x8d9db08) at /usr/src/debug/kdelibs-4.11.2/kded/kded.cpp:925 #45 0x0804fba3 in launch (argc=<optimized out>, argc@entry=1, _name=_name@entry=0x80524a7 "kded4", args=<optimized out>, args@entry=0x0, cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized out>, envs@entry=0x0, reset_env=reset_env@entry=false, tty=tty@entry=0x0, avoid_loops=avoid_loops@entry=false, startup_id_str=startup_id_str@entry=0x8052336 "0") at /usr/src/debug/kdelibs-4.11.2/kinit/kinit.cpp:726 #46 0x0804ce98 in main (argc=4, argv=0xbfac9f44, envp=0xbfac9f58) at /usr/src/debug/kdelibs-4.11.2/kinit/kinit.cpp:1841
*** Bug 328626 has been marked as a duplicate of this bug. ***
Created attachment 84128 [details] New crash information added by DrKonqi bluedevil-input (2.0.0) on KDE Platform 4.11.3 using Qt 4.8.5 - What I was doing when the application crashed: Clicked "connect" from systray icon menu, submenu "logitech bluetooth mouse m555b", under heading "known devices". - Unusual behavior I noticed: The mouse was already connected (i.e. I was already using it to navigate aforementioned menu). I found it surprising that there was an option to "connect" in the first place. -- Backtrace (Reduced): #6 BlueDevil::Device::UUIDs (this=this@entry=0x0) at /usr/src/debug/libbluedevil-2.0/bluedevil/bluedevildevice.cpp:218 #7 0x00000000004043c4 in InputHelper::InputHelper (this=0x10fb4c0, address=...) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/input/helper/inputhelper.cpp:42 #8 0x0000000000403d01 in main (argc=2, argv=0x7fffb4c6df48) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/input/helper/main.cpp:49
confirmed, fairly reproducible on fedora 20 (using fresh bluez5 branch snapshot)
https://git.reviewboard.kde.org/r/114433/ seems to help here.
This file will be deleted from the project, no point on tracking bugs about it.
This file will be deleted when? And why? Is it getting replaced? If so, by what? Closing bugs that are not fixed is not that great an idea.
Created attachment 84190 [details] New crash information added by DrKonqi bluedevil-input (2.0.0) on KDE Platform 4.11.3 using Qt 4.8.5 - What I was doing when the application crashed: Right mouse on bluetooth widget --> Logitech Bluetooth mouse M555b --X crash dialog -- Backtrace (Reduced): #6 BlueDevil::Device::UUIDs (this=this@entry=0x0) at /usr/src/debug/libbluedevil-2.0/bluedevil/bluedevildevice.cpp:218 #7 0x00000000004043c4 in InputHelper::InputHelper (this=0x220ffa0, address=...) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/input/helper/inputhelper.cpp:42 #8 0x0000000000403d01 in main (argc=2, argv=0x7fff5c80b648) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/input/helper/main.cpp:49
Created attachment 84199 [details] New crash information added by DrKonqi bluedevil-input (2.0.0) on KDE Platform 4.11.3 using Qt 4.8.5 - What I was doing when the application crashed: Running bluedevil-input manually from the command line -- Backtrace (Reduced): #6 BlueDevil::Device::UUIDs (this=this@entry=0x0) at /usr/src/debug/libbluedevil-2.0/bluedevil/bluedevildevice.cpp:218 #7 0x00000000004043c4 in InputHelper::InputHelper (this=0x20f7760, address=...) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/input/helper/inputhelper.cpp:42 #8 0x0000000000403d01 in main (argc=1, argv=0x7fff3f5275c8) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/input/helper/main.cpp:49
(In reply to comment #11) > This file will be deleted from the project, no point on tracking bugs about it. And in the interim I just continue manually configuring devices? This should be a quick fix and needs to be resolved and released as soon as possible.
Fixes were commited over the past 2 days, that *should* fix this (it does in my own testing). fresh bluedevil (bluez5 branch) snapshot fedora packages are queue'd for updates-testing, other distros are encouraged to do the same.
*** Bug 329905 has been marked as a duplicate of this bug. ***