Hide Forgot
Description of problem: Each time the KDE (KF 5) "Software Updates" widget starts (or is started by hand), it exits with the following error message (notification): "Update error" "The task was forcibly canceled The task was canceled successfully and no packages were changed. The backend did not exit cleanly." Version-Release number of selected component (if applicable): PackageKit-1.1.4-1.fc25.x86_64 How reproducible: Always Steps to Reproduce: 1. Wait for Software Updates to start or start it by hand Actual results: Gets this error notification and nothing happens Expected results: Updates displayed and done Additional info: "pkcon -v update" always stops at 39% and nothing else happens. The system is up-to-date, thanks to dnf.
updating summary to mention generic 'pkcon update' failure mode too
The packagekit daemon crashes during system startup (see "journalctl -b") with a huge memory dump (memory corruption). Below is the status reported by "systemctl status packagekit" : ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled) Active: failed (Result: signal) since jeu. 2016-11-24 21:37:16 CET; 4min 33s ago Process: 2321 ExecStart=/usr/libexec/packagekitd (code=killed, signal=ABRT) Main PID: 2321 (code=killed, signal=ABRT) nov. 24 21:37:15 cm690a packagekitd[2321]: 7f5382ee2000-7f5382ee3000 r--p 00025000 fd:00 15748 /usr/lib64/ld-2. nov. 24 21:37:15 cm690a packagekitd[2321]: 7f5382ee3000-7f5382ee4000 rw-p 00026000 fd:00 15748 /usr/lib64/ld-2. nov. 24 21:37:15 cm690a packagekitd[2321]: 7f5382ee4000-7f5382ee5000 rw-p 00000000 00:00 0 nov. 24 21:37:15 cm690a packagekitd[2321]: 7ffc7c7b6000-7ffc7c7d7000 rw-p 00000000 00:00 0 [stack] nov. 24 21:37:15 cm690a packagekitd[2321]: 7ffc7c7e6000-7ffc7c7e8000 r--p 00000000 00:00 0 [vvar] nov. 24 21:37:15 cm690a packagekitd[2321]: 7ffc7c7e8000-7ffc7c7ea000 r-xp 00000000 00:00 0 [vdso] nov. 24 21:37:15 cm690a packagekitd[2321]: ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] nov. 24 21:37:16 cm690a systemd[1]: packagekit.service: Main process exited, code=killed, status=6/ABRT nov. 24 21:37:16 cm690a systemd[1]: packagekit.service: Unit entered failed state. nov. 24 21:37:16 cm690a systemd[1]: packagekit.service: Failed with result 'signal'.
I have the same issue. # pkcon -v get-updates 00:30:42 PackageKit Verbose debugging enabled (on console 1) 00:30:42 PackageKit filter=(null), filters=0 00:30:42 PackageKit adding state 0x564991b170d0 00:30:42 PackageKit role now get-updates Getting updates [ ] (0%) 00:30:42 PackageKit notify::connected [=========================] Loading cache [========= ] (39%) 00:30:43 PackageKit notify::connected The daemon crashed mid-transaction! # pkmon -v 00:30:37 PackageKit Verbose debugging enabled (on console 1) 00:30:37 PackageKit refreshing task list Transactions: [none] 00:30:37 PackageKit notify::connected daemon connected=1 00:30:37 PackageKit refreshing task list network status=online Daemon state: 'State: 0 repair-system /12169_aabadbca state[finished] exclusive[1] background[0] 1 repair-system /12170_baecbdcb state[finished] exclusive[1] background[0] ' 00:30:42 PackageKit emit transaction-list-changed 00:30:42 PackageKit current: /12171_daadbeec 00:30:42 PackageKit emit added: /12171_daadbeec 00:30:42 PackageKit added: /12171_daadbeec Transactions: 1 /12171_daadbeec Daemon state: 'State: 0 get-updates /12171_daadbeec state[running] exclusive[1] background[0] ' /12171_daadbeec allow_cancel 1 /12171_daadbeec percentage -1 00:30:42 PackageKit role now get-updates /12171_daadbeec role get-updates /12171_daadbeec status setup /12171_daadbeec status query /12171_daadbeec percentage 3 /12171_daadbeec status loading-cache /12171_daadbeec percentage 7 /12171_daadbeec percentage 12 /12171_daadbeec percentage 16 /12171_daadbeec percentage 21 /12171_daadbeec percentage 25 /12171_daadbeec percentage 30 /12171_daadbeec percentage 34 /12171_daadbeec percentage 39 00:30:43 PackageKit notify::connected daemon connected=0 # systemctl status packagekit ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled) Active: failed (Result: signal) since Fri 2017-01-20 00:30:43 CET; 1min 6s ago Process: 22843 ExecStart=/usr/libexec/packagekitd (code=killed, signal=ABRT) Main PID: 22843 (code=killed, signal=ABRT) Jan 20 00:30:43 omega packagekitd[22843]: 7f8ba551c000-7f8ba551d000 rw-p 00000000 00:00 0 Jan 20 00:30:43 omega packagekitd[22843]: 7f8ba551d000-7f8ba5543000 r--p 00000000 fd:01 2098397 /var/lib/rpm/Name Jan 20 00:30:43 omega packagekitd[22843]: 7f8ba5543000-7f8ba5545000 rw-p 00000000 00:00 0 Jan 20 00:30:43 omega packagekitd[22843]: 7f8ba5545000-7f8ba5546000 r--p 00025000 fd:01 526194 /usr/lib64/ld-2.24.so Jan 20 00:30:43 omega packagekitd[22843]: 7f8ba5546000-7f8ba5547000 rw-p 00026000 fd:01 526194 /usr/lib64/ld-2.24.so Jan 20 00:30:43 omega packagekitd[22843]: 7f8ba5547000-7f8ba5548000 rw-p 00000000 00:00 0 Jan 20 00:30:43 omega packagekitd[22843]: 7ffdae61b000-7ffdae63c000 rw-p 00000000 00:00 0 [stack] Jan 20 00:30:43 omega packagekitd[22843]: 7ffdae657000-7ffdae659000 r--p 00000000 00:00 0 [vvar] Jan 20 00:30:43 omega packagekitd[22843]: 7ffdae659000-7ffdae65b000 r-xp 00000000 00:00 0 [vdso] Jan 20 00:30:43 omega packagekitd[22843]: ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
I reported the PackageKit Daemon crashes via ABRT, see bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1418188 https://bugzilla.redhat.com/show_bug.cgi?id=1382900 Hope it helps.
Thanks Tomas. These both look like crashes in libsolv.
Another one: https://bugzilla.redhat.com/show_bug.cgi?id=1418574 This is the last, unless you ask for more :-).
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.