Hide Forgot
Description of problem: While trying to update my Fedora 25 beta, I encounter the following error that blocks the complete update process: Error: Transaction check error: file /usr/share/themes/Adwaita/gtk-3.0/gtk.css conflicts between attempted installs of gnome-themes-standard-3.22.2-1.fc25.x86_64 and gnome-themes-standard-3.22.2-1.fc25.x86_64 Version-Release number of selected component (if applicable): - Fedora 25 (installed atop a former Fedora 24) - gnome-themes-standard 3.20.2-1.fc25 - dnf 1.1.10-2.fc25 How reproducible: always (up until a change in the f25 repositories, I suppose) Steps to Reproduce: 1. Install Fedora 25 (atop Fedora 24?) 2. Run "dnf update" Actual results: The update process ends with the error: Error: Transaction check error: file /usr/share/themes/Adwaita/gtk-3.0/gtk.css conflicts between attempted installs of gnome-themes-standard-3.22.2-1.fc25.x86_64 and gnome-themes-standard-3.22.2-1.fc25.x86_64
Still looking for a solution. Meanwhile I've managed to update most of my system by running: $ sudo dnf --exclude=gnome-themes-standard update
Tried a complete update today, problem still present. I've used "--exclude" once again to update all the system, except gnome-themes-standard.
I successfully rolled back to gnome-themes-standard-3.20-1.fc25 through a "dnf downgrade". Then I tried once again to update, and the same error occurs. In other words, installing 3.20-1 does not trigger the problem that I have, while trying to install 3.22.2-1 does trigger it.
This bug is preventing me from upgrading f24->f25. Is there any way to force dnf to install gnome-themes-standard 3.20.2-1.fc25 during system upgrade? I am using the following: dnf system-upgrade download --refresh --releasever=25 I also tried the following: 1. dnf system-upgrade download --refresh --releasever=25 --exclude=gnome-themes-standard Error: package gnome-themes-standard-3.20.2-1.fc24.x86_64 requires adwaita-gtk2-theme = 3.20.2-1.fc24, but none of the providers can be installed 2. dnf system-upgrade download --refresh --releasever=25 --exclude=gnome-themes-standard --exclude=adwaita-gtk2-theme This works with a bunch of downgrades, but after reboot the upgrade starts and then just ends up booting back into f24. I also set selinux to permissive just in case that was the problem.
This comment was flagged a spam, view the edit history to see the original text if required.
I have the same problem during upgrade 24 -> 25. Anyone found a solution yet?
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.