At a quick glance, the Sweet Ambar Blue SDDM theme has two versions – one for Plasma 5 and another one for Plasma 6. You probably want the one for Plasma 6. You can check which version of Plasma you’re running in System Settings -> About this System -> KDE Plasma Version.

Be extremely careful when installing Plasma/SDDM themes. They are user-submitted, not always reviewed, and can contain arbitrary code. There have been incidents involving malicious damaging code downloaded through Plasma global themes.

Naw, everybody knows that you have to use regex for that

People who consciously use and support F/LOSS usually do it because they look at software with a very critical eye. They see the failures of proprietary software and choose to go the other way. That same critical view is why they are critical of most “AI” tools – there have been numerous failures attributed to AI, and precious little value that isn’t threatened by those failures.

jq, and its Yaml sibling, yq.

If you want something Debian-but-not-Ubuntu-based, give LMDE a try.

Sounds to me like the kernel or the video driver died. Try pressing caps-lock a few times – if the keyboard’s LEDs don’t change, your inputs are dead and pretty much your only option is to power down or reset the computer. Most modern filesystems, like ext4 and btrfs (you likely have one of those) are very robust and can easily handle an ungraceful shutdown. When you start the OS again, it’ll run fsck on the root partition and get it into a functional state. Data loss can still occur if the computer dies while a process is still writing a file, but I think it was inevitable the moment the OS froze.

Unfortunately I can’t offer much advice other than to use a numbered Proton version instead of experimental, and to try again at a lower quality setting. You should also try Gamemode to temporarily optimize your system for running games.

I’ve played RDR2 on a weaker system than yours. It’s a very intensive game to run in terms of memory usage, streaming from mass storage, and CPU/GPU. Install it on an SSD to give it the best chance, and use a system monitor like bpytop or htop to check the RAM/CPU stats and temperatures.

Fuck, I mixed up my musicians, I meant David Bowie!

Bon Jovi David Bowie and Harambe were the cosmic glue that kept the universe’s shit together. Nothing’s been normal since their deaths.

Make fun of the shitty parents instead who named their kid X-A- (ah fuck I don’t know how to type that character, THE POINT IS FUCK MUSK)

If you want addictive, try Stardew Valley and Factorio. I think both have Linux-native releases on Steam. I’ve got 182 hours in Factorio. The factory must grow.

(edit) ah fuck I fell back into Factorio again

deleted by creator

Remember to install the Activate Linux program to let it harrass you until you do!

Is it even possible to use any kind of authentication with NFS other than Kerberos?

why is it listed as the last version that does contain it everywhere?

I don’t know, but the official advisory is most likely to be correct. Everything else is a game of Chinese whispers where the information becomes less reliable the more it is passed on. Maybe it’s because -2 still had Jia Tan’s signing key, and could have, theoretically, accepted commits signed by them.

Where is it listed as such? Can you give examples?

TL;DR: starting with 5.6.1-2, XZ is safe on Arch. Safe as in not affected by this particular vulnerability.

Look here: https://gitlab.archlinux.org/archlinux/packaging/packages/xz/-/commit/881385757abdc39d3cfea1c3e34ec09f637424ad

And here: https://security.archlinux.org/ASA-202403-1

5.6.1-2 is where the package switched from building from the tarball (backdoored) to the upstream git repo (clean). The tarball release contained some extra build instructions (which didn’t exist in the git repo) that added the backdoor during the build process. The issue arose from the downstream maintainers’ assumption that the contents of the tarball and the git repo were identical.

Subsequent changes, and 5.6.1-3, were mostly administrative, like changing the git repository’s URL (since the maintainer’s github account was banned) and locking out Jia Tan’s PGP key.

an article which said that in 5.6.1-3 the backdoor was “fixed” by just not letting the malware part communicating with the vulnerable ssh related stuff

That article is bullshit, don’t believe a thing it says. Arch was not affected by the SSH vulnerability because the sshd binary did not link liblzma where the backdoor existed, so they could never communicate in a way that could be exploited by this particular vulnerability. It was not part of the fix.

This is my go-to guide for virtualization on Linux desktops: https://www.youtube.com/watch?v=h7SG7ccjn-g The first part covers the Linux (Manjaro) installation. 12:00 is where GPU passthrough starts (see below), and 21:00 is where he sets up the virtual machine.

The video shows how to use KVM, or Kernel-based Virtual Machines. It’s a hypervisor built into the Linux kernel and much more performant than VirtualBox, but a bit more work to set up. If you give the VM about 6-8 GB RAM and at least 4 CPU cores, it’ll happily run Win10 at a reasonable speed and 25-30 FPS (assuming your computer is strong enough, as most of this load is CPU-bound). You won’t be using it to watch HD videos, but I think it’s good enough for office-type applications. Even now I’m using a Win10 VM to manage a domain controller.

One thing the video doesn’t cover is to install the spice-guest-tools service on the VM from spice-space.org to facilitate host-to-guest communication (SPICE being the protocol that shows you the VM’s graphical output, not unlike VNC).

put a VM fullscreen over both displays on one workspace and give it full power / resources

It’s called GPU passthrough, and not something I’d tell a new user to attempt. It requires some advanced tinkering, a second GPU (unless you’re willing to attempt a single GPU passthrough, which is even more sketchy), and a prayer to the Omnissiah. It involves detaching the PCI device from the host OS and handing it over to the VM so only the guest OS can use it. You can then attach a monitor directly to that GPU or use the Looking Glass application on a multi-GPU system to display the output in a window.

I like working with Linux Mint atm but I wouldn’t mind trying a different one as well

If you’re comfortable with Mint, it’s best to stay. Virtualization will work more or less the same. If you’re looking for an Arch-based distro, consider EndeavourOS. It’s basically Arch, but with an out-of-the-box experience comparable to Mint. Manjaro is another similar choice, but I can’t recommend it because they’ve made some choices that make updates risky and system maintenance a pain.

Defended Kotaku sucking up to SBI, downplayed and ignored SBI’s harrassment campaigns and the apparent racism of some of its employees. There’s also some conflict of interest because his company is in bed with SBI. I skimmed through most of the videos, it’s really not worth my time.

According to some comments, he also said some ridiculous things in support of SBI’s witch hunt against a particular Steam user on twitter, but I won’t go wading into that cesspool, so can’t verify.

Man, why do people publish serious announcements on April 1st? Between the XZ backdoor that almost pwned all of Linux, a Silksong update, Bellular News taking some absolutely degenerate stance with games “journalism”, and this, I don’t know what the fuck to believe.

Then let the thought comfort you that talentless sacks of shit are running NPC streams on tiktok and making more money than you.

Both sides ARE bad. The trick is to use critical thinking and realize that one side is “stupid and misguided” bad and the other is “literal nazi, genocide against minorities, and also very stupid” bad.