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.

  • delirious_owl
    3·
    3 months ago

    Open a bug report with the school network admkn. This is default android behavior and a privacy issue to boot

    • ReveredOxygen@sh.itjust.worksEnglish
      2·
      3 months ago

      Android is fine because you’re able to use a web browser to get an auth key. You have to register devices where you can’t do that, and it seems to be impossible in the case of the pixel watch

      Edit: Also, they’re not concerned about privacy. They want to know who every device belongs to

      • delirious_owl
        21·
        3 months ago

        That never works for me on Android systems. It probably needs some shitty Google service.

        You have a right to privacy. Its your school. They work for you.