Description of problem: During the system update apper displays "The task was canceled successfully and no packages were changed" even though the updates have been applied. Version-Release number of selected component (if applicable): apper 0.8.2-1.fc20 How reproducible: always Steps to Reproduce: 1. update your system via apper Additional info: there is even a typo in the message "canceled" instead of "cancelled"
Confirmed here too. apper-0.8.2-1.fc20.x86_64
Created attachment 894357 [details] Apper notification
Hi, The message behind the details button (part of the above message), tells that "the script was killed as the action was cancelled". journalctl: May 12 22:58:25 hp-x3430 systemd: Started PackageKit Daemon. May 12 22:58:30 hp-x3430 PackageKit: get-updates transaction /324_eceebbea from uid 1000 finished with success after 2366ms May 12 22:58:32 hp-x3430 PackageKit: get-updates transaction /325_eebadcdd from uid 1000 finished with success after 2445ms May 12 22:58:46 hp-x3430 PackageKit: update-packages transaction /327_ccedcbeb from uid 1000 finished with success after 3167ms May 12 22:58:46 hp-x3430 PackageKit: uid 1000 is trying to obtain org.freedesktop.packagekit.system-update auth (only_trusted:1) May 12 22:58:46 hp-x3430 PackageKit: uid 1000 obtained auth May 12 22:58:49 hp-x3430 yum[2235]: Updated: iproute-3.14.0-2.fc20.x86_64 May 12 22:58:50 hp-x3430 PackageKit: update-packages transaction /328_dedeccdb from uid 1000 finished with success after 4039ms May 12 22:58:51 hp-x3430 PackageKit: get-updates transaction /329_bacabcbb from uid 1000 finished with cancelled after 1227ms May 12 22:58:52 hp-x3430 PackageKit: get-updates transaction /330_edeabebb from uid 1000 finished with success after 1252ms May 12 22:58:55 hp-x3430 PackageKit: get-updates transaction /331_ebbadbda from uid 1000 finished with success after 2508ms Hope this will give a clue were the issue might be. Martin Kho
May 13 11:40:32 localhost.localdomain PackageKit[30171]: get-updates transaction /1789_bbaebdcd from uid 1000 finished with cancelled after 314ms May 13 11:40:38 localhost.localdomain PackageKit[30171]: get-updates transaction /1790_deebedec from uid 1000 finished with success after 6022ms May 13 11:40:40 localhost.localdomain PackageKit[30171]: get-updates transaction /1791_ceacddba from uid 1000 finished with success after 1583ms ~
> there is even a typo in the message "canceled" instead of "cancelled" "canceled" is correct American English, "cancelled" is the British spelling.
Confirmed here too. Strangely I manage two other F20 installations and just this one (which has been upgraded since F15 or F16) shows the issue.
I have 3 systems, one was updated from F19 with fedup, the other 2 are clean installs. One of those is my main system, which has many things installed, the other two are mostly there as backups, and are pretty minimal installations (one a clean install, the other is the updated system). All 3 show this problem, but the main system does it almost all the time, the other systems much less so. I have not yet noticed a corrolation with any special package(s) that do or do not cause the error, but will keep my eyes open.
I get this error occasionally, and haven't been able to identify any corrolations. However, it seems to me that the message is in error and that all the packages *are* updated, despite the message.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.