this post was submitted on 24 Jun 2023
34 points (100.0% liked)
Linux
33 readers
2 users here now
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One thing I suggest is:
You're trying to get something working but it isn't going anywhere? Try again later.
First, because of the obvious calming down, since stress can affect the person's capacity to solve problems.
Second, I've noticed how many things on Linux have some degree of similarity and/or relation to one another. So trying other things in the meantime can give you the needed insight for solving a previous problem.
Good advice to be honest. Luckily I have a lot of patience so I think I should be fine in the end.
And don't skip over reading things! I also run Arch with KDE and honestly with almost all problems I have, if I carefully read through either the Arch Wiki (this will probably be your most valuable tool) or the error message that comes up, the answer is usually in there somewhere, it just needs digging up.
Also: if something with a GUI crashes and doesn't give an error message, try running it in the terminal. So like, if Firefox crashes and doesn't give any info, try opening up a terminal and running
firefoxfrom there and the terminal will tell you everything that's going on. (It'll be a different command if you're using a flatpak but that's the general idea.)