Version-Release number of selected component: PackageKit-1.1.10-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/libexec/packagekitd crash_function: traverse_dirs executable: /usr/libexec/packagekitd journald_cursor: s=143cbdd2e09e404aa2975aa0bcd2368d;i=3f26;b=1fac05eed64a4eb2a833f695e7f5a15c;m=20f6ed48;t=56d0c28142d2a;x=a6e7972bfa067d85 kernel: 4.16.11-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 traverse_dirs at ../src/repo_write.c:951 #1 repo_write_filtered at ../src/dirpool.h:65 #2 repo_write at ../src/repo_write.c:2087 #3 write_main at /usr/src/debug/libdnf-0.11.1-3.fc28.x86_64/libdnf/dnf-sack.c:576 #4 rewrite_repos at /usr/src/debug/libdnf-0.11.1-3.fc28.x86_64/libdnf/dnf-sack.c:1773 #5 dnf_sack_make_provides_ready at /usr/src/debug/libdnf-0.11.1-3.fc28.x86_64/libdnf/dnf-sack.c:1805 #6 filter_provides_reldep at /usr/src/debug/libdnf-0.11.1-3.fc28.x86_64/libdnf/hy-query.c:684 #7 hy_query_apply at /usr/src/debug/libdnf-0.11.1-3.fc28.x86_64/libdnf/hy-query.c:1132 #8 hy_query_run_set at /usr/src/debug/libdnf-0.11.1-3.fc28.x86_64/libdnf/hy-query.c:1569 #9 dnf_utils_run_query_with_newest_filter at pk-backend-dnf.c:898 Potential duplicate: bug 1299170
Created attachment 1449771 [details] File: backtrace
Created attachment 1449772 [details] File: cgroup
Created attachment 1449773 [details] File: core_backtrace
Created attachment 1449774 [details] File: cpuinfo
Created attachment 1449775 [details] File: dso_list
Created attachment 1449776 [details] File: environ
Created attachment 1449777 [details] File: exploitable
Created attachment 1449778 [details] File: limits
Created attachment 1449779 [details] File: maps
Created attachment 1449780 [details] File: mountinfo
Created attachment 1449781 [details] File: open_fds
Created attachment 1449782 [details] File: proc_pid_status
Created attachment 1449783 [details] File: var_log_messages
*** Bug 1623457 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Happened shortly after wake up from sleep/suspend. I assume, during PK checking for updates. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/libexec/packagekitd crash_function: traverse_dirs executable: /usr/libexec/packagekitd journald_cursor: s=84e3bb5a6ae04073b516cf6f45744e22;i=c810d;b=0cc7fdf876d24dce94d87879ac7efe1a;m=20ba1780fd;t=57497aa2088cf;x=34512b5a7ab3f545 kernel: 4.17.18-200.fc28.x86_64 package: PackageKit-1.1.10-1.fc28 reason: packagekitd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.