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.

  • ReveredOxygen@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 months ago

    The Pixel watch has this problem too. However, it randomizes the MAC per network, so that strategy won’t even work. I’ve tried to get it from the debug log but failed I’ve resigned that it won’t be getting connected to the school network

    • Trainguyrom@reddthat.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      What is it with these schools and not just using WPA Enterprise? They already hand out an email to every student so it makes it dead simple to deactivate the account’s PSK upon terming the student