You are not logged in.
I just wanted to share a wild troubleshooting story with neofetch on Arch, in case someone else ever stumbles into the same rabbit hole. It was a really weird edge case.
The problem was whenever I ran neofetch in my home directory, instead of the usual system info and ASCII art, it would print out what looked like the contents of my /etc/bluetooth/main.conf file. I mean, literally pages of Bluetooth config. If I ran neofetch from other directories, it worked fine and showed the expected output.
What I tried:
* Checked $PATH, $HOME, and all the usual suspects for weirdness – everything looked normal.
* Made sure there were no aliases or functions shadowing neofetch.
* Reinstalled neofetch (even though it’s now only in AUR, not official repos).
* Nuked my ~/.config/neofetch directory and let neofetch regenerate it.
* Tried running with --config none and also in a clean environment with env -i.
* Checked file permissions everywhere.
* Compared my environment to a test user, where everything worked fine.
* Even tried different shells and minimal configs.
It only happened in my home directory, and only on my main user. Other users, or running neofetch from /tmp or anywhere else, worked as expected.
After way too long, I finally noticed I had a file called auto in my home directory. Turns out, at some point I must have saved a copy of my Bluetooth config as ~/auto (no idea why). Neofetch, depending on its config or maybe some edge-case logic, was picking up this auto file as an ASCII/logo source or similar when run from the directory where it existed.
I deleted the ~/auto file, and boom – neofetch went back to normal in my home directory.
If neofetch is showing you something totally unexpected, check for stray files in your current directory with names like auto, especially if you’ve ever played with custom ASCII/logo/image settings. Sometimes the bug is just a forgotten file with a magic name!
Hope this helps someone else avoid a few hours of head-scratching!
Offline