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.

  • Avid Amoeba
    link
    fedilink
    arrow-up
    30
    ·
    3 months ago

    I think NDISwrapper is still maintained for issues like this.

    • eldavi@lemmy.ml
      link
      fedilink
      arrow-up
      19
      ·
      edit-2
      3 months ago

      i wasn’t aware that you could use ndiswrapper on an access point; i’ll look into it.

      UPDATE: googles says that you can’t do this because ndiswrapper uses windows drivers that don’t support ap mode.