Description of problem: $ sudo pkcon refresh force Version-Release number of selected component: PackageKit-1.1.5-0.1.20161221.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repodata_add_dirnumnum executable: /usr/libexec/packagekitd global_pid: 1676 kernel: 4.8.15-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #4 repodata_add_dirnumnum at /usr/src/debug/libsolv-0.6.24/src/repodata.c:2736 #5 solvable_copy_cb at /usr/src/debug/libsolv-0.6.24/ext/repo_rpmdb.c:1648 #6 repodata_search at /usr/src/debug/libsolv-0.6.24/src/repodata.c:1072 #7 solvable_copy at /usr/src/debug/libsolv-0.6.24/ext/repo_rpmdb.c:1719 #8 repo_add_rpmdb at /usr/src/debug/libsolv-0.6.24/ext/repo_rpmdb.c:2020 #9 repo_add_rpmdb_reffp at /usr/src/debug/libsolv-0.6.24/ext/repo_rpmdb.c:2085 #10 dnf_sack_load_system_repo at /usr/src/debug/PackageKit-1.1.5-20161221/libdnf-367545629cc01a8e622890d89bd13d062ce60d7b/libdnf/dnf-sack.c:1311 #11 dnf_utils_create_sack_for_filters at pk-backend-dnf.c:705 #12 pk_backend_search_thread at pk-backend-dnf.c:941 #13 pk_backend_job_thread_setup at pk-backend-job.c:813
Created attachment 1239048 [details] File: backtrace
Created attachment 1239049 [details] File: cgroup
Created attachment 1239050 [details] File: core_backtrace
Created attachment 1239051 [details] File: dso_list
Created attachment 1239052 [details] File: environ
Created attachment 1239053 [details] File: limits
Created attachment 1239054 [details] File: maps
Created attachment 1239055 [details] File: mountinfo
Created attachment 1239056 [details] File: namespaces
Created attachment 1239057 [details] File: open_fds
Created attachment 1239058 [details] File: proc_pid_status
Created attachment 1239059 [details] File: var_log_messages
Similar problem has been detected: pkcon search sublime reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repodata_add_dirnumnum executable: /usr/libexec/packagekitd global_pid: 2669 kernel: 4.9.5-200.fc25.x86_64 package: PackageKit-1.1.5-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: packagekitd killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
`abrt` rejected my error report "because the backtrace is unusable", but I did some limited debugging of my own, and found a few clues that might be helpful in narrowing down the root cause: 1. I've found some earlier `packagekitd` bug that had to do with distribution updates and 'Exclude=' entries. I have none in my repositories' configuration. 2. `dnf clean all` didn't change anything. 3. The same problem persisted after moving (a) most, except the base Fedora repositories and (b) all of the .repo files out of `/etc/yum.repos.d/`, and multiple cycles of `dnf update`/`pkcon refresh` (`dnf` releases the leftover locks after a `packagekitd` crash). 4. Incidentally, the repository that was handled while the crash happened was the virtual(?) '@System' repository. 5. `dnf list installed | grep @System` returned the following list: aksusbd.i386 7.40-1 @System geoclue.x86_64 0.12.99-8.fc23 @System libmusicbrainz.x86_64 2.1.5-20.fc23 @System libsilc.x86_64 1.1.10-14.fc23 @System shared-desktop-ontologies.noarch 0.11.0-4.fc23 @System telepathy-haze.x86_64 0.8.0-3.fc22 @System telepathy-salut.x86_64 0.8.1-8.fc23 @System Only two of these I remember installing directly. The others are a bit of a mystery to me, but none of these seem relevant to me in my daily use. So I removed these packages (very little dependencies had to be removed, and nothing worrying), but the problem remains. `pkcon refresh` leads to SIGABRT. Another `dnf clean all` didn't help either.
(In reply to Itzik Ephraim from comment #14) > `abrt` rejected my error report "because the backtrace is unusable", but I > did some limited debugging of my own, and found a few clues that might be > helpful in narrowing down the root cause: > > 1. I've found some earlier `packagekitd` bug that had to do with > distribution updates and 'Exclude=' entries. I have none in my repositories' > configuration. > > 2. `dnf clean all` didn't change anything. > > 3. The same problem persisted after moving (a) most, except the base Fedora > repositories and (b) all of the .repo files out of `/etc/yum.repos.d/`, and > multiple cycles of `dnf update`/`pkcon refresh` (`dnf` releases the leftover > locks after a `packagekitd` crash). > > 4. Incidentally, the repository that was handled while the crash happened > was the virtual(?) '@System' repository. > > 5. `dnf list installed | grep @System` returned the following list: > aksusbd.i386 7.40-1 @System > geoclue.x86_64 0.12.99-8.fc23 @System > libmusicbrainz.x86_64 2.1.5-20.fc23 @System > libsilc.x86_64 1.1.10-14.fc23 @System > shared-desktop-ontologies.noarch 0.11.0-4.fc23 @System > telepathy-haze.x86_64 0.8.0-3.fc22 @System > telepathy-salut.x86_64 0.8.1-8.fc23 @System > > Only two of these I remember installing directly. The others are a bit of a > mystery to me, but none of these seem relevant to me in my daily use. > So I removed these packages (very little dependencies had to be removed, and > nothing worrying), but the problem remains. `pkcon refresh` leads to > SIGABRT. Another `dnf clean all` didn't help either. Forgot to mention: Fedora 25 Kernel: 4.9.9-200.fc25.x86_64 PackageKit.x86_64 1.1.5-1.fc25 libsolv.x86_64 0.6.26-1.fc25 hawkey.x86_64 0.6.3-6.2.fc25 python3-hawkey.x86_64 0.6.3-6.2.fc25 dnf.noarch 1.1.10-5.fc25 python3-dnf.noarch 1.1.10-5.fc25
OK, I have some progress here. It's actually solved for me now, but I did too many things at once and now I don't know what it was exactly: 1. Removed the @System packages (see Comment #15). 2. `dnf clean all` 3. `dnf update --refresh` 4. `rpmdb --rebuilddb` 5. `pkcon -p -v refresh` No errors! (To be accurate, I ran all of the above with `sudo`)
I was getting the following error on the Updates widget: "The task was forcibly canceled The task was canceled successfully and no packages were changed. The backend did not exit cleanly." Solved with 'rpmdb --rebuilddb'.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.