Issue when trying to install Google-Chrome from the command line with rpm-ostree. Fails with error: failed to add subkeys for /var/cache/rpm-ostree/repomd/google-chrome-43-x86_64/linux_signing_key.pub to rpmdb Reproducible: Always Steps to Reproduce: 1.Enable Google-Chrome repo 2.Try to install google-chrome-stable from the commandline using rpm-ostree install google-chrome-stable Actual Results: Fails with error: failed to add subkeys for /var/cache/rpm-ostree/repomd/google-chrome-43-x86_64/linux_signing_key.pub to rpmdb Expected Results: Google-Chrome should be installed Additional Information: This is the same with other repos enabled such as for mullvad-vpn Version of Fedora is Fedora Silverblue 43 beta Version of rpm-ostree is rpm-ostree-2025.11.1.fc43.x86_64
See https://github.com/coreos/rpm-ostree/issues/5494
(In reply to Timothée Ravier from comment #1) > See https://github.com/coreos/rpm-ostree/issues/5494 Thank you Timothée!
Workaround in https://pagure.io/workstation-ostree-config/pull-request/690 I'm proposing this as a blocker/FE for F43.
Summary: - rpm-ostree is impacted by https://bugzilla.redhat.com/show_bug.cgi?id=2372978, see: https://github.com/coreos/rpm-ostree/issues/5494 - Updating the bundled libdnf in rpm-ostree will likely not happen for F43 as we need to branch for C9S before, see: https://github.com/coreos/rpm-ostree/pull/5498 - When https://fedoraproject.org/wiki/Changes/Third_Party_Software_Mechanism was added in F35, we forgot to enable the unit syncing the config for Atomic Desktops. Thus as a workaround: - Enable the fedora-third-party-refresh.service: https://bugzilla.redhat.com/show_bug.cgi?id=2403093 - Disable the Chrome RPM repo for now: https://pagure.io/workstation-ostree-config/pull-request/690 --- Technically this won't fix this issue but at least it will not have users hit this error right after installation.
Proposed as a Freeze Exception for 43-final by Fedora user siosm using the blocker tracking app because: Without this workaround, Atomic Desktops users that enable Third Party Software and try to layer packages will immediately hit the error linked in the bug. We can revert this workaround once rpm-ostree is fixed.
*** Bug 2403433 has been marked as a duplicate of this bug. ***
Accepted as a freeze exception in https://pagure.io/fedora-qa/blocker-review/issue/1975
Will be "fixed" (workaround'ed) when https://pagure.io/workstation-ostree-config/pull-request/695 lands in a build, hopefully tomorrow's. We'll re-open it after that to track the actual fix.
What's the status on this?
The workaround should be in place in Rawhide & F43. I will have to double check that. The underlying bug is not fixed yet: https://github.com/coreos/rpm-ostree/issues/5494 / https://github.com/coreos/rpm-ostree/pull/5498 Should I close it and re-open it or close it and open a new bug to track the actual fix?
Let's do this.
Hi. This issue persists after rebasing to Fedora 43 Kinoite (released, non-beta).
That's not actually quite the same issue. https://pagure.io/fedora-qa/issue/836
FEDORA-2025-ffaa2d6bf6 (rpm-ostree-2025.12-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-ffaa2d6bf6
(In reply to Fedora Update System from comment #14) > FEDORA-2025-ffaa2d6bf6 (rpm-ostree-2025.12-1.fc43) has been submitted as an > update to Fedora 43. > https://bodhi.fedoraproject.org/updates/FEDORA-2025-ffaa2d6bf6 I've tested the update and it has fixed the issue. Thank you! You may close this ticket.
FEDORA-2025-ffaa2d6bf6 (rpm-ostree-2025.12-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.