The problem is always having the bad option being enabled by default. Not even the ads are the biggest problem. I didn’t even mention their current ads in the terminal. The problem is the same Microsoft is having now, that your keyboard input gets sent to an untrustworthy third party.
Your comment got cut off. If you wanted to dispute the paid paid claim. It is about Ubuntu Pro, that’s literally all what the basic tier is. We recently even had the case where a patch with a highish CVE rating was only available to subscribers of the service. We also verified that the same patch was already available on Debian. Even without my anecdote it should be obvious why it is bad.
Emphasis on it was. It started to go downhill with Amazon integration and now we have paid security updates. They are holding back developed and available security packages for their OS!
There is no way to still recommend Ubuntu. No need to even talk about the other questionable decisions like snap.
sudo is not simply a tool to give admin privileges, but a tool to manage elevated permissions or run commands in a different users context.
These things become a lot more relevant once you use the tools professionally. In a well configured system you are only allowed to run the things you are explicitly allowed.
To be completely honest sudo is basically pointless in a single user context. There is almost no reason to even have it installed. It makes dealing with different environments easier though.
Anyway as I said it does not matter in many cases if you are the systems administrator. On the other hand there is also no benefit in getting used to bad practices in case you have to unlearn them later.
One more thing: what you suggest with chroot is one of the very reasons why you should not do that. You might have handed over the keys to break out of chroot. It is a well known vector which boils down to never run anything as root in a chroot environment.
sudoedit opens the editor as your user and just writes the file as root. For a single user who is also admin on the system this does not matter in many cases.
In a multi user context you can easily escape your editor and run a shell which allows a non admin user to escalate their privileges. So from a security implementation standpoint this must exist and it does for this reason.
Of course this also prevents some mistakes from happening and a bad plugin cannot destroy your whole system easily and so on. It boils down to good practice.
According to a ProtonDB user the specific crashes I am referring to have been finally fixed with 545.29.02. So two weeks ago for a 5 years old card. Good job Nvidia!
I would have loved having that earlier, because I threw mine out after all the frustration with Nvidia and I still doubt that it is fully working now.
Don’t get me wrong it’s great for others stuck with Nvidia hardware though. I would never ever recommend buying any Nvidia hardware for Linux though. The experience is miserable compared to AMD.
You are lucky if you can play without a crash for even one minute with that card. I am not exaggerating. Something is seriously messed up with the 20XX series.
Also Wayland is still a mess for Nvidia cards overall which is becoming more and more important.
You could try disabling VRR in your display settings. I believe it is set to auto by default if supported, but it does not work properly for some monitors causing flickering.
It feels like you can join in later. There are not thousands of replies in the first few hours. So commenting or participating was a waste of time before in many bigger subs. Noone would ever see your answer anyway or interact with you, so there was really no point.
Here it feels like you are actually participating in some way. I really like it.