Bug 2073206 - interrupted dimming partly locks window switching
Summary: interrupted dimming partly locks window switching
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 36
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F36FinalBlocker
TreeView+ depends on / blocked
Reported: 2022-04-07 21:35 UTC by René Genz
Modified: 2022-04-19 22:04 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-04-19 22:04:11 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-shell issues 5124 0 None opened gdm: Waiting for idle screen blank makes gdm widgets unresponsive to any input 2022-04-13 14:20:29 UTC
GNOME Gitlab GNOME mutter issues 2224 0 None opened Interrupting screen dimming partly locks session 2022-04-11 10:18:00 UTC
GNOME Gitlab GNOME mutter merge_requests 2333 0 None opened clutter/stage: Repick when pointer actor goes unmapped 2022-04-13 14:20:29 UTC

Description René Genz 2022-04-07 21:35:09 UTC
Description of problem:
Interrupting screen dimming partly locks window switching in Wayland and Xorg session of GNOME.

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

How reproducible:
easy, 100%

Steps to Reproduce:
1. to speed up testing: `gnome-control-center lock` -- Blank screen delay: 1 minute
2. open 2 independent programs, f.i. `nautilus` and `gnome-terminal` (or "GNOME settings" and `firefox`) ; you can test with a single window and right mouse button click on desktop too
3. when dimming starts: move mouse cursor or press keyboard key
4. use left mouse button to select other window

Actual results:
- other window not selectable
- no hover-over effect for buttons in top bar
- click on "Activities" in upper left corner - does not switch to overview mode
- right mouse button on desktop - context menu does not show up
- selecting buttons in the currently selected window - works (gnome-control-center)
- selecting buttons in the currently selected window - does not work (firefox)

Expected results:
no such problems

Additional info:
To get unstuck do either of these with currently selected window:
- double left click on title bar
- right mouse button click on title bar
- click-and-hold title bar and move window around
This helps as well:
- Super key on keyboard
- Alt+Tab to cycle window list
- Alt+F2 -- Esc

No problem if screen gets completely black and mouse cursor disappears and then you move mouse cursor.

I tested only on notebook (upgrade from Fedora Workstation 34 to 36) with built-in Intel graphics chip: $ lspci -nn | grep VGA
...Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

Comment 1 René Genz 2022-04-08 01:26:57 UTC
Same problem with nvidia graphics card on a different computer (upgraded from 34 to 36 too). Proposing as blocker bug.

Comment 2 Fedora Blocker Bugs Application 2022-04-08 01:28:58 UTC
Proposed as a Blocker for 36-final by Fedora user sobek using the blocker tracking app because:

 the best match seems to be https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Default_panel_functionality with "bad impression to a typical user"

Comment 3 Kamil Páral 2022-04-08 12:55:19 UTC
I can confirm this on my laptop. Use `gsettings set org.gnome.desktop.session idle-delay 10` to test this quickly (10 second screen blanking delay). I tested with terminal and nautilus, if any of those is active while the blanking starts and is interrupted, my screen is completely frozen and doesn't respond to mouse input, contrary to what comment 0 says (none of those listed mouse-related workarounds work for me). I have to use the keyboard to get unstuck - either start typing, or press Super, or Alt+Tab, etc.

Comment 4 František Zatloukal 2022-04-11 16:43:43 UTC
Discussed during the 2022-04-11 blocker review meeting: [1]

The decision to classify this bug as an AcceptedBlocker was made:

"It violates the following criteria: “All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use.”"

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2022-04-11/f36-blocker-review.2022-04-11-16.00.log.txt

Comment 5 Nathan 2022-04-12 06:13:56 UTC
Confirming this issue, with an Acer with integrated Intel graphics

Comment 6 Jonas Dreßler 2022-04-13 13:42:06 UTC
gnome-shell issue: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5124

Fixed by this mutter MR: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2333

Comment 7 František Zatloukal 2022-04-13 16:47:24 UTC
Setting to POST then...

Comment 8 Fedora Update System 2022-04-18 21:44:48 UTC
FEDORA-2022-374212758c has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-374212758c

Comment 9 Kamil Páral 2022-04-19 10:29:48 UTC
(In reply to Fedora Update System from comment #8)
> FEDORA-2022-374212758c has been submitted as an update to Fedora 36.
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-374212758c

The bug is gone.

Comment 10 Fedora Update System 2022-04-19 17:27:36 UTC
FEDORA-2022-374212758c has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-374212758c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-374212758c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2022-04-19 22:04:11 UTC
FEDORA-2022-374212758c has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

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