I know whenever I try to help someone with a Linux issue it’s always an uphill battle to get them to stop guessing what they think the problem might be and show me the logs.
People really don’t want to give you the information you need to help them.
I make sure to give my guess and also append as many logs and exact information as possible, right down to every step I took that produced the problem.
So far my success rate with the forums is 0%. But hey, people at least tried to be helpful!
I know whenever I try to help someone with a Linux issue it’s always an uphill battle to get them to stop guessing what they think the problem might be and show me the logs.
People really don’t want to give you the information you need to help them.
I make sure to give my guess and also append as many logs and exact information as possible, right down to every step I took that produced the problem.
So far my success rate with the forums is 0%. But hey, people at least tried to be helpful!
To be fair, people who know which logs to attach and how to get them usually already know enough to troubleshoot the issue by themselves.
You’d think so, but the logs often contain a ton of noise along with the one line that tells me what the actual issue is.
This is such a hard part of learning Linux. “Just look at the logs” Which logs? Where? How?
journalctl > logs.txt(don’t actually do this)(what does this do?)
By default, it saves all your system logs in a text file, starting from the moment you installed your distro.