Fedora-43Beta

[chrisofbristol (Chris Bristol)]

I’m not sure whether it is appropriate to post about a beta here, but I’ve been getting an error message on startup (which I really should have copied), and YouTube won’t play on Firefox 142.0.1, so I’m trying to “update software”. I keep getting the same popup error message:

Download Unsigned Software?

failed to parse PKI file /var/cache/PackageKit/43/metadata/rpmfusion-nonfree-steam-43-x86_64/RPM-GPG-KEY-rpmfusion-nonfree-fedora-43

It just repeats whether I choose Cancel or Download.

[gnwiii (George N. White III)]

Might have the same underlying cause as https://discussion.fedoraproject.org/t/package-operations-in-gnome-software-fail-packagekitd-uses-a-lot-of-cpu-and-spams-the-journal-with-errors-if-google-chrome-repo-is-enabled/164645:

@adamwill

Cause

This problem is caused by changes in RPM 6 (a pre-release of which is included in Fedora 43 Beta). Specifically, RPM 6 now automatically imports these ‘subkeys’ when the main key is imported. RPM 4 did not do so. libdnf also attempts to import the subkeys after importing the main key. So now, libdnf imports the main key, RPM automatically imports the subkeys, then libdnf also tries to import the subkeys, and this seems to cause the errors.

[chrisofbristol (Chris Bristol)]

Bugzilla report: #2372978

$ pkcon repo-disable google-chrome

$ sudo rm /var/cache/PackageKit/43/metadata/google-chrome-43-x86_64/ -rf

# reboot

Did this, [edit](YouTube now works), but it hasn’t made any difference to the update.

You can also try updating libdnf and related packages from this test build which has the proposed fix for this problem included (then restart packagekit.service and kill running gnome-software processes, or reboot).

Sorry I don’t read Chinese . Could someone tell me what to do in simple terms please?

[thephatlee (Marko Jokinen)]

I got similar error on google chrome repo and workaround on that was to edit repo file and add # as first on each line so it is disabled just not removed.

Repo files can be found /etc/yum.repos.d/ and sudo nano repo name here

[chrisofbristol (Chris Bristol)]

I did

sudo gedit /etc/yum.repos.d/google-chrome.repo

and put in the hashes. It made no difference, so I have returned it to what it was.
I’ve caught the startup error now, it is:

[computersavvy (Jeff V)]

@thephatlee

workaround on that was to edit repo file and add # as first on each line so it is disabled

It is not necessary to edit the repo file at all (though if you do the line enabled=1 should be changed to enabled=0). On the cli when using dnf the option --disablerepo <reponame> will disable that repo while that command is running and does not require editing any files.

With dnf5 (in use since [I think] f41) there is another command that can be used to enable or disable repos without editing any files.
sudo dnf --setopt=<reponame>.enabled=0 will disable the repo.

See the man page for dnf to find out what all is possible.

[chrisofbristol (Chris Bristol)]

I’m in a vicious circle. There is a problem with the OS and I can’t update the OS to fix it, as the problem is with the software that updates the OS - which is confusingly called “Software”.

[gnwiii (George N. White III)]

You applied a workaround for google-chrome, so whle it helped with youtube, it won’t affect your problem with rpmfusion-nonfree-steam. You may need an analogous process for the nonfree-steam repo so you are able to apply updates and then wait for an update to libdnf (and “related packages”) before enabling rpmfusion-nonfree-steam and reinstalling packages.

I rarely do updates with the GUI. I generally use “sudo dnf update --offline”, which downloads packages, runs a test, and then tells you the command to reboot and install.

[theprogram (MatH)]

Edit: Sorry misread ‘update’ as ‘upgrade’

[glb (Gregory Lee Bartholomew)]

@gnwiii

You may need an analogous process for the nonfree-steam repo so you are able to apply updates

It was pointed out in another thread that you might need to use the rpmfusion-*-updates-testing with the beta release (at least for the moment).

Upgrade to 43 fails

Enable testing to match fedora sudo dnf system-upgrade download --releasever=43 --enable-repo=rpmfusion-*-updates-testing $ dnf list libheif* Updating and loading repositories: Repositories loaded. Installed packages libheif.i686 1.20.2-4.fc43 updates-testing libheif.x86_64 1.20.2-4.fc43 updates-testing Available packages libheif-devel.i686 1.20.2-4.fc43 fedora libheif-devel.i686 1.20.2-4.fc43 updates-testing libheif-devel.x86_64 1.20.2-4.fc43 fedora lib…

[chrisofbristol (Chris Bristol)]

I didn’t understand the first paragraph, however I could see that the second might fix it.

The download worked, and after shutting all other windows, the update worked too. “Software” now runs, but I can’t test whether it will do an update yet because obviously everything is now up-to-date

Thanks George for staying on topic, answering my query and solving my problem.

[gnwiii (George N. White III)]

@chrisofbristol

“Software” now runs, but I can’t test whether it will do an update yet because obviously everything is now up-to-date

Maybe the rpmfusion-*-updates-testing will reach the beta-release. Until then you might need to use dnf5 command-line updating (or just remove the problem packages until the release appears).

[chrisofbristol (Chris Bristol)]

@gnwiii

use dnf5 command-line updating…until the release

Ok, thanks.

[edit] The startup error message has now gone. Updates are now available so I’ve tried Software - it still doesn’t work. No worries, I’m happy to use the command line until it’s fixed.

[computersavvy (Jeff V)]

@theprogram

Sorry misread ‘update’ as ‘upgrade’

When using dnf ‘upgrade’ and ‘update’ are synonymous. One is an alias for the other so it does not really matter which is used. I prefer to use ‘upgrade’ but both do exactly the same thing.

[traxtopel (Grant Williamson)]

Seeing a similar problem when trying to run pkcon.

“Do you want to allow installing of unsigned software? [N/y]” loop, enter password same message.

libdnf update fixes the issue.

[chrisofbristol (Chris Bristol)]

@traxtopel

libdnf update fixes the issue.

How is that done please? I guessed at “sudo update libdnf” but it errors.

[theprogram (MatH)]

I have a fresh install of F43 Beta - installed yesterday - and I do not have libdnf installed. I could install it with

sudo dnf install libdnf

I’m on Sway though - not Gnome.

What errors are you getting?

[gnwiii (George N. White III)]

@chrisofbristol

I guessed at “sudo update libdnf” but it errors.

Guessing, especially when using sudo, is dangerous. Before running a command for the first time:

• run `type to check that the command exists and is coming from a an expected location. In this case:

% type update
update not found

• run man <command> to check the command’s purpose and options.

See: Fedora DNF Documentation.

[computersavvy (Jeff V)]

@chrisofbristol

I guessed at “sudo update libdnf” but it errors.

I think that should have been sudo dnf update libdnf

[chrisofbristol (Chris Bristol)]

Thanks, I tried it. Unfortunately it tells me that there’s nothing to do. I’ll just have to keep using a terminal to do updates and wait for a fix.