https://bugs.kde.org/show_bug.cgi?id=520857
Bug ID: 520857
Summary: qdbus commands ran while on lockscreen cause issues
Classification: Plasma
Product: plasmashell
Version First 6.6.5
Reported In:
Platform: Bazzite
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Screen locking
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
DESCRIPTION
I have a script that manages the colorblindness mode setting as well as
brightness of my system depending on the time of day and have noticed that if
this script is ran while on the lockscreen (which happens a lot since the
script is scheduled with systemd timers so it triggers on wake if the timer was
triggered during sleep), it either doesn't work or causes odd bugs.
STEPS TO REPRODUCE
1. Create a script with a `sleep 5` in the beginning and then either `qdbus
--literal org.kde.KWin /Effects org.kde.kwin.Effects.unloadEffect
colorblindnesscorrection` or `qdbus org.kde.Solid.PowerManagement
/org/kde/Solid/PowerManagement/Actions/BrightnessControl
org.kde.Solid.PowerManagement.Actions.BrightnessControl.setBrightness 100`
later on.
2. Run the script.
3. Before the 5 seconds is up, press Meta + L to lock the screen.
4. Observe glitches once script runs while on the lockscreen.
OBSERVED RESULT
When modifying the color blindness correction from lockscreen, the lock screen
effect will get out of sync with the user effect. Ex. The script enables color
blindness while on the lockscreen, I unlock device, disable it while unlocked,
and then if I simply lock the device again, color blindness mode is re enabled
on lock screen and also when unlocking.
When modifying the display brightness from lockscreen, it seems to crash the
power management service in some way because the screen will go black and come
back and then future commands (even while unlocked) will result in the error
`Cannot find
'org.kde.Solid.PowerManagement.Actions.BrightnessControl.setBrightness' in
object /org/kde/Solid/PowerManagement/Actions/BrightnessControl at
org.kde.Solid.PowerManagement`. It also makes the brightness and power controls
disappear from the system tray. Rebooting is the only way I have found to fix
this.
EXPECTED RESULT
Controlling these system properties would work whether locked or unlocked.
Especially on a system with only one user. I could see it getting tricky when
there are multiple users and each one might have different configurations. I'm
not sure how this is normally handled though - does the brightness change to
the last configured percentage for a user when unlocking into that user or it
is it a global setting?
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window): Bazzite 44
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
--
You are receiving this mail because:
You are watching all bug changes.
