Fusion
February 26, 2026, 11:54am
1
Signals wakeUp, aboutToTurnOff seem to not be currently exposed, they were in version 6.5, here is a list of the fields that are available on output object using workspace.screens.forEach
geometry = KWin::Rect(0, 0, 5120, 1440)
devicePixelRatio = 1
name = DP-1
manufacturer = Samsung Electric Company
model = Odyssey G95C
serialNumber = HNTX101210
objectNameChanged = function() { [native code] }
geometryChanged = function() { [native code] }
scaleChanged = function() { [native code] }
aboutToChange = function() { [native code] }
changed = function() { [native code] }
blendingColorChanged = function() { [native code] }
transformChanged = function() { [native code] }
currentModeChanged = function() { [native code] }
mapToGlobal = function() { [native code] }
mapFromGlobal = function() { [native code] }
Is this intended change or should a bug report be created?
zzag
February 26, 2026, 1:32pm
2
The dpms mode was reworked in 6.6. They were public-ish signals (edit: to be precise, they were intended only for effects). What was the usecase for those signals?
Fusion
February 26, 2026, 1:47pm
3
I did use them to emit dbus signal and then used that to toggle my lights behind monitor. Is there an alternative i could use now?
supagu
April 2, 2026, 11:41pm
4
My use case was to detect screen on/off to send a message to my CEC device to turn my TV on and off.
I have my own thread about it here:
Some years ago I developed a KWin script to use CEC device to turn the screen on and off automatically using a KWin script.
My old post is here: Determine when monitor is turned on or off via python dbus - #14 by supagu
I have some some code that used to work (I think it was using Qt5), now it appears not to work (My computer is using Qt6):
The problem is with this line of code:
firstScreen.aboutToTurnOff.connect(aboutToTurnOff)
Gives me the error:
/home/server/.local/share/kwin/scripts/…