Bug 2085449 - 300% display scale causes applications to crash immediately
Summary: 300% display scale causes applications to crash immediately
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 36
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-13 11:54 UTC by Yosuke Matsumura
Modified: 2023-05-25 16:20 UTC (History)
7 users (show)

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


Attachments (Terms of Use)
Portion of logs that show when apps are opened and crashed (2.76 KB, text/plain)
2022-05-13 11:54 UTC, Yosuke Matsumura
no flags Details

Description Yosuke Matsumura 2022-05-13 11:54:13 UTC
Created attachment 1879397 [details]
Portion of logs that show when apps are opened and crashed

Description of problem:
In Fedora 36, when 300% resolution scale is selected, applications will crash immediately once the mouse is moved at all. This is only reproducible with the 300% option (100, 200, and 400)

Version-Release number of selected component (if applicable):
42.0

How reproducible:
Every time.

Steps to Reproduce:
1. Open Settings > Display, and change resolution scale to 300%
2. Move mouse
3.

Actual results:
Settings application and all open apps crash. Any application that is opened afterwards also crashes.

Expected results:
300% scale and all apps work.

Additional info:
https://ask.fedoraproject.org/t/fedora-36-cannot-bear-300-zoom-in/22187/2
https://www.reddit.com/r/Fedora/comments/uofxk2/fedora_36_problems_after_upgrade_from_35/

Comment 1 Yosuke Matsumura 2022-05-13 12:04:28 UTC
This is when using Wayland. Not reproducible on Xorg.

Comment 2 Yosuke Matsumura 2022-05-13 14:14:16 UTC
This is also not reproducible on Rawhide which has is running gnome-shell-42.1-1.fc37.x86_64.

So I upgraded gnome-shell on Fedora 36 using `rpm-ostree override replace gnome-shell-42.1-1.fc36.x86_64.rpm` which I downloaded from https://koji.fedoraproject.org/koji/buildinfo?buildID=1963580. However this does not change the behavior in F36 - apps still crash as before.

Comment 3 Matthias Clasen 2022-06-01 20:47:45 UTC
This has been fixed upstream in gtk 4.6.5

Comment 4 Ben Cotton 2023-04-25 17:09:28 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 5 Ludek Smid 2023-05-25 16:20:57 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.