Description of problem: No idea. A notification about a crash in the background shortly after logging in. Version-Release number of selected component: PackageKit-0.9.4-4.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: /usr/libexec/packagekitd executable: /usr/libexec/packagekitd kernel: 3.16.1-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #2 munmap at /lib64/ld-linux-x86-64.so.2 #3 _dl_unmap at /lib64/ld-linux-x86-64.so.2 #4 _dl_close_worker.part.0 at /lib64/ld-linux-x86-64.so.2 #5 _dl_close at /lib64/ld-linux-x86-64.so.2 #6 _dl_catch_error at /lib64/ld-linux-x86-64.so.2 #7 _dlerror_run at /lib64/libdl.so.2 #8 dlclose at /lib64/libdl.so.2 #9 _g_module_close.isra.0 at /lib64/libgmodule-2.0.so.0 #10 g_module_close at /lib64/libgmodule-2.0.so.0
Created attachment 930098 [details] File: backtrace
Created attachment 930099 [details] File: cgroup
Created attachment 930100 [details] File: core_backtrace
Created attachment 930101 [details] File: dso_list
Created attachment 930102 [details] File: environ
Created attachment 930103 [details] File: exploitable
Created attachment 930104 [details] File: limits
Created attachment 930105 [details] File: maps
Created attachment 930106 [details] File: open_fds
Created attachment 930107 [details] File: proc_pid_status
Created attachment 930108 [details] File: var_log_messages
Another user experienced a similar problem: This crash happens fairly regularly when doing package updates. I update most often with dnf, but I've seen this crash occur using yum, and I think even apper. Not sure about the Gnome software package. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: /usr/libexec/packagekitd executable: /usr/libexec/packagekitd kernel: 3.16.1-300.fc21.x86_64 package: PackageKit-0.9.4-4.fc21 reason: packagekitd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
The backtrace is missing debug symbols. Please do 'debuginfo-install PackageKit' and let ABRT file a new bug when it crashes again. Thanks!
> The backtrace is missing debug symbols. Blame ABRT or whatever else made it impossible to find/install the needed -debuginfo packages. I raise doubts that debuginfo-install would have succeeded.
I filed https://github.com/abrt/abrt/issues/851 for the ABRT issue
Once TC4 is released and I'm able to resume testing F21 on my laptop, I remember reading about this issue and that a workaround was supposedly done to fix it. So - if it does still occur then it should be possible to re-report with the debuginfo.
*** Bug 1135686 has been marked as a duplicate of this bug. ***