Description of problem: The Download of the Fedora 29 update does not work Version-Release number of selected component (if applicable): Fedora 28 How reproducible: Always Steps to Reproduce: 1. Open the application "Software" 2. Change to the "Update" tab 3. Click on "Download" in the "Fedora 29 Now Available" Actual results: Downloads for a short time and then shows "Unable to upgrade to Fedora 29" Expected results: Upgrade actually works Additional info:
Created attachment 1503288 [details] screenshot
Me to I have same issue
Exact same issue. Tried on multiple days and after restarts. Happy to provide more info is someone can tell me which log to find it in.
Is there anything relevant in journalctl?
> Is there anything relevant in journalctl? perhaps. What would I filter it by to narrow it down?
Try 'journalctl /usr/bin/gnome-software /usr/libexec/packagekitd'
This looks like it might be helpful: ` PackageKit[2350]: upgrade-system transaction /1980_adacdabe from uid 1000 finished with need-untrusted after 22697ms gnome-software[3201]: failed to call gs_plugin_app_upgrade_download on packagekit-upgrade: could not do untrusted question as no klass support ` An issue with having added other software repos perhaps?
Ahh, yes, maybe you have a repo that has gpgcheck=0? I think this may be causing issues with packagekit/gnome-software.
sorry I'm new to Fedora and I don't know where to look for this. I don't see anything obvious in /etc/dnf. A `sudo dnf repolist` gives: ``` repo id repo name status *fedora Fedora 28 - x86_64 57,327 home_mhsabbagh home:mhsabbagh (Fedora_28) 2 *rpmfusion-free RPM Fusion for Fedora 28 - Free 563 *rpmfusion-free-updates RPM Fusion for Fedora 28 - Free - Updates 257 *rpmfusion-nonfree RPM Fusion for Fedora 28 - Nonfree 203 *rpmfusion-nonfree-updates RPM Fusion for Fedora 28 - Nonfree - Updates 92 slack slack 44 sublime-text Sublime Text - x86_64 - Stable 2 *updates Fedora 28 - x86_64 - Updates 19,958 ```
You could try to temporarily disable some of the extra repos (home_mhsabbagh, slack, sublime-text) and see if the error goes away (just as a temporary workaround, this is something that gnome-software should handle better). gnome-software has the Software Repositories dialog in the app menu where you can disable repos.
Same issue here with error message below : Error running transaction: package pgdg-fedora10-10-4.noarch is already installed.
Hm, I wonder why it wants to reinstall pgdg-fedora10-10-4.noarch. Sounds like there are issues in packagekit with handling packages that changed, but didn't correctly bump version (such as pgdg-fedora10-10-4.noarch).
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.