Bug 466428

Summary: Power Settings Not Applied/Enforced
Product: [Plasma] Powerdevil Reporter: Myc <mycclark>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: me, nate
Priority: NOR    
Version: 5.27.1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Myc 2023-02-25 20:03:34 UTC
SUMMARY
***
Power settings are not applied.  This is both the general power settings as well as activity specific settings.  Screens do not timeout, machine will never go to sleep, ect...
***


STEPS TO REPRODUCE
1. Create user and apply their power settings.
2. Log out and back in.
3. Settings are no longer working. 

OBSERVED RESULT
The settings only work for the first session for a user, after that they do not work.

EXPECTED RESULT
Power settings always work as expected.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.13-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6500T CPU @ 2.50GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 530
Manufacturer: LENOVO
Product Name: 10FM001UUS
System Version: ThinkCentre M900

ADDITIONAL INFORMATION
Comment 1 Myc 2023-02-26 00:57:49 UTC
Updated to 5.27.1 and problem still exists.

Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.13-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6500T CPU @ 2.50GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 530
Manufacturer: LENOVO
Product Name: 10FM001UUS
System Version: ThinkCentre M900
Comment 2 Myc 2023-03-01 05:48:24 UTC
The problem has been intermittent to about one in ten boots power setting work as intended.
Comment 3 Nate Graham 2023-03-01 15:53:54 UTC
Not a KDE issue; please update your Fedora installation to receive the packaging fix for Bug 462695.

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