I guess I’m just really lucky, because I almost never run into those. Sometimes I find the good ol’ xkcd DenverCoder9 problem:
Lost user: (Random Monday Five Years Ago, 7:00 pm) Hey, here’s your exact problem, down to the specific language on the error message even.
Lost user: (Random Monday Five Years Ago, 8:30 pm) nvm figured it out
<Thread was locked for inactivity>
But even more often than that I actually get frustrated in the other direction:
Lost user: Hey, I’m having a problem with totally-not-grombl.
Experienced user: Oh yeah, I’ve seen that. Just run sudo grombl reload -skqq --xbs-juju '2793' and then restart your desktop environment.
Lost user: Oh thanks, that totally worked!
Meanwhile I’m like…but why did that work?! It was a completely different package and there’s no indication why the two would even be related…? And sure, it did work, but I’ve learned nothing now.
I guess I’m just really lucky, because I almost never run into those. Sometimes I find the good ol’ xkcd DenverCoder9 problem:
But even more often than that I actually get frustrated in the other direction:
Meanwhile I’m like…but why did that work?! It was a completely different package and there’s no indication why the two would even be related…? And sure, it did work, but I’ve learned nothing now.