-
-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong Distribution Icon in Gnome Control Center #2619
Comments
Seems, this issue not related to papirus-icon-theme. Ask gnome-control-center package maintainers to fix it on https://bugzilla.redhat.com/ |
Thank you for pointing that out. I've opened a bug report with Red Hat instead. :) |
I received a response from Red Hat. They pointed out that this is not a bug in RHEL. They mentioned that papirus-icon-theme theme is overriding fedora-logo-icon with an upstream Fedora logo instead of a Red Hat fedora logo, and they referenced this commit from papirus-icon-theme regarding replacing the gnome-control-center icons in Ubuntu and Fedora in the thread. They also mentioned that the way papirus-icon-theme has set up this icon, it will be broken everywhere; not just in gnome-control-center, as "RHEL expects fedora-logo-icon to be a Red Hat fedora, not a Fedora project logo". If you would like to check the bug report I submitted to Red Hat, that is HERE. |
So, fedora-logo-icon should point to rhel logo. Okay... I've seen things dumber. |
Yeah, I find that confusing too. I guess it's because the Red Hat logo IS a fedora?? |
I prefer to remove this icon to avoid confusion. Especially because the logo doesn't change in future versions. |
When you go into gnome-control-center, and select "Details" and then "About", you can see the wrong icon for the distribution being displayed.
This is what gnome-control-center currently shows, and I did find these icons in the icon theme. Is there a way to set them so that they show up correctly in gnome-control-center? It's a minor thing, but it bugs me to no end. Thank you!
The text was updated successfully, but these errors were encountered: