About fucking time!

I still prefer OsmAnd, far more feature, and at least you can ask it to avoid a specific road. Organic Map cannot.

Maybe the Murena version, but the official one is stock android with all its trackers.

Now if they could add proper USB support so we’d be able to upgrade the firmware of Windows only controllers (looking at you 8bitdo Ultimate), that’d be great.

An unstoppable fuck colliding with an unmovable fuck.

As will any moz://

Probably trough the commandline, it has been a long time since I last checked, but not using the gui, which asked for the password for any repository modification.

But you still need to add the remote… With a root password of course. At least last time I tried.

A good example of shitty YaST imo is the YaST sudo tool… Which doesn’t work unless you first manually edit the sudoer file to remove two lines that specifically says that they are default configurations and should be changed by the distro maintainers…

Why the fuck does it ask for root password to change every little thing? Want to change network password? Root password. Install a flatpak? Root password. Sneeze? You guessed it, root password.

I’d be using it instead of Fedora if it wasn’t for that shit. I even tried to spin myself a custom OpenSuse ISO…

Looks alright to me.

Not a specialist, but I suppose it has to do with having different configurations for different top level folder. In Unix-like systems, every top level folder have a different purpose, and what works for the root may not for /tmp, /swap, etc.

In those example, no need to snapshot /tmp, as it is a forder whose file are bound to be deleted, and for which being able to restore has no use.
/swap is pretty similar , and is often formated with a dedicated filesystem.
/usr often only change during the package manager transactions, so snapshots are often tied to that, while /home may be set to keep daily snapshots.

Pedantic? Say the person that immediately assume anyone with a different opinion than his is a morron and did not read his previous message ?

Here is some gaming benchmark. It is from 2022, sure, but is still relevant today to illustrate that gaming performance on Linux isn’t as easy as being the “same software with different configuration”.

And I could go on with other games, which had different results.

There are many variables that can affect those performance. Obviously, the Kernel, Driver and Mesa version has a big influence, but so have some less obvious causes like the filesystem used, the compiler options used, or even the compiler itself. That’s why those performances can vary so much in benchmarks.

Phoronix many benchmarks proves the opposite. There is differences, even at the same Mesa/Kernel version.
The difference between an hyper optimized distro, like Clear Linux (optimized for Intel CPUs), and more general ones (Ubuntu, Fedora) can be huge.
Even between those general purposes distro, the technology choices (filesystem, scheduler, etc.) can make a considerable difference in some games/workloads.

Too bad it is nVidia only.

For overclocking you have LACT.

You can also change this behavior in libzypp configuration file, if I recall well.

Unfortunately not.

“The XDNA driver will work with AMD Phoenix/Strix SoCs so far having Ryzen AI onboard.”. So only mobile SoC with dedicated AI hardware for the time being.

On OpenSUSE, in Yast bootloader tool, there is a checkbox to to do something like locking the bootloader (it has been a while, I don’t remember the exact thingy). Rebooted and oh, surprise, the bootloader was locked… Which mean Grub didn’t load.

I had to reinstall the whole OS 🤣

Proton experimental moves quite a lot. Maybe they moved to a new version of something that broke your install for a reason or another.