tell me the most ass over backward shit you do to keep your system chugging?
here’s mine:
sway struggles with my dual monitors, when my screen powers off and back on it causes sway to crash.
system service ‘switch-to-tty1.service’

[Unit]
Description=Switch to tty1 on resume
After=suspend.target

[Service]
Type=simple
ExecStart=/usr/local/bin/switch-to-tty1.sh

[Install]
WantedBy=suspend.target

‘switch-to-tty1.service’ executes ‘/usr/local/bin/switch-to-tty1.sh’ and send user to tty1

#!/bin/bash
# Switch to tty1
chvt 1

.bashrc login from tty1 then kicks user to tty2 and logs out tty1.

if [[ "$(tty)" == "/dev/tty1" ]]; then
    chvt 2
    logout
fi

also tty2 is blocked from keyboard inputs (Alt+Ctrl+F2) so its a somewhat secure lock-screen which on sway lock-screen aren’t great.

  • Snot FlickermanEnglish
    36·
    3 months ago

    I have an old laptop running some basic services.

    I have taken it apart before to replace the hard drive with an SSD, but I never replaced the dead CMOS battery because you have to literally completely disassemble it to get at the battery.

    So I have a cronjob that runs on startup to change the system clock to the right time-zone.

    It just felt simpler than completely disassembling a hard-to-take-apart laptop.

    • piexil@lemmy.world
      2·
      3 months ago

      Debian (and Ubuntu) has the package “fake-hwclock”. I’m sure other distros do too.

      Periodically saves the time info to disk and resets the clock with it on boot.