Version-Release number of selected component: PackageKit-0.9.4-4.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: vasprintf executable: /usr/libexec/packagekitd kernel: 3.16.1-301.fc21.x86_64+debug runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 vasprintf at /usr/include/bits/stdio2.h:210 #3 g_vasprintf at gprintf.c:316 #4 g_strdup_vprintf at gstrfuncs.c:507 #5 g_error_new_valist at gerror.c:388 #6 g_set_error at gerror.c:558 #7 hif_source_update at hif-source.c:1068 #8 pk_backend_refresh_source at pk-backend-hif.c:1298 #9 pk_backend_refresh_cache_thread at pk-backend-hif.c:1384 #10 pk_backend_job_thread_setup at pk-backend-job.c:791 #11 g_thread_proxy at gthread.c:764 Potential duplicate: bug 700904
Created attachment 933072 [details] File: backtrace
Created attachment 933073 [details] File: cgroup
Created attachment 933074 [details] File: core_backtrace
Created attachment 933075 [details] File: dso_list
Created attachment 933076 [details] File: environ
Created attachment 933077 [details] File: limits
Created attachment 933078 [details] File: maps
Created attachment 933079 [details] File: open_fds
Created attachment 933080 [details] File: proc_pid_status
Created attachment 933081 [details] File: var_log_messages
Created attachment 933082 [details] File: exploitable
Another user experienced a similar problem: I am not certain (since it's been several days) which action caused it but I remember trying to install either rpmfusion repository rpm file or google-chrome rpm file. The "install" progress kept spinning and eventually crashed. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: vasprintf executable: /usr/libexec/packagekitd kernel: 3.17.4-301.fc21.x86_64 package: PackageKit-1.0.3-2.fc21 reason: packagekitd killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
*** This bug has been marked as a duplicate of bug 1174255 ***