Bug 435895

Summary: Display Configuration applet's "Presentation Mode" is secretly still active after being turned off
Product: [Plasma] KScreen Reporter: Peri <peri.com>
Component: Plasma AppletAssignee: kscreen-bugs-null <kscreen-bugs-null>
Severity: normal CC: ecc_2000, kde, materka, nanabaahgyan, nate
Priority: NOR    
Version: 5.21.4   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Peri 2021-04-19 01:26:56 UTC

When you enable the "Presentation Mode" option accessible from the Display Configuration icon from the System Tray and disable it again, it will still be enabled until you restart plasmashell.

1. Check the option "Presentation Mode" from the Display Configuration icon from the System Tray to enable it
2. Check it again to disable it

The Presentation Mode will be kept enabled even when the checkbox is unchecked: the screen won't automatically be turned off as expected from "Screen Energy Saving" setting, not sure about the automated suspension since I don't use it. Killing plasmashell and starting it again "fixes" the issue.

When unchecking the Presentation Mode box from the Display Configuration menu it should disable the mode.

Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

Comment 1 Nate Graham 2021-04-21 20:23:42 UTC
Can confirm. Interestingly enough, the Battery & Brightness applet doesn't list any active inhibitions while Presentation Mode is on, so it must be using some other mechanism to suppress power management. Perhaps it's just a matter of porting it to use the normal method.
Comment 2 ecc_2000 2021-05-06 17:32:20 UTC
Also noticed this bug on Manjaro.

KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Kernel Version: 5.11.18-1-MANJARO
Comment 3 nbgyan 2021-09-11 11:28:54 UTC
Can confirm this too.

Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-34-generic (64-bit)
Comment 4 Nate Graham 2021-09-14 16:34:34 UTC
Aha, this was fixed automatically by the fix for Bug 433675, since they use the same data source!

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