The i3 Autostart Trap: How One Line of Code Hijacks Your Config
· 2 min read
For months, I was haunted by a ghost in my machine. My i3 config, which I had carefully crafted, was behaving erratically. Scripts that were supposed to run on startup would sometimes fail. Worse, a hideous black-and-white noise screensaver would randomly appear, despite my explicit commands to disable it. I had gotten so used to the randomness that I accepted it as a fact of life.
Today, that ended. The culprit was found, and it's a lesson in how seemingly harmless "convenience" features can wreak havoc in a minimal environment.