First suggestion: commit to using Ubuntu for a set period of time. Could be a week, could be 2 hours. When you encounter issues, force yourself to stay on Ubuntu.

What you’ll find is that at first, errors will seem like gibberish, then you’ll do some snooping online, and find out how to access some log files or poke around your loaded modules. You’ll slowly learn commands and what they do.

Eventually, something will click, ie; “wait a minute, I just checked to see which kernel modules are loaded, and I’m missing one that was mentioned in my error, that must mean I need to load that module at boot.” You load that module, reboot, try your command again, and bam, everything works. You’ve learned how to troubleshoot an issue.

The best way to learn Linux is to immerse yourself in it. You can’t efficiently learn German if, every time you hear a phrase you don’t understand, you switch back to English, right?

Ubuntu Wiki Ask Ubuntu Ubuntu Forums

The wiki has some information and should correspond to how Ubuntu specifically is configured. You can ask for ubuntu specific help in those communities. You can also ask here and on several Linux communities on Lemmy.

The Arch Wiki I find to be more in depth than the ubuntu wiki. Of course some things may differ from Ubuntu’s defaults but I found it a useful resource when using Ubuntu.

Finally I suggest you learn a bit about how Linux works in general, what is in what directory, what is wayland and xorg, understand how drives are named etc and some understanding of the terminal (moving around in directories, how to use sudo etc, no need to learn to make bash scripts).

Just come ask here when you have trouble, and we’ll try to help.

When troubleshooting, the biggest thing is searching the web honestly. But some more things to help you out: look for logs. Linux has loads of logs and sometimes can tell you how to fix the problem.

Logs may not be immediately apparent. Some programs have their own log files that you can look into. Sometimes, if you run the program from the terminal, it’ll print out logs there. Otherwise, you read look through journalctl, although this has logs for everything so might be harder to search.

Another useful tip, particularly for system tools and terminal tools, is manual pages. Just run man ls and replace ls with any command, you’ll get the documentation on how to use that tool.

The first thing I’ll say is the reason you’re more comfortable with Windows is because you’ve been using it for however long and learning to deal with the issues it has. The same needs to be done on Linux. You’ll have to learn how it works just like you forgot you did for Windows.

Second, along with logs like other users said, you have to know how to use a search engine well. Most issues will be easy to solve, but some may take some searching. The Arch wiki is a good resource even if you aren’t using Arch.