Version-Release number of selected component: PackageKit-0.8.15-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: g_thread_unref executable: /usr/libexec/packagekitd kernel: 3.12.5-302.fc20.i686+PAE runlevel: N 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
Created attachment 845765 [details] File: backtrace
Created attachment 845767 [details] File: cgroup
Created attachment 845768 [details] File: core_backtrace
Created attachment 845769 [details] File: dso_list
Created attachment 845770 [details] File: environ
Created attachment 845771 [details] File: exploitable
Created attachment 845772 [details] File: limits
Created attachment 845773 [details] File: maps
Created attachment 845774 [details] File: open_fds
Created attachment 845775 [details] File: proc_pid_status
Created attachment 845776 [details] File: var_log_messages
Another user experienced a similar problem: I was playing solitaire, and packagekitd popped up with an error. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: g_thread_unref executable: /usr/libexec/packagekitd kernel: 3.15.8-200.fc20.x86_64 package: PackageKit-0.8.17-1.fc20 reason: packagekitd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Packagekit really hasn't worked in months. Sometimes it throws an error. Mostly it just says that it can't update package X because package X isn't installed (it always is). reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: g_thread_unref executable: /usr/libexec/packagekitd kernel: 3.16.3-200.fc20.x86_64 package: PackageKit-0.8.17-1.fc20 reason: packagekitd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
*** This bug has been marked as a duplicate of bug 1057781 ***