Noctalia Shell Lockscreen (Quickshell) Still Refuses To Trigger

[Posty2k3]

Distro: CachyOS
WM: Niri
Stasis Version: 0.8.1

Issue: Despite the latest version of Stasis supposedly fixing quickshell lock screen triggering issues, it still refuses to trigger the Noctalia lock screen. I was able to get the config to trigger gtklock correctly using the same exact config file, but Noctalia's will not. Running stasis through terminal in verbose mode shows that the logind detection is returning "b false" as expected, but it still states "Lockscreen already running". I even confirmed that the command you're using to detect the lockscreen already running does in fact return "b false" and "b true" correctly when the Noctalia lock screen is triggered.

Stasis Config:

[Posty2k3]

Also on a side note, the Discord server link on the main page is invalid so I wasn't able to join the server to ask about this. So I created an issue instead.

[saltnpepper97]

Hello @Posty2k3

Thank you for giving stasis a try. yes indeed there was an issue in v0.8.0 can you check the latest git commit and confirm it works for you as it did in my testing?

[Posty2k3]

Unfortunately the latest git did not fix the issue for me.

Version:

Using gtklock triggers as expected:

Using Noctalia's lock screen still results in detecting the screen as already locked and not actually launching the command:

[saltnpepper97]

okay i will have to monitor dbus directly. Give me some time, will probably patch this tonight or tmrw. :)

[saltnpepper97]

@Posty2k3 Hello sir,

I ended up installing noctalia shell myself today after not being able to track it with any method at all

• Hyprland does not expose ext_session_lock_v1 so i can't bind to it in rust or any language for that matter,
• Despite me having it working with detecting via lockedhint the one time it does not want to work any longer

so i decided what the heck let's test this thing and see if i can track the lock process myself. Absolutely no luck. As far as I can see, the ipc for noctalia spawns ephemeral processes for this so it's basically impossible to track unless they expose some way to track lock state easily or provide me with some way to track it lol. So i did the thing of going over there and knocking on their door to let them know that I feel as though that should be a feature regardless for extended functionality of noctalia shell. as in testing with a very basic config with just vanilla quickshell i can use basic processes tracking for the lock but yeah noctalia is a whole nother story. Hopefully we can get this sorted soon enough.

Regards,
Dustin

[saltnpepper97]

Hello @Posty2k3,

I have patched Quickshell myself today in order to get it to emit org.freedesktop.ScreenSaver Active true so that we can track that and so can everyone else!

You can find the pull request here

[Lagrange-X]

I find a not perfect way to trigger the Noctalia lock screen.
Change the config

    lock_screen:
      timeout 1800 # 30 minute(s) after brightness
      command "loginctl lock-session"
      lock-command "qs -c noctalia-shell ipc call lockScreen lock"
    end

It can trigger the Noctalia lock screen, but it have a problem:

[2025-12-20 22:14:15][Stasis] Restarting media monitoring after config reload...
[2025-12-20 22:14:15][Stasis] Starting MPRIS media monitor
[2025-12-20 22:14:27][Stasis] Captured brightness via sysfs: 100/100 on device 'nvidia_wmi_ec_backlight'
[2025-12-20 22:14:27][Stasis] Running brightness command: brightnessctl set 25%
[2025-12-20 22:14:37][Stasis] Running lock-command: qs -c noctalia-shell ipc call lockScreen lock
[2025-12-20 22:14:37][Stasis] Attempting to restore brightness to 100
[2025-12-20 22:14:37][Stasis] Falling back to brightnessctl for brightness restore
[2025-12-20 22:14:37][Stasis] Lockscreen ended — exiting lock watcher
[2025-12-20 22:14:42][Stasis] Captured brightness via sysfs: 100/100 on device 'nvidia_wmi_ec_backlight'
[2025-12-20 22:14:42][Stasis] Running brightness command: brightnessctl set 25%
[2025-12-20 22:14:52][Stasis] Running lock-command: qs -c noctalia-shell ipc call lockScreen lock
[2025-12-20 22:15:07][Stasis] Running DPMS command: niri msg action power-off-monitors
[2025-12-20 22:15:27][Stasis] Running suspend command: systemctl suspend
[2025-12-20 22:15:27][Stasis] Idle timers automatically paused
[2025-12-20 22:15:34][Stasis] Attempting to restore brightness to 100
[2025-12-20 22:15:34][Stasis] Falling back to brightnessctl for brightness restore
[2025-12-20 22:15:34][Stasis] Firing 1 post-lock resume command(s) while locked...
[2025-12-20 22:15:34][Stasis] Running resume command for action: ac.dpms
[2025-12-20 22:15:36][Stasis] System resumed from suspend - resetting state
[2025-12-20 22:15:36][Stasis] Idle timers automatically resumed
[2025-12-20 22:15:42][Stasis] Lockscreen ended — exiting lock watcher

It will reset the progress

[djspacewhale]

I am also having this issue; the action is triggered on time, but Stasis thinks my lockscreen is already running and quits trying. Here's my log from the last run:

➜ stasis -v
debug:   Parsed Config:
debug:     pre_suspend_command = "qs -c noctalia-shell ipc call lockScreen lock"
debug:     monitor_media = true
debug:     ignore_remote_media = true
debug:     media_blacklist = []
debug:     respect_wayland_inhibitors = true
debug:     notify_on_unpause = false
debug:     notify_before_action = false
debug:     notify_seconds_before = 0
debug:     debounce_seconds = 0
debug:     lid_close_action = Ignore
debug:     lid_open_action = Ignore
debug:     lock_detection_type = Logind
debug:     inhibit_apps = [Literal("vlc"), Literal("mpv"), Regex(Regex("steam_app_.*"))]
debug:   Actions:
debug:     lock_screen: timeout=300s, command="qs -c noctalia-shell ipc call lockScreen lock"
debug:     dpms: timeout=300s, command="niri msg action power-off-monitors", resume_command="niri msg action power-on-monitors"
debug:     suspend: timeout=900s, command="systemctl suspend"
info:    Triggering instant actions...
debug:   Instant actions complete, starting at index 0
info:    Stasis starting...
info:    Control socket bound at /tmp/stasis.sock
debug:   User config initialized
info:    Starting daemon...
info:    Verbose mode enabled, log level set to DEBUG
debug:   Loaded config from: /home/dj/.config/stasis/stasis.rune
info:    Config loaded with actions: [lock_screen, dpms, suspend]
debug:   XDG_CURRENT_DESKTOP detected: niri
info:    Starting media monitor
info:    Setting up idle detection (respect inhibitors=true)
info:    Stasis started! Idle actions loaded: 3
debug:   Event loop started
info:    Desktop detected, skipping power source check
info:    Browser media monitor started
info:    Browser bridge not detected, will check periodically
info:    Binding ext_idle_notifier_v1
info:    Binding zwp_idle_inhibit_manager_v1
info:    Binding wl_seat
debug:   Idle detection active
info:    Listening for lid open/close events via UPower
info:    Listening for loginctl Lock/Unlock events
debug:   Trying XDG_SESSION_ID: c1
debug:   Firefox pactl check: playerctl_players=true, uncorked_audio=false
debug:   playerctl players exist but audio corked; checking MPRIS playback status for browser players
info:    Using session /org/freedesktop/login1/session/c1 from XDG_SESSION_ID
info:    Monitoring session /org/freedesktop/login1/session/c1
info:    Listening for system suspend events
debug:   Firefox/browser players appear corked/paused after retries
debug:   No MPRIS players reporting as playing
debug:   Initial check: no media, polling disabled
debug:   Action triggered: name="lock_screen" kind=LockScreen timeout=300 command="qs -c noctalia-shell ipc call lockScreen lock"
info:    Lock screen action triggered
info:    Lockscreen already running, skipping action.
debug:   Lock detected - entering lock watcher loop
debug:   logind LockedHint (c1): b false
info:    Lockscreen ended - exiting lock watcher
debug:   Action triggered: name="lock_screen" kind=LockScreen timeout=300 command="qs -c noctalia-shell ipc call lockScreen lock"
info:    Lock screen action triggered
info:    Lockscreen already running, skipping action.
debug:   Lock detected - entering lock watcher loop
debug:   logind LockedHint (c1): b false
info:    Lockscreen ended - exiting lock watcher
debug:   Action triggered: name="lock_screen" kind=LockScreen timeout=300 command="qs -c noctalia-shell ipc call lockScreen lock"
info:    Lock screen action triggered
info:    Lockscreen already running, skipping action.
debug:   Lock detected - entering lock watcher loop
debug:   logind LockedHint (c1): b false
info:    Lockscreen ended - exiting lock watcher
debug:   Action triggered: name="lock_screen" kind=LockScreen timeout=300 command="qs -c noctalia-shell ipc call lockScreen lock"
info:    Lock screen action triggered
info:    Lockscreen already running, skipping action.
debug:   Lock detected - entering lock watcher loop
debug:   logind LockedHint (c1): b false
info:    Lockscreen ended - exiting lock watcher
^Cinfo:    Received SIGINT
info:    Shutdown initiated: SIGINT
info:    Media monitor shutting down...
info:    App inhibitor shutting down...
info:    Browser bridge detector shutting down...
info:    Browser media monitor shutting down...
info:    Browser media monitor task exited
info:    event loop shutting down...
info:    Main idle loop shutting down...
info:    Lock watcher loop shutting down...
info:    Event loop shutting down...
info:    Shutdown complete, goodbye!
Session summary: 67 scopes, 86 events
  Successful scopes: 67
  Failed scopes: 0
  Aborted scopes: 0
  Total duration: 0ms

with stasis-git from the AUR, using Niri (and Noctalia ofc).

[saltnpepper97]

@djspacewhale, @Posty2k3, @SolitaryDream-X, there is a pull request on the quickshell page that will fix all this, we just have to wait for that to go through then it's a quick patch to stasis and are we are all good!

EDIT: If you mention the importance of the update on the pull request page it might help nudge things along.

[saltnpepper97]

idk if or when they will patch it @djspacewhale, @Posty2k3 , @SolitaryDream-X, @noxxious but you can use my fork of quickshell for now. if one of you wants to package it for arch

https://github.com/saltnpepper97/quickshell

simple quickshell example

import Quickshell
import Quickshell.Wayland
import QtQuick

ShellRoot {
  WlSessionLock {
    id: lock
    exposeDbus: true

    WlSessionLockSurface {
      Rectangle {
        anchors.fill: parent
        color: "#111111"

        Text {
          anchors.centerIn: parent
          text: "LOCKED – click to unlock"
          color: "white"
          font.pixelSize: 28
        }

        MouseArea {
          anchors.fill: parent
          onClicked: lock.locked = false
        }
      }
    }

    Component.onCompleted: lock.locked = true
  }
}

use that with script like this

#!/usr/bin/env sh
set -eu

svc="org.quickshell.SessionLock"
path="/org/quickshell/SessionLock"
iface="org.quickshell.SessionLock"

interval="${1:-0.25}"   # seconds; pass "1" for 1s, etc.

last=""

cleanup() {
  printf "\n"
  exit 0
}
trap cleanup INT TERM

while :; do
  ts="$(date '+%Y-%m-%d %H:%M:%S')"

  if ! busctl --user --no-pager --list 2>/dev/null | grep -q "$svc"; then
    line="$ts  service=missing"
  else
    # busctl output is: "b true" or "b false" -> awk prints 2nd field
    locked="$(busctl --user --no-pager call "$svc" "$path" "$iface" GetLocked 2>/dev/null | awk '{print $2}')"
    secure="$(busctl --user --no-pager call "$svc" "$path" "$iface" GetSecure 2>/dev/null | awk '{print $2}')"
    line="$ts  Locked=$locked  Secure=$secure"
  fi

  if [ "$line" != "$last" ]; then
    echo "$line"
    last="$line"
  fi

  sleep "$interval"
done

and using enable_loginctl for stasis and call loginctl lock and unlock when you get signal from quickshell.

sorry, i hope this helps for now, while we wait for them to merge the pull request on quickshell team.

[Unknight64]

Noctalia now uses their own fork of Quickshell (https://github.com/noctalia-dev/noctalia-qs), maybe you'll get a faster response there.

[Lagrange-X]

Noctalia has now integrated its own idle management