You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
It seems that swayidle isn't triggering the screen lock as expected per the configured settings in the power saving menu. What's interesting is that it does perform the automatic suspend.
To Reproduce
Log in regolith wayland session on ubuntu 24.04 and regolith 3.2
Set power saving screen blank to 5 minutes
Wait 5 minute
Expected behavior
Screen automatically locks
Actual Behavior
Screen doesn't dim or lock
Screenshots
Configuration file(s)
No additional files configured
Installation Details
Regolith Install Stage: ("current-3_2")
Regolith Version: [3.2]
Host OS: [Ubuntu]
Additional context
Pgrep of swayidle
raman@raman-asus-vivobook15:~$ ps aux | grep swayidle
raman 56575 0.0 0.0 6400 3456 ? S 17:01 0:00 swayidle -w timeout 300 export curr_brightness=$(light) echo $curr_brightness | tee $XDG_RUNTIME_DIR/screen_brightness_old.var if [ 1 -eq "$(echo "${curr_brightness} > 30" | bc)" ]; then light -S 30 fi resume light -S $(cat $XDG_RUNTIME_DIR/screen_brightness_old.var) timeout 900 if on_ac_power; then systemctl suspend fi timeout 900 if ! on_ac_power; then systemctl suspend fi before-sleep swaymsg output '*' dpms off;$(trawlcat wm.program.lock "gtklock -d --background $(trawlcat regolith.lockscreen.wallpaper.file /dev/null)");playerctl -a pause;sleep 1 after-resume swaymsg output '*' dpms on lock $(trawlcat wm.program.lock "gtklock -d --background $(trawlcat regolith.lockscreen.wallpaper.file /dev/null)")
The text was updated successfully, but these errors were encountered:
The current behavior is the screen dims to 30% brightness. Although, what you're suggesting does sound pretty reasonable. The screen should automatically lock.
Ahh that makes sense. My current brightness is usually set low so that explains why I didn't see any changes.
Auto locking the screen is also how the i3 session behaves so it makes sense for the sway session to match. If desired, this is something I can probably submit a pr for if I'm pointed in the right direction of what to update
Describe the bug
It seems that swayidle isn't triggering the screen lock as expected per the configured settings in the power saving menu. What's interesting is that it does perform the automatic suspend.
To Reproduce
Expected behavior
Actual Behavior
Screenshots
Configuration file(s)
No additional files configured
Installation Details
Additional context
Pgrep of swayidle
The text was updated successfully, but these errors were encountered: