On a fresh installation of Fedora Rawhide, openQA tests that deal with updates fail because there is an issue with openh264 update and it the following line is shown: ``` Unable to download updates ``` when a user clicks on the Details button, this is what they get: ``` Failed to resolve transaction: Packages for argument 'mozilla-openh264' available, but not installed. ``` I tried to do this manually, running `pkcon update` and the command goes like this: ``` Getting updates [=========================] Finished [=========================] The following packages have to be installed: mozilla-openh264-2.6.0-2.fc43.x86_64 H.264 codec support for Mozilla browsers openh264-2.6.0-2.fc43.x86_64 H.264 codec library The following packages have to be obsoleted: noopenh264-2.6.0-1.fc43.x86_64 Fake implementation of the OpenH264 library The following packages have to be updated: libheif-1.20.1-1.fc43.x86_64 HEIF and AVIF file format decoder and encoder Proceed with changes? [N/y] y [=========================] Testing changes [=========================] Updating packages [=========================] Finished [ ] (0%) Do you want to allow installing of unsigned software? [N/y] y [=========================] Querying [=========================] Updating packages [=========================] Finished [ ] (0%) Do you want to allow installing of unsigned software? [N/y] y ``` And this goes on and on until the operation is cancelled. The packages remain not updated. However, when one tries `dnf update`, the updates run without any issues. Reproducible: Always Steps to Reproduce: 1. Install the latest Rawhide. 2. Run Software and attempt updates. 3. See the problem. Actual Results: Software reports update issues. Expected Results: Software should not report any issues and update should be possible.
This is probably also why we aren't getting update notifications, I'm guessing. Proposing as a Beta blocker per Beta criterion "The installed system must be able appropriately to install, remove, and update software with the default tool for the relevant software type in all release-blocking desktops (e.g. default graphical package manager). This includes downloading of packages to be installed/updated."
Based on the dates, it looks like this affects the KDE upgrade (not update) test too - it doesn't fail every day, but it's failed 6 out of 9 tries since Fedora-Rawhide-20250625.n.0 , the same compose where GNOME tests started failing. Before that it was reliably passing every day.
A few things: 1. Can you confirm this is happening OUTSIDE of rdu3? ie, is it a real problem everywhere? Or just the new datacenter? 2. cisco is in process of completely redoing their cdn. It should roll out in the next week or two...
1. I just reproduced it on a local VM, so it's not specific to rdu3. 2. Noted!
oh, I misread the KDE update test log, though, that's probably not the same thing - it started earlier. The failures on GNOME started with Fedora-Rawhide-20250629.n.0 , they last passed with Fedora-Rawhide-20250627.n.0 .
Ping? Is anyone looking at this? It's quite a bad bug. GNOME Software is just kinda broken by this.
This is a gnome-software / dnf5daemon issue. GNOME Software was switched in Rawhide to dnf5daemon last month.
Neal points out that this started failing exactly when we got gnome-software-49~alpha-1.fc43 , which switched us from PackageKit to dnf5daemon.
I see two bugs here: 1) one described in the description using `pkcon` deserves a PackageKit bug. 2) the error seen in the gnome-software comes from the dnf5, it is a bug in the dnf5 plugin of the gnome-software (or dnf5 itself, it depends; I'll fix the plugin).
I made series of fixes (while being at it) for the dnf5 plugin in the gnome-software, which will be built as gnome-software-49~alpha-3.fc43 shortly.
FEDORA-2025-8135edba74 (gnome-software-49~alpha-3.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-8135edba74
FEDORA-2025-8135edba74 (gnome-software-49~alpha-3.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.