Ah, gotcha. It’s just difficult to figure out what this does if you’re not already neck deep in configuring status bar JSON

Screenshots showing what this does in action would help a lot

Don’t just look at sdb hits in the log. Open up that entire session in journalctl kernel mode (journalctl -k -bN where N is the session number in session history) and find the context surrounding the drive dropping and reconnecting.

You’ll probably find that something caused a USB bus reset or a similar event before the drive dropped and reconnected. if you find nothing like that try switching power supplies for the HDD and/or switching USB ports until you can move the drive to a different USB root port. Use lsusb -t and swap ports until the drive is attached beneath a different root port. You might have a neighboring USB device attached to the bus that’s causing issues for other devices attached to the same root port (it happens, USB devices or drivers sometimes behave badly.)

Always look at the context of the event when you’re troubleshooting a failure like this, don’t just drill down on the device messages. Most of the time the real cause of the issue preceded the symptom by a bit of time.

Time to train an LLM to format XML and hope for the best

Openssh backdoor via a trojan’ed release of liblzma

I bought a hybrid AMD/Nvidia laptop in 2021, installed Arch, the Nvidia dkms driver and flatpak steam and everything I wanted to play just worked. Getting gaming up and running is so much easier now thanks to valve’s work on proton.

Same experience on two more machines after.