Updates failed / Repair failed

Ask Fedora
,
1

Today discover showed a message to install updates after restart.After I restart I see a discover notification that updates failed and that repair failed. discover give no hints what this caused this or how to continue from here.

The system works as I’m typing these lines.

EDIT: than if I update with dnf up the proton OpenPGP key is updated and the update works. But after reboot discover still notifies about a brokend update.

2

You are not the first person to notice this issue with lack of info.

Might be good feedback to giive the KDE folks over at https://discuss.kde.org/
It will be them who need to fix this.

3

Same thing happened to me today. Discover had System Updates (289 packages to upgrade). I chose to ‘Update All’ and restarted. When I logged back in, the system tray notification stated “Failed Offline Update” with an option to “Repair System”. Clicked “Repair System” button then recived another notification stating “Repair Failed”. I then tried to update again via Discover, failed again.

Next I did an update via terminal - sudo dnf update. All updates went through, restarted my system, and no updates show in Discover.

Any ideas why this could have failed via Discover? Is it best to just update via terminal?

4

None. Please report to the kde folks over at https://discuss.kde.org/

I use the terminal method personally because its precise and the error messages are actionable.

In my case I automated the updates and keep a record of the update logs.

5

I like the idea of creating an update log. I would like the current version and update version of each package in that is being updated.

I just used the following command:
sudo dnf update | tee ~/update_log_$(date +%Y%m%d.%H%M%S).txt

Looks like it gives me to version # that is being replaced and the version # that is be installed. Any ideas why the ‘from’ repo is showing ?

Here is an example:

`breeze-gtk-common                           noarch 0:6.6.5-1.fc44            updates    178.0 KiB
   replacing breeze-gtk-common               noarch 0:6.6.4-1.fc44            <unknown>  178.0 KiB
6

You need to capture stderr and well as stdout.

sudo dnf update |& tee ~/update_log_$(date +%Y%m%d.%H%M%S).txt

That log will show errors and progress nicely.
Full details of the update that you apply will be in the dnf history.
See dnf history --help for how to view the history.