Frequently Asked Questions

Stasis Not Detecting Apps

If Stasis isn't detecting your applications for idle inhibition:

• Ensure your compositor is supported (see Supported Compositors)
• Start your compositor in a real session context (niri-session, dbus-run-session, or compositor-recommended launcher)
• Check that the app names in inhibit_apps match the actual application names
• Use stasis -v or check ~/.local/state/stasis/stasis.log for detailed logs on detected apps

Regex Patterns Not Matching

If your regex patterns in inhibit_apps aren't working:

• Ensure you're using raw string syntax: r"pattern"
• Test patterns with verbose logging to see what apps are detected
• Remember that River uses process-based detection (fallback) which may have different app names

Service Not Starting

If your systemd service won't start:

• Verify the ExecStart path in your systemd service file points to the correct binary location
• Check service logs for specific errors:

journalctl --user -u stasis.service

Common issues include incorrect binary paths or missing dependencies.

Configuration Not Reloading

If changes to your configuration aren't taking effect:

• Use stasis reload to send a reload signal to the running daemon
• Check configuration syntax if reload fails
• Restart the service if reload continues to fail:

systemctl --user restart stasis.service

Configuration Errors

If Stasis reports configuration errors:

• Validate your RUNE syntax (see RUNE notes in documentation)
• Verify built-in action block names (fixed as of v0.1.2):
  • startup
  • lock_screen / lock-screen
  • dpms
  • suspend
  • brightness
  • * (custom actions can be named anything)
• Check the manual: man 5 stasis
• Use verbose logging to identify configuration issues

Need More Help?

If your problem isn't listed here and you've tried everything: