Bug 1894624

Summary:	Lock screen does not keep monitors in sleep state
Product:	[Fedora] Fedora	Reporter:	Brandon Nielsen <nielsenb>
Component:	wayland	Assignee:	Adam Jackson <ajax>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	35	CC:	abrahamyychan, ajax, belarusaed, dquinone, jan.public, michaelhthomas, ndegraef, peter.verthez, redhat-bugs, robert.de.rooy, rsenk330, thofmann
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-18 10:44:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Brandon Nielsen 2020-11-04 16:31:56 UTC

Description of problem: When a Gnome Wayland session is locked, the monitors initially go to sleep (backlights off), but eventually wake up (backlights turn on). If a notification comes in, the monitors come completely on, and stay on, displaying the lock screen.


How reproducible: Every time.


Steps to Reproduce:
1. Lock screen, either by waiting, or by <Super>-<L>
2. Wait


Actual results: Eventually monitors will wake, without further input from the user. They will never return to sleep.


Expected results: Monitors remain asleep until the user interacts with the system.


Additional info: Seems this was initially reported against Fedora 29[0]. I don't recall seeing the issue before F32.

I have not tested against alternative DEs, only Gnome.

The issue does not appear in a live environment.

The issue does not appear with an X session.

I have only tested on a desktop system with multiple(2) DisplayPort monitors running amdgpu. I will test with a single monitor when I get a chance.

Possibly related upstream issues, Gnome[1][2][3], amdgpu[4].

[0] - https://bugzilla.redhat.com/show_bug.cgi?id=1653026
[1] - https://gitlab.gnome.org/GNOME/mutter/-/issues/1021
[2] - https://gitlab.gnome.org/GNOME/mutter/-/issues/1419
[3] - https://gitlab.gnome.org/GNOME/mutter/-/issues/230
[4] - https://gitlab.freedesktop.org/drm/amd/-/issues/662

Comment 1 Brandon Nielsen 2020-11-04 20:40:27 UTC

Issue persists with only a single DisplayPort monitor connected.

Comment 2 Brandon Nielsen 2020-11-05 20:53:56 UTC

Another similar bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/877

Comment 3 abrahamyychan 2020-11-25 03:45:25 UTC

I'm running an nvidia gpu and having the same issue, so I don't believe it's amd related.
2080ti, Fedora 32, Gnome 3.36.7

Comment 4 Michael Thomas 2020-12-17 16:16:24 UTC

Can confirm this also on Fedora 33, Gnome 3.38 on Wayland, and an AMD APU w/ amdgpu and an HDMI monitor connected. The display turns off, then powers back on with an input of a completely black screen. Any mouse movement, keyboard movement, etc. brings back the lock screen as expected.

Comment 5 David Quiñones 2021-01-08 10:01:21 UTC

Can confirm this happens also in X1, so it's definitely not AMD related. Gen 7 with Intel UHD Graphics 620, connected to an HP monitor via HDMI.
.

Comment 6 Brandon Nielsen 2021-02-05 03:01:50 UTC

This seems to have been fixed for me in F33 at some point in the last couple weeks.

Comment 7 Till Hofmann 2021-02-05 20:55:47 UTC

I still have this issue with gnome 3.38.3.

Comment 8 Brandon Nielsen 2021-02-09 00:16:16 UTC

(In reply to Brandon Nielsen from comment #6)
> This seems to have been fixed for me in F33 at some point in the last couple
> weeks.

I take this back, I am still seeing the issue.

Comment 9 Till Hofmann 2021-04-29 08:00:52 UTC

The issue also occurs on Fedora 34.

Comment 10 Robert 2021-06-05 12:20:27 UTC

Seeing the same issue with F34 Wayland on both a ThinkPad T14s with Intel graphics, and on a desktop with AMD graphics (RX590).

On the ThinkPad it seems to only happen when an external (DP) monitor is attached. The desktop system has two monitors.

Comment 11 Aliaksiej Razumaŭ 2021-10-12 10:31:59 UTC

Fedora 34, Gnome 40.4, Radeon RX 570.

System info (generated by fpaste --sysinfo, but re-uploaded because of pastes lifetime is too short): https://gist.github.com/belarusaed/7f21e2532cba9e30d9023b474c4bca77

Have 2 monitors: 1 HDMI and 1 DP. When using win+l, monitors powering off and instantly powering on with black screen or lock screen (randomly, I think, I did not notice the pattern).

Reproduced on Wayland and on X.org.

Comment 12 Ben Cotton 2021-11-04 13:40:45 UTC

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Ben Cotton 2021-11-04 14:10:19 UTC

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Ben Cotton 2021-11-04 15:07:20 UTC

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Robert 2021-11-04 15:10:56 UTC

Same issue with F34 and F35.

Comment 16 Brandon Nielsen 2021-11-29 16:08:29 UTC

The problem had gone away for me, but I'm seeing it again with F35. Reopening.

Comment 17 Brandon Nielsen 2021-11-30 01:08:08 UTC

Poking at it some makes it appear kernel dependent for me.

5.15.4-201.fc35.x86_64 has the issue.

5.14.18-300.fc35.x86_64, 5.14.17-301.fc35.x86_64 do not.

If I get a chance I will try to bisect.

Comment 18 Brandon Nielsen 2021-12-02 19:27:19 UTC

Result of the bisect has resulted in bug 2028613.

Comment 19 Niels De Graef 2022-08-18 10:44:12 UTC

The core Wayland protocol doesn't really care about suspend-resume (arguably some protocol extensions like idle-inhibit do, but those are a separate component in any case), so I'm going to close this as a duplicate of bug 2028613, which should be the actual root cause (the graphical drivers in the kernel having a bug).

Thanks for your work on this Brandon!

Comment 20 Niels De Graef 2022-08-18 10:44:50 UTC


*** This bug has been marked as a duplicate of bug 2028613 ***