Reply To: Disabling screen blanking lock-out

[DaveForum Admin]

Here is the command from set-screen-blank used to set the blanking.

 os.system("xset dpms "+str(blank_time_value)+" "+str(blank_time_value)+" "+str(blank_time_value)+" s "+str(blank_time_value)+" "+str(blank_time_value)+" ")

As well as record the value set there in desktop-session.conf. Here is what desktop-session does with that recorded value.

 #Finally Set the screen blank time / screen saver
        if [ "$SCREEN_BLANK_TIME" = "0" ]; then
            echo_cmd xset -dpms; 
            echo_cmd xset s off; 
            echo_cmd xset s noexpose;
            echo_cmd xset dpms $SCREEN_BLANK_TIME $SCREEN_BLANK_TIME $SCREEN_BLANK_TIME s $SCREEN_BLANK_TIME $SCREEN_BLANK_TIME;
        else
            echo_cmd xset +dpms; 
            echo_cmd xset s on; 
            echo_cmd xset s expose; 
            echo_cmd xset dpms $SCREEN_BLANK_TIME $SCREEN_BLANK_TIME $SCREEN_BLANK_TIME s $SCREEN_BLANK_TIME $SCREEN_BLANK_TIME;
        fi

Which as can be seen by the comment is last loaded. This is why startup commands for screen blanking are overridden.

Also commenting the line out will cause the config check script to not see the option and readd it. This is handled in /use/(local?/)lib/desktop-session/ds-config-check to prevent errors/crashing due to missing parameters.

Not sure which one of the xset commands cause the crash. Is it just the zero value? Maybe an enable option is needed in the config?

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown