Version-Release number of selected component: PackageKit-0.8.16-1.fc21 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: g_thread_unref executable: /usr/libexec/packagekitd kernel: 3.14.0-0.rc0.git3.1.fc21.x86_64 runlevel: 3 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (3 frames) #0 g_thread_unref at gthread.c:760 #1 pk_backend_job_thread_setup at pk-backend-job.c:795 #2 g_thread_proxy at gthread.c:798 Potential duplicate: bug 1048590
Created attachment 855199 [details] File: backtrace
Created attachment 855200 [details] File: cgroup
Created attachment 855201 [details] File: core_backtrace
Created attachment 855202 [details] File: dso_list
Created attachment 855203 [details] File: environ
Created attachment 855204 [details] File: exploitable
Created attachment 855205 [details] File: limits
Created attachment 855206 [details] File: maps
Created attachment 855207 [details] File: open_fds
Created attachment 855208 [details] File: proc_pid_status
Created attachment 855209 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
This looks like a race in pk_backend_job_thread_create: pk_backend_job_thread_setup may run and try to free the thread object before g_thread_new has returned. The fix should be simple: Just don't store the thread object inside the job; just do g_thread_unref (g_thread_new (...));
*** Bug 1048590 has been marked as a duplicate of this bug. ***
Thanks! Fixed upstream in https://github.com/hughsie/PackageKit/commit/c0d0481767a2b11ab0750d51474008a38a503a6e
Should be fixed in PackageKit-1.0.9-1.fc22