Description of problem: Discover fails to refresh the pending updates if some configured yum repos are unreachable (e.g. because they are on a corporate VPN and you're not currently on that VPN). If there are packages that Discover thinks need to be updated, but have actually been updated manually using dnf, then Discover fails to remove them from the list of updates. Hitting refresh shows an error about an unreachable repo, and then the list of updates is not changed. So updates that are actually already installed are still shown as pending. Alternatively, if there are updates available from a repo that is on the VPN, but you disconnect from the VPN and refresh, the uninstallable updates are still shown. Version-Release number of selected component (if applicable): plasma-discover-5.24.3-1.fc34.x86_64 How reproducible: Always Steps to Reproduce: 1. Configure a yum repo with a bad URL that cannot be reached. 2. Try to refresh Discover updates 3. Be annoyed. Actual results: Discover fails to refresh the updates. Expected results: An unreachable repo should be gracefully skipped (as DNF and PackageKit do). It should not break Discover so that it can't show a valid set of available updates. Additional info:
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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. Thank you for reporting this bug and we are sorry it could not be fixed.