Discover couldnt install a library after it rebooted pc to install updates

Ask Fedora
1

earlier today i ran discover because it told me there was available some updates

i let it download them and i restarted pc so it could install them, nothing weird, all finished as expected

when i was back in kde desktop i was warned about some library that could not be installed, it told me it could try to fix the problem, i clicked on the option but it told me it couldnt fix the problem and it cleared the notification saying the name of the library

i dont know how to check what library was the one that couldnt be updated, system is doing just fine

i was checking the dnf pages but nothing mentions check for broken packages or something like that, discover is the same

what would be the best way to see what library was left behind and how to fix it, as i mentioned, all is just fine here, so this is to avoid future problems, i imagine fedora 45 is not far, so i dont want issues when moving to it

2

If you run sudo dnf update --refresh does it report that it can do an update for you?
If it reports an error please post the whole of the output from dnf here.

3

Was it the same error as this by any chance?

4

today yes, it can do a update, because there are new packages, yesterday i didnt had any after the library that failed, but the packages of today are all different,
yesterday as things like librewolf, today is libreoffice and others, update reported no problems at all from 34 packages downloaded

cant remember the name, so

5

from what i have read, there is no way to know if a file is damaged or missing from dnf or discover?

6

You can do:

rpm -V firefox

to verify the files installed for package firefox (obviously substitute whatever package your interested in).

The output will show a code for any file that fails verification - this StackExchange answer has a useful list of the codes.

7

the problem is, that i dont know which one is the program with the problematic library

if i have to do it manually, i wont do it

8

rpm -Va then to check all packages. Could be a big output if there was a wide problem, but let’s see.

9

thank you for your reply

i ran it as normal user and took like 3 minutes and complained alot, then i ran it as superuser and got this

.5....T.  c /etc/printcap
.M.......    /boot/efi/EFI/BOOT
.......T.  c /etc/sysconfig/nftables.conf
.......T.  c /etc/sysconfig/kernel
.M.......  g /boot/efi/EFI/fedora/BOOTX64.CSV
.M.......  g /boot/efi/EFI/fedora/BOOTIA32.CSV
.......T.  c /etc/sysconfig/raid-check
.......T.    /boot/efi/System/Library/CoreServices/SystemVersion.plist
.......T.    /boot/efi/mach_kernel
.....UG..  g /var/run/pcscd
.......T.  c /etc/sysconfig/run-parts
.......T.  c /etc/sysconfig/crond
.......T.  c /etc/sysconfig/wpa_supplicant
.......T.  c /etc/sysconfig/o2cb
.......T.  c /etc/sysconfig/man-db
.......T.  c /etc/sysconfig/qemu-ga
.......T.  c /etc/sysconfig/atd
S.5....T.  c /etc/sysconfig/livesys
.M.......    /var/lib/fwupd
.M.......  c /boot/efi/EFI/fedora/grub.cfg
.M.......  c /boot/efi/EFI/fedora/grub.cfg
.M.......  g /run/thermald/thermald.pid
S.5....T.  c /etc/plasmalogin.conf
......G..    /run/plasmalogin
.M.......    /var/lib/plasmalogin

not sure what are those letters on the left

10

The StackExchange link in the earlier post explains them.

I doubt that any of these are genuine problems though - these all look like files that can legitimately modified compared to the initial version that the package installs.

11

when you wrote that i imagined something different and didnt checked

the only ones that could be a problem is the wpa and kernel i think

the rest are cfgs or similar text files

not knowing more, seems like all is well here

well, for a couple weeks, i will move to f45 as soon as i can, not sure if upgrade or just iso from usb

12

Maybe check:
/var/lib/PackageKit/offline-update-completed

If it’s the libdnf plugin issue.

Edit: Adding the upsteam issue

13

it comes as folder doesnt exist

in /var/lib/PackageKit/ all i find is a transactions.db file