Ooops

Nope, this is “Your system ran out of memory and now this program isn’t reacting anymore (it’s trying to allocate memory but there is no free memory left). Please stop the program or try to get rid of some of its subprocesses to free up memory.”

Canonical is basically the closed to corporate Linux you will find on the free distro market… They are pushing stuff you don’t want for marketing reasons (for example their own proprietary Snaps when a better working open source solution already exists with Flatpack), love their telemetry (can be mostly disabled for now, but given the defaults and their other behavior we can already see where this is heading) and in general decide more alongside their latest business plan than actually making sense or listening to users.

But that’s okay as it’s rolling release and unlike other distros you only need to do it exactly once…

My first thought was: So Slackware works very well but is ugly as hell?

But those aren’t affected usually. For them it’s about stability because their certification processes are a lot of work and they won’t risk any interruptions unless absolutely necessary. So they actually pay a lot of money for support beyond the normal EOL.

That’s because the drivers are bullshit but not the problem in general. They work well for some very specific cards, not at all for other and in general it’s just random hit or miss.

And then, to make it more fun, not all wayland compositors are born equal either.

Basically yes. Or: the term is fine; in the eyes of people who never heard or thought about its racist origin.

And your were entirely on the right track when your first comment started with explaining the origin first. When that’s your starting point and you then get the response “But I’ve been saying it for years”, it’s probably far more successful to go with “Yes, but it can be offensive for people knowing its origin, so why not use available alternative terms?” than with “bro it’s been fucking racist for years”. In one case people have a high chance on thinking about it, in the other they will instictively feel attacked and get defensive about it.

I just don’t understand why people are attached to it

Because words aren’t racist, people and opinions and sentiments expressed by them are.

When the term ricing is used for so long and 95%+ of people don’t know where it came from and have zero negative connotations associated with it, your argument (from their perspective) sounds like this:

“Don’t use the term, by its obscure origin you didin’t even know about it is racist”

“I’ve been saying it for years without any racism intended nor perceived”

“bro it’s been you are being a fucking racist for years”

And then you are surprised by the negative reaction…

Correct. There are still games that don’t work because there is actual work being done to make them not work.

I wonder where the problem is… must be Linux’ fault.

There’s probably a chameleon there, but well camouflaged…

You just type ZZ… then the program assumes you fell asleep trying to exit and stops.

I’m still waiting for more distributions to include it to replace my old 3A+ home server.

That’s probably the ugly method but as it’s my personal device I didn’t see a problem adding such things to /etc/environment

PS: You should be able to also set this when starting i3 with “QT_QPA_PLATFORMTHEME=qt5ct i3”…

That’s defintiely the wrong title.

No, it’s not the user catching Linux in trying to pretend user friendliness witht the terminal.

It’s Linux catching the user in still hating it when he gets the wanted user friendliness, for the sole reason of being conditioned to hate the terminal.

Malware for desktop users is the low hanging fruit with little rewards. You just hear about it because it’s so rediculous easy.

The real money is on servers, so that’s were real money/work is invested to develop malware for much higher gains. How successful are they again?

It builds the kernel module for your specific kernel. It’s not different from the nvidia package, that’s just the same thing pre-build for the default kernel (in fact if you install both nvidia-dkms will build the module locally, then realize the exact same thing it just build is already there and move on…).

the correct way to fix it is to first do a system update -Syu and afterwards install the new package

Or you just do it as one step in general: pacman -Syu <package name>

You didn’t upgrade before installing. -y updates the package list to match the mirror, -u updates your system (and you should not use them separately, so if in doubt always use -yu).

So when you try to install (without synchronising the package list first) your system looks at it’s outdated package list, then requests files that are no longer on the mirror as they are already on a higher version.

There’s one caveat here: The UEFI specification doesn’t strictly require the ability to handle more than one EFI System Partition on a drive, so some simply don’t. So this “use a separate boot partition”-method might fail on some computers that just don’t recognize a second ESP on the same drive and only surely works with a whole separate drive for Linux.

Simplified version: SSDs or more precisely NAND flash memory has some technical quirks. You can’t just overwrite stuff like you do with magnetic hard drives. You have to actually delete things. Also you can usually only delete full physical blocks.

But data rarely fits neatly into physical blocks, so instantly deleting data would mean every time you delete something that partly resides in one block, you would need to save the data in that block you want to keep, wipe the whole thing then rewrite parts of it. That’s a lot of unnecessary stress on the hardware and also more work in teh writing and rewriting process.

So SSDs use a similiar approach as old magnetic hard drives. Blocks aren’t physical deleted but marked as no longer used. Which works well for hard drives where you can just overwrite data, but for SSDs this is also far from optimal as with every new write you want to commit you have to pre-check if this unused part of a block is already deleted and usuable or not? In the latter case you either need to do the “save some of it, wipe the block, rewrite” oparation you tried to avoid before or simply go on and try to find another actual free block to use. Which decreases performance obviously. And at some time you would have a lot of wasted half-full blocks and would need to organize your data to reclaim these

Enter TRIM… where periodically (usually when the system is idle anyway) the blocks that are marked as deleted are checked if there’s still used data in it (those are then copied to a completely free block and the whole block is wiped to free it up for the next write.

In layman’s terms it’s basically anolog to defragmenting a hard drive in the brackground. When the drive isn’t doing anything important it spends time rearranging data only partly using a physical block to wipe the whole thing and also to wipe blocks that are completely marked as deleted to keep everything neat and organized with fully used blocks and wiped blocks available for re-use.

PS: so-called continues TRIM is available also. That will basically do the whole “everytime a part in a block is marked as deleted write the other data to a new block an wipe the whole block”-routine in real-time… but after the regular writes are done to not clog up the system. But periodic TRIM is easier on the drive and usually sufficient.

PPS: TRIM is part of the drive’s set of commands. So all the data handling involved doesn’t need to be handled by the file system. You just issue the TRIM command to the drive and it handles everything internally.