screen_off = "qdbus org.kde.kglobalaccel /component/org_kde_powerdevil invokeShortcut 'Turn Off Screen'" I use this on deck and the following on desktop where the monitors automatically shut off: "kscreen-doctor output.DP-2.disable" hope it helps!
I think it's something like
kscreen-doctor --dpms off
works the same as xset dpms
This works!
Key Commands
- List Connected Displays To see all connected outputs and their status:
kscreen-doctor -o
Example output:
Output: 1 eDP-1
enabled
connected
Modes: 1:2560x1600@60.00*!
This helps identify your display names (e.g., eDP-1 or HDMI-A-1).
- Turn Off All Displays (DPMS) To put all displays into low-power mode:
kscreen-doctor --dpms off
Uses DPMS (Display Power Management Signaling) to turn off displays safely.
- Turn On All Displays To wake all displays:
kscreen-doctor --dpms on
- Disable/Enable a Specific Output To control a specific display (e.g., HDMI-A-1):
kscreen-doctor output.HDMI-A-1.disable
kscreen-doctor output.HDMI-A-1.enable
Note: Avoid disabling your primary/laptop panel (e.g., eDP-1) unless you have another display connected.
- Bonus: Adjust Brightness or Scale
kscreen-doctor output.eDP-1.brightness.50 # 0-100
kscreen-doctor output.eDP-1.scale.1.5 # Scale factor
Like the monitor has gone to sleep? Maybe ddcutil?
Hahahaha! Wayland sucks so much you users can't even turn the screen on or off.
Welp, time to return to physical switches I guess!
Did you read anything other than half of the words in the title? If you’re a troll, please, stop, we don’t need more separation of communities in this world. If you’re not a troll and genuinely this stupid: get off the internet, go to your local library and just read any nonfictional book, that should give you some insight on how things actually work in the real world.
I use this in a cronjob to turn a raspberry pi screen off at night and back on in the morning:
wlr-randr --output "HDMI-A-1" --off
wlr-randr --output "HDMI-A-1" --on
I've also go this environment variable set but I don't know if it is needed outside of cron:
XDG_RUNTIME_DIR=/run/user/1000
Thank you for sharing your setup. Your solution using wlr-randr in a cron job is indeed useful for wlroots-based compositors (such as Sway, Hyprland, or labwc), where the wlr-output-management protocol is supported.
For those (like me) encountering the error 'compositor doesn’t support wlr-output-management-unstable-v1', this indicates that the compositor in use (e.g., KDE/KWin, GNOME/Mutter, or other non-wlroots compositors) does not support wlr-randr. In such cases, alternatives should be considered.
I will be post my findings, I can't believe I'm the only or just one of the few looking to archive this in a laptop..
Linux
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP