Description of problem: Crash every time I run `pkcon refresh`. Version-Release number of selected component: PackageKit-1.1.6-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: pk_backend_refresh_cache_thread executable: /usr/libexec/packagekitd journald_cursor: s=0fa1f239b1794f89889dfeb23027acbc;i=1f48b;b=3d1f6cbaeedc401f8162bdd9c7ff304e;m=e106870ee;t=551c87c4b8b39;x=7ced7cc4e49b472a kernel: 4.11.4-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (3 frames) #0 pk_backend_refresh_cache_thread at pk-backend-dnf.c:1654 #1 pk_backend_job_thread_setup at pk-backend-job.c:813 #2 g_thread_proxy at gthread.c:784 Potential duplicate: bug 1114207
Created attachment 1287104 [details] File: backtrace
Created attachment 1287105 [details] File: cgroup
Created attachment 1287106 [details] File: core_backtrace
Created attachment 1287107 [details] File: cpuinfo
Created attachment 1287108 [details] File: dso_list
Created attachment 1287109 [details] File: environ
Created attachment 1287110 [details] File: exploitable
Created attachment 1287111 [details] File: limits
Created attachment 1287112 [details] File: maps
Created attachment 1287113 [details] File: open_fds
Created attachment 1287114 [details] File: proc_pid_status
Created attachment 1287115 [details] File: var_log_messages
Similar problem has been detected: Logged into my computer. Notification was displayed that PackageKit quit unexpectedly. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: pk_backend_refresh_cache_thread executable: /usr/libexec/packagekitd journald_cursor: s=fc22d2cbec5e4b95af3cda0296001c74;i=177a6a;b=7f5a6e0a1ec84c1aa930e81bb9134963;m=3c68dfa8;t=551bfd6e9384f;x=27d24d6edab72c26 kernel: 4.11.3-302.fc26.x86_64 package: PackageKit-1.1.6-1.fc26 reason: packagekitd killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1461362 has been marked as a duplicate of this bug. ***
Are there any critical warnings in the journal? I can't see how dnf_state_done() can be returning FALSE and not setting the error. Thanks.
Similar problem has been detected: Logged in to my computer and a crash notification appeared. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: pk_backend_refresh_cache_thread executable: /usr/libexec/packagekitd journald_cursor: s=fc22d2cbec5e4b95af3cda0296001c74;i=17c0a3;b=44852a3e95b84cdf8a663363dd5faa62;m=a5c7eb60;t=551e880e975fa;x=26fd60f3d0caba7c kernel: 4.11.4-300.fc26.x86_64 package: PackageKit-1.1.6-1.fc26 reason: packagekitd killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 0
PackageKit-1.1.6-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-7f91d69342
*** Bug 1462366 has been marked as a duplicate of this bug. ***
PackageKit-1.1.6-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-7f91d69342
PackageKit-1.1.6-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1464556 has been marked as a duplicate of this bug. ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days