Linux @lemmy.ml squid_slime @lemm.ee 3mo ago

What is the most duct-tape thing you've done to Linux?

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.

175

You're viewing a single thread.

175 comments

Got fed up of Pipewire suspending (old receiver takes ~2 sec to work again after spdif stream is cut) that now I auto-run aplay to play a silent .wav on loop
- But there is a setting to disable that? I don't remember where I found it because I don't remember where to find any settings, but you can definitely disable automatic shut off of audio devices.
  
  Yes, you kinda can disable suspend, but it will still cut off spdif transmission even then. Normally that wouldn't be an issue but my receiver is super old and takes its sweet time to start actually playing audio after it gets a signal
  
  Ah, didn't know it worked differently for spdif, never had anything nice enough to use it.

175 comments