Objects is too unspecific, so I will just assume something like this:

The people constantly talking about gaming on Linux are the meme.

In actual reality you just play your games without yapping about invented problems or imaginary benefits.

Defaults badpass_message="YOU SHALL NOT PASS!"

ILoveCandy

I might be biased but there could simply be some degree of objective assessment involved… *spitting looking at you snap*

Well… let me explain what this wrapper does…

I am so terrified of a future where people have hallucinate their own perfect AI companions and no longer understand that they need any actual human friends.

Yeah, I heard that several times but decided to try it anyway.

But I expected problems with Steam not with flatpak itself just removing the very same graphics driver it had just installed as a dependency…

Flatpak just working would be a nice thing. Everytime I try they fuck something new up…

(Last time I thought about installing Steam via Flatpak on Arch to get rid of all the multilib 32bit stuff not needed for aynthing else anymore it worked for nearly 4 days. Then flatpak update randomly uninstalled its nvidia drivers because an “update” removing the old package first, then realizing it can’t find the new one make total sense of course.)

But those Arc cards actually look good (for the low budget segment they are in that is…) and are mainly held back by lackluster drivers. So I get the decision.

As many as are driving the correspondig vehicle legally on streets.

Would be nice if this was the only (or one of just a few) Realtek chips that are a fucking mess…

There might a common problem with those Realtek devices but I fail to find it. 😅

I would assume people running a modern kernel on an orignal 32-bit first generation Pentium machine don’t need such an excuse as they have to do it constantly already…

I’m pretty sure the unmodified/-optimized kernel doesn’t even fit the RAM of 1990’s Thinkpads.

EVs are inherently cheaper that CE-based alternatives.

So unless this is about stopping the 24/7 propaganda of fossil fuel lobbyists, it’s just some useless PR stunt.

“Teams” is what came to mind for him first when he thought of online meetings. To me that suggests […]

People who haven’t touched Google with a ten-foot pole for years still “google” stuff in general conversation because that’s what people generally understand. People who never used Twitter (or that modern renamed far-right bot paradise) talk about stuff that got “tweeted”.

So no… associating colloquial use of terms with actual habits doesn’t work well.

Trust the slob! Learn to love the slob! Slob is life!!

We just need to create that one single ultimate community for good linux jokes.

We are talking about 40k here, so dying will probably be the nice outcome you hope for…

it’s getting more prevalent as more stuff (especially servers) run on Linux […] Linux’s days of living in “security through obscurity” are over"

Servers are primarily running Linux for decades. So any security through obscurity would be gone for as long, if it even existed ever…

though I’ll admit to not having tested that sort of thing with Wine/Proton installed

The more primitive the better the chances. And there are some really primitive cases of ransonware perfectly happy with running through Wine and encrypting your files. So limiting Wine’s file access (or better running it as a separate unpriviledged user with no access to anything but your games) is always a good idea.

pacman -S vulcan-mesa-implicit-layers

Which will then probably tell you that it conflicts with vulkan-mesa-device-select and asks if you want to replace it. Which might either work or just get you another conflict because vulkan-mesa-device-select is required by some other package.

Btw… pacman -Qi <package name> usually tells you anything you need to know about a package. In this context mainly why it was installed (as a requirement for which package) and which other packages are required as a dependency.

So maybe you should take one step back first. Check why 'vulkan-mesa-device-select` was installed in the first place. If it’s not dependency of something else you can either remove it (or replace it) alongside its lib32 version.