Version-Release number of selected component: kdelibs-4.11.3-1.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: kded4 crash_function: KCrash::defaultCrashHandler executable: /usr/bin/kded4 kernel: 3.11.7-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 21446 Truncated backtrace: Thread no. 1 (10 frames) #1 KCrash::defaultCrashHandler at /usr/src/debug/kdelibs-4.11.3/kdeui/util/kcrash.cpp:346 #3 findNode at /usr/include/QtCore/qmap.h:483 #4 contains at /usr/include/QtCore/qmap.h:555 #5 BlueDevil::Adapter::deviceForUBI at /usr/src/debug/libbluedevil-2.0/bluedevil/bluedeviladapter.cpp:190 #6 BluezAgent::RequestConfirmation at /usr/src/debug/bluedevil-2.0.0/src/daemon/kded/bluezagent.cpp:128 #7 BluezAgent::qt_static_metacall at /usr/src/debug/bluedevil-2.0.0/x86_64-redhat-linux-gnu/src/daemon/kded/moc_bluezagent.cpp:81 #8 qt_static_metacall at /usr/src/debug/bluedevil-2.0.0/x86_64-redhat-linux-gnu/src/daemon/kded/moc_bluezagent.cpp:123 #9 BluezAgent::qt_metacall at /usr/src/debug/bluedevil-2.0.0/x86_64-redhat-linux-gnu/src/daemon/kded/moc_bluezagent.cpp:124 #10 QDBusConnectionPrivate::deliverCall at qdbusintegrator.cpp:951 #11 QDBusConnectionPrivate::activateCall at qdbusintegrator.cpp:856
Created attachment 820534 [details] File: backtrace
Created attachment 820535 [details] File: cgroup
Created attachment 820536 [details] File: core_backtrace
Created attachment 820537 [details] File: dso_list
Created attachment 820538 [details] File: environ
Created attachment 820539 [details] File: limits
Created attachment 820540 [details] File: maps
Created attachment 820541 [details] File: open_fds
Created attachment 820542 [details] File: proc_pid_status
Created attachment 820543 [details] File: var_log_messages
I'm hitting this one too after loading bluez-5.12-1.fc20.x86_64 to test the fix for bz 1027365.
Created attachment 835557 [details] backtrace
*** Bug 1030590 has been marked as a duplicate of this bug. ***
*** Bug 1043544 has been marked as a duplicate of this bug. ***
*** Bug 1045653 has been marked as a duplicate of this bug. ***
*** Bug 1046001 has been marked as a duplicate of this bug. ***
This should be fixed by recent update, https://admin.fedoraproject.org/updates/FEDORA-2013-23248/bluedevil-2.0.0-0.5.20131128.fc20,libbluedevil-2.0-0.2.20131113.fc20 (now in stable updates).
Uh, no. This was fixed upstream on December 19, it can't be fixed in the November 12 snapshot. You need to queue the latest snapshot, which should fix all these crashes.
libbluedevil-2.0-0.4.20131220.fc20, bluedevil-2.0.0-0.8.20131219.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/FEDORA-2013-23719/libbluedevil-2.0-0.4.20131220.fc20,bluedevil-2.0.0-0.8.20131219.fc20
Package bluedevil-2.0.0-0.11.rc1.fc20, libbluedevil-2.0-0.6.rc1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing bluedevil-2.0.0-0.11.rc1.fc20 libbluedevil-2.0-0.6.rc1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-23719/bluedevil-2.0.0-0.11.rc1.fc20,libbluedevil-2.0-0.6.rc1.fc20 then log in and leave karma (feedback).
bluedevil-2.0.0-0.11.rc1.fc20, libbluedevil-2.0-0.6.rc1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Please keep this bug closed, I can assure you that THIS crash is fixed. The crash in bug #1048063 has a different backtrace according to the faf link. Please attach a backtrace with debugging information to that bug.