Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2066781 - Blurry Fedora logo in About
Summary: Blurry Fedora logo in About
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-control-center
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F36FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2022-03-22 13:33 UTC by Máirín Duffy
Modified: 2023-05-25 16:41 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 16:41:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Blurry fedora logo in contrl center (deleted)
2022-03-22 13:33 UTC, Máirín Duffy
no flags Details
no blurry for me at RC1.4 (deleted)
2022-05-04 16:03 UTC, Geraldo Simião
no flags Details
resizing the settings window (deleted)
2022-05-04 16:09 UTC, Carl G.
no flags Details
screencast from Fedora-Workstation-Live-x86_64-36-1.5.iso (deleted)
2022-05-05 03:33 UTC, Geraldo Simião
no flags Details
Blurry logo even in 1080p display, dark theme as well (deleted)
2022-05-28 03:22 UTC, Jeff Shee
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-control-center issues 1709 0 None opened about: center image, not fill 2022-10-20 11:46:18 UTC

Description Máirín Duffy 2022-03-22 13:33:15 UTC
Created attachment 1867497 [details]
Blurry fedora logo in contrl center

Description of problem:
In fedora-release-identity-workstation-36-0.16.noarch
the Fedora logo in control center is pixelated and looks blurry.

It looks like this change caused it

https://src.fedoraproject.org/rpms/gnome-control-center/c/dcef09d2059c34054395970d8d7492c12c48a1b9?branch=rawhide

Can this change be reverted?

Version-Release number of selected component (if applicable):
gnome-control-center-42~rc-1.fc36.x86_64

How reproducible:
A+++

Steps to Reproduce:
1. Install latest Fedora Workstation 36 testing image
2. Go to Settings >  About
3. Behold blurry Fedora logo

Actual results:
Blurry Fedora logo

Expected results:
Clean and sharp Fedora logo

Attaching screenshot

Additional info:

Comment 1 Stephen Gallagher 2022-05-04 14:42:43 UTC
It looks fine to me on gnome-control-center-42.0-4.fc36.x86_64

Can you try updating to the latest and check again? The other possibility is that it may be related to the resolution (hidpi?). I see that your image is 2553x1390, which is not a common desktop resolution.

Comment 2 Fedora Blocker Bugs Application 2022-05-04 15:24:39 UTC
Proposed as a Freeze Exception for 36-final by Fedora user carlg using the blocker tracking app because:

 blurry Fedora logo in gnome-control-center (Settings) > About

Comment 3 Geraldo Simião 2022-05-04 16:03:13 UTC
Created attachment 1877082 [details]
no blurry for me at RC1.4

Fedora-Workstation-Live-x86_64-36-1.4.iso seems good to me here

Comment 4 Carl G. 2022-05-04 16:09:31 UTC
Created attachment 1877084 [details]
resizing the settings window

Comment 5 Stephen Gallagher 2022-05-04 18:39:12 UTC
Okay, I see it now. If you expand the settings window vertically, the logo enlarges in physical size but not in image resolution.

Comment 6 Geraldo Simião 2022-05-05 03:33:34 UTC
Created attachment 1877196 [details]
screencast from Fedora-Workstation-Live-x86_64-36-1.5.iso

tested now the last release candidate (1.5)
resolution is 1366x768
I don't see a problem here

Comment 7 Michael Catanzaro 2022-05-05 18:26:30 UTC
(In reply to Máirín Duffy from comment #0)
> It looks like this change caused it
> 
> https://src.fedoraproject.org/rpms/gnome-control-center/c/
> dcef09d2059c34054395970d8d7492c12c48a1b9?branch=rawhide
> 
> Can this change be reverted?

I requested that revert because I tested the change on F35 and found it caused gnome-control-center to display the logo at a huge size. It was obviously broken.

I didn't test F36 or rawhide, though. These are different because they use GTK 4 instead of GTK 3, with different underlying widgets to display the image. Perhaps it's totally fine. Just needs to be tested.

Comment 8 Michael Catanzaro 2022-05-05 18:27:00 UTC
(In reply to Stephen Gallagher from comment #1)
> It looks fine to me on gnome-control-center-42.0-4.fc36.x86_64
> 
> Can you try updating to the latest and check again? The other possibility is
> that it may be related to the resolution (hidpi?). I see that your image is
> 2553x1390, which is not a common desktop resolution.

It's probably only blurry on hidpi, which is likely why I didn't notice.

Comment 9 Maksym Hazevych 2022-05-05 18:46:54 UTC
(In reply to Geraldo Simião from comment #6)
> I don't see a problem here

Please look at the attachment 
(In reply to Carl G. from comment #4)
> Created attachment 1877084 [details]
> resizing the settings window

Comment 10 Michael Catanzaro 2022-05-05 18:58:19 UTC
Ah... I see.

Comment 11 Matthias Clasen 2022-05-06 10:43:41 UTC
The one missing thing here - an upstream issue: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1815

Comment 12 Geraldo Simião 2022-05-06 12:06:35 UTC
Then why it doesn't happen when I tested rc 1.5? https://bugzilla.redhat.com/attachment.cgi?id=1877196
Resolution related?

Comment 13 somethingsomethingfedora 2022-05-06 14:57:08 UTC
(In reply to Geraldo Simião from comment #12)
> Then why it doesn't happen when I tested rc 1.5?
> https://bugzilla.redhat.com/attachment.cgi?id=1877196
> Resolution related?

Yes, looks to me like you don't have enough vertical resolution to pull it down far enough to notice the transition.

Comment 14 Jeff Shee 2022-05-28 03:22:35 UTC
Created attachment 1884416 [details]
Blurry logo even in 1080p display, dark theme as well

Comment 15 tiberias 2022-11-15 23:05:36 UTC
Any news on that issue? Just updated to F37 and this behaviour still exists.

Comment 16 Damián Barberón 2022-11-16 14:14:05 UTC
Uptream fix has been merged 3 weeks ago:

https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1475

Comment 17 Ben Cotton 2023-04-25 16:56:11 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 18 Ludek Smid 2023-05-25 16:41:37 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.