Bug 1027366

Summary: bluedevil/kded crashes when other device attempts to pair
Product: [Fedora] Fedora Reporter: Jozef Mlich <jmlich>
Component: bluedevilAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: brunano21, cunio, danofsatx, dvratil, hhorak, jgrulich, jreznik, kcleveng, kevin, ltinkl, rdieter, rnovacek, smparrish, than
Target Milestone: ---Keywords: Reopened, Triaged, Upstream
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8aaf176904e8220298b82a8df18d6c4f1b6c648d
Whiteboard: abrt_hash:2debd36b2fe10af91d2ef76d37e71482fbb357a2
Fixed In Version: bluedevil-2.0.0-0.11.rc1.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-04 00:52:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
backtrace none

Description Jozef Mlich 2013-11-06 16:35:22 UTC 
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
Comment 1 Jozef Mlich 2013-11-06 16:35:34 UTC 
Created attachment 820534 [details]
File: backtrace
Comment 2 Jozef Mlich 2013-11-06 16:35:39 UTC 
Created attachment 820535 [details]
File: cgroup
Comment 3 Jozef Mlich 2013-11-06 16:35:47 UTC 
Created attachment 820536 [details]
File: core_backtrace
Comment 4 Jozef Mlich 2013-11-06 16:35:52 UTC 
Created attachment 820537 [details]
File: dso_list
Comment 5 Jozef Mlich 2013-11-06 16:35:57 UTC 
Created attachment 820538 [details]
File: environ
Comment 6 Jozef Mlich 2013-11-06 16:36:02 UTC 
Created attachment 820539 [details]
File: limits
Comment 7 Jozef Mlich 2013-11-06 16:36:08 UTC 
Created attachment 820540 [details]
File: maps
Comment 8 Jozef Mlich 2013-11-06 16:36:13 UTC 
Created attachment 820541 [details]
File: open_fds
Comment 9 Jozef Mlich 2013-11-06 16:36:18 UTC 
Created attachment 820542 [details]
File: proc_pid_status
Comment 10 Jozef Mlich 2013-11-06 16:36:26 UTC 
Created attachment 820543 [details]
File: var_log_messages
Comment 11 Dan Mossor [danofsatx] 2013-12-12 02:51:22 UTC 
I'm hitting this one too after loading bluez-5.12-1.fc20.x86_64 to test the fix for bz 1027365.
Comment 12 Dan Mossor [danofsatx] 2013-12-12 02:52:36 UTC 
Created attachment 835557 [details]
backtrace
Comment 13 Rex Dieter 2013-12-19 15:03:09 UTC 
*** Bug 1030590 has been marked as a duplicate of this bug. ***
Comment 14 Rex Dieter 2013-12-19 15:03:23 UTC 
*** Bug 1043544 has been marked as a duplicate of this bug. ***
Comment 15 Kevin Kofler 2013-12-20 23:56:41 UTC 
*** Bug 1045653 has been marked as a duplicate of this bug. ***
Comment 16 Rex Dieter 2013-12-23 09:30:18 UTC 
*** Bug 1046001 has been marked as a duplicate of this bug. ***
Comment 17 Rex Dieter 2013-12-23 09:39:39 UTC 
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).
Comment 18 Kevin Kofler 2013-12-23 11:58:24 UTC 
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.
Comment 19 Fedora Update System 2013-12-23 12:03:47 UTC 
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
Comment 20 Fedora Update System 2013-12-25 02:37:19 UTC 
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).
Comment 21 Fedora Update System 2013-12-28 02:10:34 UTC 
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.
Comment 23 Kevin Kofler 2014-01-04 00:52:29 UTC 
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.