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)
Check that the app names in inhibit_apps match the actual application names
Use stasis -v or check ~/.cache/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

💡 Tip: Run Stasis with verbose logging (stasis -v) to see exactly what application names are being detected, then adjust your patterns accordingly.

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 you're using the correct built-in action block names (they are fixed as of v0.1.2):
- lock_screen / lock-screen
- dpms
- suspend
- brightness
- custom-* (for custom actions)
Check the manual: man 5 stasis
Use verbose logging to identify configuration issues

Brightness Not Correctly Resetting

If brightness controls aren't working properly:

⚠️ Video Group Required:

Check the logs with cat ~/.cache/stasis/stasis.log. If you see warnings about setting brightness, you need to add yourself to the video group:

sudo gpasswd -a <user> video

Log out and back in for the group change to take effect.

Input Timer Increasing Randomly

If the idle timer keeps counting up even while you're using your mouse or keyboard:

⚠️ Input Group Required:

Ensure your user is in the input group:

sudo gpasswd -a <user> input