• Re: PC monitor is freezing, but I can ssh into it and operate okay

    From Dan Ritter@21:1/5 to Tom Browder on Wed Dec 11 14:40:01 2024
    Tom Browder wrote:
    I can ssh in, reboot, and all is well. Is there any way to completely turn off the screen saver and its timer via system settings?

    There are three things that could be called screen saver
    settings:

    - the console blanker is controlled via
    setterm -blank 0
    (the 0 is minutes; 0 to disable blanking)

    - the X11 basic setting is
    xset s off
    and the "don't use display power management at all" is
    xset -dpms

    - This may be overrules by a desktop environment like GNOME or
    KDE, in which case you need to look at
    gsettings set org.gnome.desktop.session idle-delay 0
    or something similar.

    - whatever X or Wayland screensaver you use to draw
    fancy toasters or mazes will have its own command, e.g.
    xscreensaver-command --exit


    -dsr-


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tomas@tuxteam.de@21:1/5 to Tom Browder on Wed Dec 11 16:20:01 2024
    On Wed, Dec 11, 2024 at 09:01:19AM -0600, Tom Browder wrote:
    On Wed, Dec 11, 2024 at 08:21 Tom Browder <tom.browder@gmail.com> wrote:

    On Wed, Dec 11, 2024 at 07:14 Dan Ritter <dsr@randomstring.org> wrote:

    Tom Browder wrote:

    ...

    I can ssh in, reboot, and all is well. Is there any way to completely
    turn
    off the screen saver and its timer via system settings?

    There are three things that could be called screen saver

    ...

    Thanks, Dan, I'll try those and report back.


    My system didn't recognize anything you suggested except:

    # gsettings set org.gnome.desktop.session idle-delay 0

    Interestingly, all the other commands before AND AFTER the reboot responded:

    unable to open display ""

    This one is because they have to "talk" to the right X server, so they
    need the DISPLAY env variable set, to know which one.

    On your (probably) single machine with (probably) just one X server
    and one display, try prefixing the command with a var setting like
    so:

    DISPLAY=:0 <my command with args>

    [...]

    Cheers
    --
    t

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZ1msagAKCRAFyCz1etHa RoahAJ9n/SC9WjAa0zlJ/gFnJwCKabvGeACePm0OjLQ/5e4LJIuE5i47nR9MBvw=
    =xWKg
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tomas@tuxteam.de@21:1/5 to tomas@tuxteam.de on Wed Dec 11 16:20:01 2024
    On Wed, Dec 11, 2024 at 04:14:58PM +0100, tomas@tuxteam.de wrote:
    On Wed, Dec 11, 2024 at 09:01:19AM -0600, Tom Browder wrote:

    [...]

    unable to open display ""

    This one is because they have to "talk" to the right X server, so they
    need the DISPLAY env variable set, to know which one.

    On your (probably) single machine with (probably) just one X server
    and one display, try prefixing the command with a var setting like
    so:

    DISPLAY=:0 <my command with args>

    (of course, this will only work if there /is/ an X server running
    in the first place :)

    Cheers
    --
    t

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZ1mtEgAKCRAFyCz1etHa Rl0mAJ0cCQyP2xWfkrJhn8gqT864qAUExACeLrG5/wuD5esjllMiEZPbWRpm0CU=
    =C+4W
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Ritter@21:1/5 to tomas@tuxteam.de on Wed Dec 11 17:10:01 2024
    tomas@tuxteam.de wrote:
    On Wed, Dec 11, 2024 at 04:14:58PM +0100, tomas@tuxteam.de wrote:

    DISPLAY=:0 <my command with args>

    (of course, this will only work if there /is/ an X server running
    in the first place :)

    (of course, if there is no X server running, only the console
    setting has any meaning. Or whatever Wayland does.)

    -dsr-

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From eben@gmx.us@21:1/5 to Tom Browder on Wed Dec 11 20:20:01 2024
    On 12/11/24 07:33, Tom Browder wrote:
    I can ssh in, reboot, and all is well. Is there any way to completely turn off the screen saver and its timer via system settings?

    There may be related problems with my newly installed HP printer which sometimes hangs when attempting to print random web pages (I don't do it intentionally but I'm sometimes "forced" to as a "honey do" task).

    If you think something is actually running and the monitor's in some power-saving state, you can use "ddccontrol" to change the power-saving
    state. Here's how I turn each monitor off and on in turn (in sh):

    alltext="$("$DDC" -p 2>/dev/null | sed -n /Detected/,/^Reading/p)" devices="$(echo "$alltext" | grep '^ - D' | cut -f 4 -d ' ')"
    for device in $devices ; do
    echo -n '-=>' $device
    echo " ($(echo "$alltext" | grep -A 3 "$device" | grep 'Monitor Name' \
    | cut -f 2 -d : | colrm 1 1)) <=-"
    for state in off on ; do
    case $state in
    off) ddcstate=5 ;;
    on) sleep $sleeptime # this assumes this happens last
    ddcstate=1
    esac
    echo -n "$state "
    "$DDC" -r 0xd6 -w $ddcstate "$device" > /dev/null 2>&1
    done # for state
    echo
    done # for device

    There are probably better ways to do it. One of my monitors is pretty slow, which is why sleeptime is as high as it is. Adjust to taste.

    If nothing is happening, this won't help. But OTOH it probably won't hurt either.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)