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.
We just need to create that one single ultimate community for good linux jokes.
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.
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 - If CachyOS keeps with its usually sane naming structure the package you should first update, just to be sure, will named cachyos-keyring, but no guarantees there…), 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.
I did not mention the US (who are just now trying very hard to become a failed state anyway) but was talking about other power production. No one but lobbyists still riding the dead horse that is nuclear power is caring for who dominates in construction of new reactors when that’s a very small fraction of added production capacity, globally as well as in China.
Making yet another story about some “big push for nuclear” when it’s actually just varying levels of stagnation and decline while renewables show exponential growth is either colossally stupid of bullshit propaganda.
Not that those fairy tales about a nuclear future with renewable upbuild collapsing any day now are new as we all should know by now:
Funny story.
And now give us numbers how those “dominance in nuclear upbuild” compares to power production in general…
Being lazy and having update-related issues with nextcloud too often for my taste I went back to the basics (as that’s all I actually use 99% of the time) with Syncthing for file syncing and Radicale for caldav/carddav.
rolling release (for gaming)
Seriously… after all these years without some pesky version upgrade screwing things up I couldn’t bring myself to install a non-rolling distro on any device I actively use.
And I only recently learned that a separate vimdiff command exists (not that it makes a difference over vim -d)…
Arch live ISO gives you arch-chroot which does all the binds automatically
That isn’t neccessary. nvidia-open automatically replaced nvidia (same for nvidia-open-dkms, nvidia-open-utils etc) when 590 hit and installing any of those nvidia-580xx packages will ask to remove them because they conflict.
It should be illegal to use pacman without pacman-contrib installed for checkupdates (no risk of partial upgrades) and for comparing and merging .pacnew-files with pacdiff…
While the distinction can be important, the snapshots from right before the update are exactly what you want in this case over some actual but always somewhat outdated real backup
“Doesn’t help” is a bit unspecific for an actual answer.
I simply installed nvidia-580xx-dkms and nvidia-580xx-utils and that was all. If you did not already use the dkms-driver package before you of course also need <your kernel>-headers and dkms (but the latter should be pulled as a dependency for nvidia-580xx-dkms anyway)…
Which automatically asks for the removal of nvidia-open (the standard package for the base linux kernel) or nvidia-open-dkms and nvidia-open-utils that replaced the earlier nvidia, nvidia-dkms, nvidia-utils packages when 590 hit.
PS: If you still have stuff using 32bit add (you might have guessed the scheme by now…) lib32-nvidia-580xx-utils to replace lib32-nvidia-open-utils
nvidia was automatically replaced with nvidia-open (also nvidia-open-lts, nvidia-open-dkms etc).
Simply installing nvidia-580xx-dkms, nvidia-580xx-utils (and lib32-nvidia-580xx-utils because Steam still needs all that 32bit stuff), which automatically removes the 590-open stuff because of conflicts, should be all you need to do.
PS: And of course your kernel’s header package if you did not use dkms before… (dkms should be pulled as a dependency automatically)
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…