Bug 2315702

Summary:	Idle suspend fails, prompting user for admin password
Product:	[Fedora] Fedora	Reporter:	Stephen Gallagher <sgallagh>
Component:	powerdevil	Assignee:	KDE SIG <kde-sig>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	41	CC:	ales.astone, fzatlouk, jgrulich, kde-sig, kparal, mkyral, natalie_clarius, ngompa13, rdieter, robatino, than, vinicius.fedora
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	AcceptedBlocker
Fixed In Version:	plasma-desktop-6.1.90-2.fc41, powerdevil-6.1.90-2.fc41	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-10-01 08:50:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2247867

Description Stephen Gallagher 2024-09-30 16:36:57 UTC

By default on Fedora, Plasma Workspaces will attempt to put the machine into "sleep" mode after fifteen minutes of inactivity. This worked properly on Fedora 40 with KDE 6.1, but when I upgraded to Fedora 41 the automatic sleep no longer works. This was true for both 6.1 and 6.2 Beta.

When I come back to the machine some time later and unlock it (the screen still locked during this time), I am presented with an admin password prompt informing me that "Authentication is required to suspend this system".

Reproducible: Sometimes

Steps to Reproduce:
1. Boot and log into KDE Plasma 
2. Leave the computer alone for at least fifteen minutes
Actual Results:  
The monitor is off and the system is locked, requiring a password to resume.

Expected Results:  
The computer should have locked the system and then suspended to save power.

This is possibly related to changes to the session in systemd 256 as discussed in https://bbs.archlinux.org/viewtopic.php?id=297757

Comment 1 Fedora Blocker Bugs Application 2024-09-30 16:39:52 UTC

Proposed as a Blocker for 41-final by Fedora user sgallagh using the blocker tracking app because:

 "All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use."

The default configuration of this system involved idle suspend. Also, as the user is prompted for authentication, it's highly visible.

Comment 2 Neal Gompa 2024-09-30 17:18:58 UTC

This is actually handled in powerdevil, reassigning there.

Comment 3 František Zatloukal 2024-09-30 17:32:56 UTC

Discussed during the 2024-09-30 blocker review meeting: [1]

The decision to classify this bug as a AcceptedBlocker (Final) was made:

"This is accepted as a violation of "All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use". It's a bit of a stretch but we think it's reasonable to read it in context as covering a significant user-visible element of default desktop configuration like this being broken in a highly visible and annoying way."

[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-09-30/f41-blocker-review.2024-09-30-16.00.log.html

Comment 4 Stephen Gallagher 2024-09-30 22:19:17 UTC

I was suspecting that it might be a hardware issue because I couldn't reproduce it on my other machine. However I discovered that there was a patch added to plasma-desktop recently that appears to have resolved the issue: https://github.com/KDE/plasma-desktop/commit/fc0048b41e27be46bfcc14ade556aa08ea29e9e9

(It's also possible that https://github.com/KDE/powerdevil/commit/0b708921b543974650202600b9f01e4957d178de played a role here; I updated them both together and the issue disappeared).

Given that the plasma-desktop crash was a race-condition issue, I suspect that my hardware just happened to be more prone to hitting it.


Since https://bodhi.fedoraproject.org/updates/FEDORA-2024-112d223c56 carried both of these fixes, I think we can consider this bug fixed by that.

Comment 5 Kamil Páral 2024-10-01 06:29:58 UTC

I'll test it on my machine and report the result.

Comment 6 Kamil Páral 2024-10-01 08:50:41 UTC

Suspend works as expected on KDE with latest stable updates on my machine, closing this.