Implement zwlr-output-power-management

[witchlliee]

It's useful to let desktop shells to safely power down monitors when the system goes idle.

[witchlliee]

Okay I'm a idiot. It occurred to me I could just let Jay turn-off the monitors and lock the screen. But there is a little problem, it don't use noctalia to lock the screen at all:

idle = {
    minutes = 1,
    grace-period = { seconds = 3 },
}
on-idle = {
    type = "exec",
    exec = {
        prog = ["noctalia", "msg", "session", "lock"],
        privileged = true,
    },
}

I also tried as prog instead:

prog = "noctalia msg session lock",

Yet no luck.

[mahkoh]

shell = "noctalia msg session lock",

[witchlliee]

shell = "noctalia msg session lock",

it still doesn't lock the screen for some reason

idle = {
    minutes = 1,
    grace-period = { seconds = 3 },
}
on-idle = {
    type = "exec",
    exec = {
        shell = "noctalia msg session lock",
        privileged = true,
    },
}

[mahkoh]

You can always look at the logs.

[witchlliee]

You can always look at the logs.

That would be it from the logs:

Details

[2026-07-15T16:59:14.262Z INFO jay::client::tasks] Client 195 terminated the connection [2026-07-15T16:59:14.262Z INFO jay::client] Removing client 195 [2026-07-15T16:59:15.288Z INFO jay::client::tasks] Client 190 terminated the connection [2026-07-15T16:59:15.288Z INFO jay::client] Removing client 190 [2026-07-15T16:59:52.513Z ERROR jay::client::tasks] An error occurred while trying to handle a message from client 191: An error occurred reading from/writing to the client: An io-uring error occurred: Connection reset by peer (os error 104) [2026-07-15T16:59:52.513Z INFO jay::client] Shutting down client 191 [2026-07-15T16:59:52.513Z ERROR jay::client::tasks] An error occurred while sending data to client 191: An error occurred reading from/writing to the client: An io-uring error occurred: Broken pipe (os error 32) [2026-07-15T16:59:52.513Z INFO jay::client] Removing client 191 [2026-07-15T17:09:17.633Z ERROR jay::backends::metal::video] Could not queue a CRTC sequence: Could not queue a CRTC sequence: Invalid argument (os error 22) [2026-07-15T17:09:17.633Z ERROR jay::backends::metal::video] Could not queue a CRTC sequence: Could not queue a CRTC sequence: Invalid argument (os error 22) [2026-07-15T17:09:17.634Z ERROR jay::backends::metal::video] Could not queue a CRTC sequence: Could not queue a CRTC sequence: Invalid argument (os error 22) [2026-07-15T17:10:07.117Z INFO jay::libinput] libinput: event8 - Logitech PRO X 2: SYN_DROPPED event - some input events have been lost. [2026-07-15T17:10:07.231Z INFO jay::backends::metal::monitor] Device changed: /dev/dri/card1 [2026-07-15T17:10:07.233Z INFO jay::backends::metal::video] Reusing desired state for OutputId { _connector: None, manufacturer: "AUS", model: "XG27ACS", serial_number: "TBLMTF008163", hash: OutputIdHash([229, 197, 176, 129, 202, 74, 177, 186, 71, 111, 161, 65, 232, 98, 177, 195, 130, 83, 238, 148, 163, 236, 146, 211, 131, 19, 226, 91, 182, 186, 88, 87]) } [2026-07-15T17:10:07.347Z INFO jay::backends::metal::video] Initialized connector DP-2 with mode Mode { width: 2560, height: 1440, refresh_rate_millihz: 164958 } [2026-07-15T17:10:07.347Z INFO jay::tasks::connector] Connector DP-1 disconnected [2026-07-15T17:10:08.840Z INFO jay::backends::metal::monitor] Device changed: /dev/dri/card1 [2026-07-15T17:10:08.843Z INFO jay::backends::metal::video] Reusing desired state for OutputId { _connector: None, manufacturer: "TCL", model: "27G64", serial_number: "00001", hash: OutputIdHash([102, 231, 73, 132, 215, 145, 21, 87, 238, 112, 124, 251, 168, 151, 88, 170, 223, 128, 64, 213, 55, 175, 43, 225, 237, 189, 212, 68, 177, 194, 162, 125]) } [2026-07-15T17:10:08.846Z INFO jay::backends::metal::video] Reusing desired state for OutputId { _connector: None, manufacturer: "AUS", model: "XG27ACS", serial_number: "TBLMTF008163", hash: OutputIdHash([229, 197, 176, 129, 202, 74, 177, 186, 71, 111, 161, 65, 232, 98, 177, 195, 130, 83, 238, 148, 163, 236, 146, 211, 131, 19, 226, 91, 182, 186, 88, 87]) } [2026-07-15T17:10:08.846Z ERROR jay::backends::metal::video] Could not initialize DRM device /dev/dri/card1: Could not perform modeset: Commit failed: Could not perform drm atomic ioctl: Invalid argument (os error 22) [2026-07-15T17:10:08.846Z INFO jay::backends::metal::video] Trying to disable direct scanout [2026-07-15T17:10:08.943Z INFO jay::backends::metal::video] Initialized connector DP-1 with mode Mode { width: 2560, height: 1440, refresh_rate_millihz: 165003 } [2026-07-15T17:10:08.943Z INFO jay::backends::metal::video] Initialized connector DP-2 with mode Mode { width: 2560, height: 1440, refresh_rate_millihz: 164958 } [2026-07-15T17:10:08.943Z INFO jay::tasks::connector] Connector DP-1 connected (DP-1) [2026-07-15T17:10:18.429Z ERROR jay::client::tasks] An error occurred while trying to handle a message from client 185: An error occurred reading from/writing to the client: An io-uring error occurred: Connection reset by peer (os error 104) [2026-07-15T17:10:18.429Z INFO jay::client] Shutting down client 185 [2026-07-15T17:10:18.429Z ERROR jay::client::tasks] An error occurred while sending data to client 185: An error occurred reading from/writing to the client: An io-uring error occurred: Broken pipe (os error 32) [2026-07-15T17:10:18.429Z INFO jay::client] Removing client 185 [2026-07-15T17:10:18.459Z INFO jay::client::tasks] Client 187 terminated the connection [2026-07-15T17:10:18.459Z INFO jay::client] Removing client 187 [2026-07-15T17:10:18.459Z INFO jay::client::tasks] Client 186 terminated the connection [2026-07-15T17:10:18.459Z INFO jay::client] Removing client 186 [2026-07-15T17:10:18.979Z INFO jay::client] Client 196 connected, pid: 18223, uid: 1000, fd: 82, comm: "ghostty", caps: CAP_DATA_CONTROL_MANAGER|CAP_VIRTUAL_KEYBOARD_MANAGER|CAP_FOREIGN_TOPLEVEL_LIST|CAP_IDLE_NOTIFIER|CAP_SESSION_LOCK_MANAGER|CAP_LAYER_SHELL|CAP_SCREENCOPY_MANAGER|CAP_SEAT_MANAGER|CAP_DRM_LEASE|CAP_INPUT_METHOD|CAP_WORKSPACE|CAP_FOREIGN_TOPLEVEL_MANAGER|CAP_HEAD_MANAGER|CAP_GAMMA_CONTROL_MANAGER|CAP_VIRTUAL_POINTER_MANAGER [2026-07-15T17:10:19.218Z INFO jay::client] Client 197 connected, pid: 18268, uid: 1000, fd: 344, comm: "fastfetch", caps: CAP_DATA_CONTROL_MANAGER|CAP_VIRTUAL_KEYBOARD_MANAGER|CAP_FOREIGN_TOPLEVEL_LIST|CAP_IDLE_NOTIFIER|CAP_SESSION_LOCK_MANAGER|CAP_LAYER_SHELL|CAP_SCREENCOPY_MANAGER|CAP_SEAT_MANAGER|CAP_DRM_LEASE|CAP_INPUT_METHOD|CAP_WORKSPACE|CAP_FOREIGN_TOPLEVEL_MANAGER|CAP_HEAD_MANAGER|CAP_GAMMA_CONTROL_MANAGER|CAP_VIRTUAL_POINTER_MANAGER [2026-07-15T17:10:19.219Z INFO jay::client::tasks] Client 197 terminated the connection [2026-07-15T17:10:19.219Z INFO jay::client] Removing client 197 [2026-07-15T17:10:21.801Z WARN jay::utils::pid_info] Could not read `exe` of pid 18298: Permission denied (os error 13) [2026-07-15T17:10:21.801Z INFO jay::client] Client 198 connected, pid: 18298, uid: 1000, fd: 344, comm: "jay", caps: CAP_DATA_CONTROL_MANAGER|CAP_VIRTUAL_KEYBOARD_MANAGER|CAP_FOREIGN_TOPLEVEL_LIST|CAP_IDLE_NOTIFIER|CAP_SESSION_LOCK_MANAGER|CAP_JAY_COMPOSITOR|CAP_LAYER_SHELL|CAP_SCREENCOPY_MANAGER|CAP_SEAT_MANAGER|CAP_DRM_LEASE|CAP_INPUT_METHOD|CAP_WORKSPACE|CAP_FOREIGN_TOPLEVEL_MANAGER|CAP_HEAD_MANAGER|CAP_GAMMA_CONTROL_MANAGER|CAP_VIRTUAL_POINTER_MANAGER [2026-07-15T17:10:21.801Z INFO jay::client::tasks] Client 198 terminated the connection [2026-07-15T17:10:21.801Z INFO jay::client] Removing client 198

But I don't see any mention to it trying to locking the screen. It does mention disconnecting the monitors from what I see.

[mahkoh]

If the noctalia application starts successfully then you need to look at the noctalia logs.

[witchlliee]

If the noctalia application starts successfully then you need to look at the noctalia logs.

Also nothing in the noctalia log. I let it goes idle and got the most recent things from the log:

Details

2026-07-15 14:56:02.153 [DBG] [notification] notification toast: all surfaces destroyed 2026-07-15 15:00:43.243 [DBG] [pipewire] mixer echo node 74 vol 0.399994 muted false (local vol 1.000000 swMute false) 2026-07-15 15:00:43.434 [INF] [wallpaper] removing instance for output 75 (disconnected) 2026-07-15 15:00:43.434 [INF] [texcache] evicted /home/ellie/Pictures/Wallpapers/wallhaven-rqj837.png 2026-07-15 15:00:43.434 [INF] [wallpaper] skipping DP-2 () — managed by external source 2026-07-15 15:00:43.434 [INF] [bar] removing instance for output 75 2026-07-15 15:00:43.445 [DBG] [pipewire] mixer echo node 74 vol 0.399994 muted false (local vol 1.000000 swMute false) 2026-07-15 15:00:45.064 [DBG] [workspace_ext] active: 3 2026-07-15 15:00:45.065 [INF] [wallpaper] skipping DP-2 () — managed by external source 2026-07-15 15:00:45.065 [INF] [wallpaper] creating on DP-1 (), path=/home/ellie/Pictures/Wallpapers/wallhaven-rqj837.png 2026-07-15 15:00:45.065 [INF] [bar] creating #0 "default" on DP-1 (), thickness=42 position=top reserve_space=true exclusive_zone=42 2026-07-15 15:00:45.066 [INF] [wallpaper] skipping DP-2 () — managed by external source 2026-07-15 15:00:45.066 [DBG] [surface] fractional scale preferred output=DP-1 surface=0x7f898a2616a0 scale=1.000 raw=120/120 logical=0x0 buffer=0x0 2026-07-15 15:00:45.066 [DBG] [surface] fractional scale preferred output=DP-1 surface=0x7f898a3617e0 scale=1.000 raw=120/120 logical=0x0 buffer=0x0 2026-07-15 15:00:45.129 [INF] [texcache] uploaded /home/ellie/Pictures/Wallpapers/wallhaven-rqj837.png 2026-07-15 15:00:45.129 [DBG] [surface] surface configure callback took 62.8ms (0x7f898a316e00, 2560x1440 logical) 2026-07-15 15:00:45.129 [INF] [file-watcher] watching '/home/ellie/.local/state/noctalia/plugins/materialized/official/screen_recorder/recorder.luau' (id 9) 2026-07-15 15:00:45.135 [DBG] [volume_widget] sync vol 1.000000 muted false glyph volume-high node 54 2026-07-15 15:00:45.135 [DBG] [main] wl_display_dispatch_pending took 69.2ms after read 2026-07-15 15:00:45.153 [DBG] [pipewire] mixer echo node 74 vol 0.399994 muted false (local vol 1.000000 swMute false) 2026-07-15 15:00:49.918 [DBG] [workspace_ext] active: 3

So I don't have any idea of what is happening. It looks like Jay isn't even trying to lock the screen with noctalia.

[mahkoh]

You need to figure out if noctalia is using the locking protocol: https://wayfolio.github.io/p/ext_session_lock_v1.html

[witchlliee]

You need to figure out if noctalia is using the locking protocol: https://wayfolio.github.io/p/ext_session_lock_v1.html

Yes it's using it for the lockscreen. I can also run that command in terminal and it will lock just fine.

https://github.com/noctalia-dev/noctalia/blob/main/src/shell/lockscreen/lock_screen.cpp

[mahkoh]

Try to remove privileged=true unless you also start noctalia proper this way.

[witchlliee]

That works. Thanks!