kparal
(Kamil Páral)
September 19, 2025, 11:12am
1
This is a discussion topic for the following Common Issue:
Problem
In Fedora 43 Beta, we have found substantial problems with PackageKit-based tools (including GNOME Software) if the google-chrome repository is enabled. The repository will be enabled if you choose to enable “third party repositories” during the first boot wizard (gnome-initial-setup), or if you later manually enable it in the GNOME Software configuration. If the repository is enabled, package operations in GNOME Software and any other PackageKit-based tool may fail, showing an error lik…
You can discuss the problem and its solutions here, but please note that debugging and technical feedback should primarily go to the issue trackers (e.g. Bugzilla) linked in the Common Issue, because that’s the place that developers watch, not here.
If there are any updates/changes/amendments for the Common Issue description, which you believe should be performed, please post it here.
kparal
(Kamil Páral)
September 19, 2025, 11:12am
2
Please see the Common Issue for solution/workarounds:
Problem
In Fedora 43 Beta, we have found substantial problems with PackageKit-based tools (including GNOME Software) if the google-chrome repository is enabled. The repository will be enabled if you choose to enable “third party repositories” during the first boot wizard (gnome-initial-setup), or if you later manually enable it in the GNOME Software configuration. If the repository is enabled, package operations in GNOME Software and any other PackageKit-based tool may fail, showing an error lik…
It’s a shame f43 gnome-software is still using packagekit.
Why was the move to using dnf5 delayed? f44 uses dnf
kparal
(Kamil Páral)
September 19, 2025, 12:07pm
4
There were regressions which made us revert back to packagekit. But I don’t have the bug references ready at this moment.
adamwill
(Adam Williamson)
September 19, 2025, 3:07pm
5
miroslavl
(Miroslav Lakota)
September 20, 2025, 8:25pm
6
I am experiencing the same issue with WineHQ
failed to add subkeys for /var/cache/PackageKit/43/metadata/WineHQ-43-x86_64/winehq.key to rpmdb
And the workaround works.
Those issues seem minor compared to the current packagekit issues
expectation
(John Rory O'Dwyer)
September 26, 2025, 6:26pm
8
I’m getting a similar issue with Fedora Silverblue 43 when trying to install Google-Chrome from the command line. Obviously Silverblue uses rpm-ostree instead of dnf and also packagekit or libdnf aren’t installed either. Any ideas?
failed to add subkeys for /var/cache/rpm-ostree/repomd/google-chrome-43-x86_64/linux_signing_key.pub to rpmdb
expectation
(John Rory O'Dwyer)
September 26, 2025, 8:46pm
9
I raised a bug and got pointed to the following:
opened 11:54AM - 18 Sep 25 UTC
### Describe the bug
I rebased to F43 Kinoite Beta and hit this error when runn… ing rpm-ostree update
```
2 metadata, 0 content objects fetched; 788 B transferred in 1 seconds; 0 bytes content written
Inactive requests:
kernel (already provided by kernel-6.17.0-0.rc5.42.fc43.x86_64)
Checking out tree 6a9f1c3... done
Enabled rpm-md repositories: fedora-cisco-openh264 updates-testing updates fedora copr:copr.fedorainfracloud.org:phracek:PyCharm rpmfusion-nonfree-nvidia-driver rpmfusion-nonfree-steam google-chrome updates-archive
Updating metadata for 'fedora-cisco-openh264'... done
Updating metadata for 'updates-testing'... done
Updating metadata for 'updates'... done
Updating metadata for 'fedora'... done
Updating metadata for 'copr:copr.fedorainfracloud.org:phracek:PyCharm'... done
Updating metadata for 'rpmfusion-nonfree-nvidia-driver'... done
Updating metadata for 'rpmfusion-nonfree-steam'... done
Updating metadata for 'google-chrome'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264'; generated: 2025-03-05T10:45:56Z solvables: 6
rpm-md repo 'updates-testing'; generated: 2025-09-17T01:38:11Z solvables: 6553
rpm-md repo 'updates'; generated: 2018-02-20T19:18:14Z solvables: 0
rpm-md repo 'fedora'; generated: 2025-09-16T07:50:12Z solvables: 77562
rpm-md repo 'copr:copr.fedorainfracloud.org:phracek:PyCharm'; generated: 2025-09-02T06:34:48Z solvables: 8
rpm-md repo 'rpmfusion-nonfree-nvidia-driver'; generated: 2025-09-14T09:08:04Z solvables: 17
rpm-md repo 'rpmfusion-nonfree-steam'; generated: 2025-08-13T21:39:54Z solvables: 1
rpm-md repo 'google-chrome'; generated: 2025-09-16T21:24:47Z solvables: 4
rpm-md repo 'updates-archive'; generated: 2025-08-14T03:18:18Z solvables: 0
Resolving dependencies... done
Will download: 20 packages (24.6 MB)
Downloading from 'updates-testing'... done
error: failed to add subkeys for /var/cache/rpm-ostree/repomd/google-chrome-43-x86_64/linux_signing_key.pub to rpmdb
```
### Reproduction steps
1. Install F43 Kinoite Beta
2. Enable google-chrome repository (I assume it got enabled when I checked out Enable third party repositories on first setup)
3. Run `rpm-ostree update`
### Expected behavior
Update is successful
### Actual behavior
Update fails with mentioned error
### System details
```
$ rpm-ostree --version
rpm-ostree:
Version: '2025.10'
Git: 761e3624a5eeecc7019ae4ee2390b13bae53148c
Features:
- rust
- compose
- container
- fedora-integration
```
```
$ rpm-ostree status -b State: idle
BootedDeployment:
● fedora:fedora/43/x86_64/kinoite
Version: 43.20250916.n.0 (2025-09-16T07:51:10Z)
BaseCommit: 6a9f1c3e780a3fa8af636fb0983712924fac624910d68a1aa1cda18718f9daf4
GPGSignature: Valid signature by C6E7F081CF80E13146676E88829B606631645531
LayeredPackages: ansible ansible-freeipa distrobox fish libvirt make nextcloud-client podman-compose powerline python3-ramalama source-to-image vagrant-hostmanager vagrant-libvirt vagrant-sshfs vim vim-enhanced vim-powerline
LocalPackages: redhat-internal-cert-install-0.1-29.el7.noarch redhat-internal-NetworkManager-openvpn-profiles-non-gnome-0.1-62.el8.noarch
```
### Additional information
Found a workaround for this issue.
1. Disable `google-chrome` repository
2. Do `rpm-ostree cleanup --repomd`
And `rpm-ostree update` now works again.