I ran into a problem where Teams was stuck loading. On the few times I could get it to load, it would display an error page telling me to “Try Again” and to try “signing out”, neither of the links would do anything.
I was able to fix it by running:
pkill teams && rm -rf ~/.config/Microsoft/Microsoft\ Teams/Application\ Cache/Cache/*
Teams is kind of a disappointment on Linux. I have to use it, so hopefully that helps someone ( or me again in the future).
After I updated my desktop to Linux kernel version 5 when I logging in my network would disconnect/reconnect every 15 seconds or so. I wasn’t able to get on the internet. My ethernet cable was plugged directly into my motherboard and I don’t have wifi capabilities.
I had a bit of trouble getting Rider set up initially to handle my dotnet core projects on Manjaro. Rider wouldn’t open the projects complaining about not being able to find SDKs like razor and web. My first stop was Settings->Build, Execution, Deployment->Toolset and Build. I messed around with those settings to no avail.
Pointing to the MSBuild.dll within my dotnet installation seemed to be the kicker, over the one that came with mono. But I also changed my dotnet core executable path to /opt/dotnet/dotnet from /usr/bin/dotnet at the same time. Once I got it working, I didn’t want to mess with it anymore, so here it sits.
I don’t like typing “nautilus” to open the folder explorer from the terminal. Mac’s “open” command is shorter and makes sense to me. To get the same command in Ubuntu, we just have to add it to bash aliases.
Open up ~/.bash_aliases to be edited. I usually use nano.
Add this line
When using the terminal, to open nautilus in the current folder, you can run this command
open . &
The “&” detaches the process from the terminal and is optional.
I had an issue that came about suddenly while working. Every now and then my cursor would jump to the upper right corner and lock to the taskbar. I couldn’t find any pattern to explain it. I tried:
activating/deactivating the trackpad
swapping my mouse out
cleaning my touchscreen
The issue persisted. I noticed that my touchscreen wasn’t responding, so as a last step, I tried temporarily deactivating my touchscreen. The problem then went away. After a reboot, my touchscreen worked properly and the cursor no longer jumped. I have no explanation as to why, but here is how:
That will give you a list of inputs with IDs. The touchscreen entry should be pretty obvious. Mine is ‘Synaptics Large Touch Screen’. Note the ID. It should be a single or two digit number.
You will be prompted at this point to choose between GDM and LightDM. I chose GDM at first, which I read was fine if Gnome was going to be used solely (sharks don’t look back!). I understood that LightDM is the option to choose if you are going to flip between the two. GDM caused me some graphic driver issues that left me unable to boot. I ended up in recovery and ran the above again, this time choosing LightDM. All good after that.
To get the better looking gnome login screen, run: