Hide Forgot
Description of problem: When system upgrade fails (in my case due to bug 1336459), the user is not informed about it in any way. The computer reboots, but there's no popup saying "System upgrade failed" (I'd expect something similar to "Updates were installed" after a successful offline update), and if you run gnome-software, there are no error details. There's just a standard banner "Fedora 24 now available". The user has no information why it failed. The user might not even understand it failed. I can use pkcon to learn the failure status, but that of course is not fit for general users: $ pkcon offline-status Status: Failed ErrorCode:failed-initialization ErrorDetails:cannot download Packages/l/libdiscid-0.6.1-5.fc24.x86_64.rpm to /var/cache/PackageKit/24/metadata/fedora/packages/: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-24&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org] Version-Release number of selected component (if applicable): PackageKit-1.1.1-2.fc23 libgusb-0.2.9-1.fc23 libhif-0.2.2-4.fc23 gnome-software-3.20.3-1.fc23 libappstream-glib-0.5.14-1.fc23 json-glib-1.2.0-1.fc23 How reproducible: seems always Steps to Reproduce: 1. make a system upgrade fail (e.g. use bug 1336459) 2. see no information about reboot anywhere
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
Tell me if you have time to look into this and I'll re-test and provide fresh logs if needed.
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.