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

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.

Deporting or locking away citizens and members of the legislature… a totally normal thing to do in a democracy.

I assume they plan to win elections in the very same way the nazis did… after the opposition was banned and/or locked away.

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.)

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

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.

Oh, I actually fully believe that they can’t live without it. That’s simply what happens with drug-induced brain-damage…

While it’s much better than the brain-rotting alternative, this move comes much too late. And I’m not talking about the fact that screens are already everywhere, that’s a totally different topic… but to late for their kids (middle school here…) in particular.

Screens instead of pen, paper and other tools (as well as movement in general) are even more damaging in the earlier years when fine motor control, perception skills and abstract thinking is in full development.

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.

Former president and failed candidate in the 2020 presidential election Donald Trump…

Strictly speaking both statements are correct, so why now?

Here’s where it’s going:

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.

and in some cases anti-ICE activists

So it’s only a matter of time until they just fake those violent anti-ICE activists they always hallucinate about to justify their insane behavior.

Sadly the people that refused to pay to get informed and love to rage about imaginary stories they got from reading headlines only, don’t deserve any better. They killed journalism despite massive amounts of warnings and now have to live with the idiot circus that replaced journalism.

If history is any indication ICE will sadly have to first become bigger, more influental and have a leadership developing their own ambitions before the “dropping them like a bad habit” happens… alongside awarding lots of Ernst-Röhm-Memorial-Awards.

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.

That’s a totally separate error… It can happen that the keyring itself is so out of date that it blocks the update, and with it the upgrade to a newer keyring. For this reason it’s often safer after a long time to do pacman -Syu cachyos-keyring (pretending I guesse right and that’s the name of the package) first to avoid the whole update getting blocked by signature with an out-of-date-key. Yet that should not apply here.

But Ignoring the warnings you get for now… This looks like vulkan-mesa-implicit-layers did not replace vulkan-mesa-device-select but now the 32bit library version lib32-vulkan-mesa-device is supposed to be replaced by cachyos/lib32-vulkan-mesa-implicit-layers, which would in turn need vulkan-mesa-implicit-layers as a dependency.

What happens when you answer ‘no’ to that first question? Alternatively, is there anything keeping you from installing vulkan-mesa-implicit-layers (thus replacing vulkan-mesa-device-select)?

Not using CachyOS but Arch… but after a long break from updates you should probably start by checking if your mirror is still up-to-date (doesn’t look like it when you local stuff is newer…).

Again… not my OS but this seems to be the file you could use to manually replace the mirrorlist in your /etc/pacman.d/ directory.

Edit: Also just to be sure… -Syyu will force a refresh of all databases (doubling the u would force “upgrading” even it’s an actual downgrade from your local version). You normally don’t do it because it puts extra load on the mirror, but in case of problems it won’t hurt.

PS: For the future (and although partial upgrades are normally to be avoided)… after a long break in updating the key breaking points are mirrors, then keyfile (they can be so out of date that you can’t start the update - so do them separately first), then pacman itself…

The latter is very rare but there have been a handful of major changes in pacman’s lifetime that broke down compatibility after a long time. Arch keeps a static pacman version available for these cases, so you can still do a proper update to fix it, but don’t know where CachyOS keeps it’s equivalent.

2nd Edit for sake of completion: A quick searched seems to indicate that CachyOS does not have a separate static pacman. So if everything else fails and it’s an actual problem of pacman itself (and only then, so please don’t try that just now) https://pkgbuild.com/~morganamilo/pacman-static/x86_64/bin/pacman-static has the static standalone version of pacman. So you can download this file, make it executable and run it.