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

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: Bug

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):

How reproducible:
Every time.

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

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:

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

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