So I’m having issues changing the screen timeout on a fresh i3 setup. I tried commending this line [exec –no-startup-id xset s 480 dpms 600 600 600] That didn’t change anything so tired swapping out 600 for 7200 just trying to extend it to 2 hours but that didn’t work either. I saw somewhere to put [xset s off -dpms &] in an .xprofile in my user folder but i don’t have .xprofile in my user folder so I’m really scratching my head trying to figure out why the system is ignoring the line in my i3 config and what is the system actually getting timeout info from if not there
@Lexi-Alder-Lake ,
There are two groups in parameters of xset.
Does this make a difference?
That seems to have worked i didn’t have xorg-xset installed silly me i just assumed i had it already now when i change the values it actually changed thank you. Now I’m trying to stop the screen from going blurry after 8-10 minutes when i run xset -q it says i have screensaver enabled but in my i3 config that whole section is commended out.
I’m super confused i got the screen to quit timing out but i can’t stop it from blur locking after roughly 7 minutes. I uncommended the line exec – no-startup-id xss-lock -L ~/.config/i3/scripts/blur-lock and now it’s back to timing out my screen but got rid of the blur lock. if i look in the blur lock config it says nothing about the amount of time before it activates or it timing out my screen
exec --no-startup-id xset s 480 dpms 600 600 600
this 480 means locking with blur after 8 minutes.
Let’s leave DPMS for later which as read is not fully compatible with blur-lock.
I ended up figuring it out if i set the dpms line to (exec –no-startup-id xset s 0 0 dpms 3600 3600 3600) and (exec –no-startup-id xautolock -time 30 -locker “/home/username/.config/i3/scripts/blur-lock”) it sets my screen to timeout after an hour and my screen to lock after 30 minutes