aT LEaZt iT wErKz

HARDER!

Heroic Games Launcher supports GoG pretty well. You can install it with Flatpak using Discover in desktop mode.

When you login to GoG and install a game, you will be able to “Add it to Steam” (top-right hamburger menu in game’s view) and it should then be available in your “Non-steam games” in gaming mode.

Other options are Bottles and Lutris

The thing with trying different distros drives me a bit nuts. If you’re getting consistently bad results across so many different ones, then you can see how distros don’t matter all that much after all. What really matters is your hw config combined with software config. Stop trying different distros expecting that some of them will maybe do something differently, stick to one and try to figure out the problem or ask for help. Only resort to other distro if you know that it will make something easier (eg provide more up to date packages).

You said what’s your hw configuration, but not much about how you handle NVIDIA drivers. By default, your GPU will run on open drivers built in Linux kernel called Nouveau, combined with OpenGL (and for your GPU that’s it for now) implemented in Mesa. This is enough for basic things to work, such as the desktop, video playback, office applications, but not necessarily games. For that you need the proprietary NVIDIA drivers. Check manual of your currently used distro for how to get those drivers in place. For your GPU even the newest drivers are available (560), so it’s good if your distro offers that. For drivers older than 555 series, use X11 session instead of Wayland.

Exactly, while RTFM I haven’t have a single issue (apart from the driver quirks itself) and even automated the driver patching for NvFBC. Usual error is using nvidia-dkms and not setting up proper hook to rebuild the kernel module on kernel updates.

What are you talking about? I wish I could do stuff like installing or managing my Arch installations more often, as it’s very relaxing and satisfying. The problem is, my installs never break and there’s nothing to do about them most of the time. I work in IT however and my job throws rocks at me all the time with some bullshit corporate software and horrible Sysadm/DevOps practices and boy’oboy is it frustrating….

It hasn’t change since mid-2000s if you only talk about the installation process itself. Usually you would have at least some piece of hardware that wouldn’t work out of box and it used to be a lot of work until getting everything in place

Hell yeah, improved Mafia Classic gaming

AFAIK, the xz vulnerability was designed for Debian based on its workaround fixing systemd service status detection. Even if it shipped to something like Arch, the malicious code wouldn’t load.

The problem with HDR is that it’s very difficult to get working on X11, to the point that those who tried (NVIDIA, 8 years ago) gave up long time ago and moved on. X11/Xorg is legacy solution that is still there mostly because it always was and things still depend on it.

Wayland can get HDR and it gradually does, but it wasn’t priority for quite a long time as there was much more basic stuff missing, to the point many users wouldn’t switch until recently, and because X was still the preferred display system for most users for such a long time, it wasn’t priority to fill missing gaps on Wayland side and it wasn’t moving forward too fast.

Now that things are coming together, over half of the user base (probably) already switched to Wayland, there are more desktop/WM options on the Wayland side, with fewer showstoppers every year, finally NVIDIA drivers start working on Wayland, color management is also getting closer to be part of the official spec. It’s already possible to play games in HDR, but with some solvable caveats: if a game runs on X11 (which for Wine/Proton the Wayland driver is still experimental) they use swap-chain hack to that’s only available in the gamescope compositor, so either in full blown Steak Deck session or wrapped in nested gamescope instance. This will be more out-of-box when:

1. the stable color management protocol is actually in place, more compositors implement it (currently only gamescope and kwin_wayland have HDR)
2. winewayland.drv stabilizes and implements HDR
3. Wine and Proton run on Wayland natively by default

Around 12 years ago, I was able to break Debian or Ubuntu installs on weekly basis due to certain packages being too old, something being missing from repos so being forced to compile stuff manually, dealing with junky 3rd party repos etc. Then after switching, I hardly ever messed anything on Arch while also spending less time tweaking it than I did with Ubuntu. Even if I did break something, it was my fault. And it’s not that I cannot handle Debian-based OS installs if I have to. I think those systems are fine if they work for you by default and stock repos contain everything you need (and it’s usually enough for servers) The problem is, it’s not always like that and you just have to add some custom package (prepared by you or someone else) every once in a while, not necessarily with an official support. This is just plain easier on Arch.

Would change distro to something easier to maintain (like Arch for example), rice the experience to the oblivion, keep it forever :3

There were some recent fixes to Steam VR but I have never tried a VR headset myself. It should work on Wayland with a compositor that supports DRM-leasing protocol, so basically everything but GNOME.

Interesting with that overly formal tone. Might be due to how school english focuses on correct grammar and vocab, but not necessarily how people actually speak casually. At least that’s how I remember English in high school.

Azure stuff (like az CLI tool) is generally available on Linux, I used it to provision services using Terraform. Things like .NET or MSSQL all have official support on Linux now.

Virus is just a program that tries to whatever its malicious intent is while being as minimal and portable as it gets. It it’s a ransomeare to encrypt all your data or a program that looks for passwords in your files, it can still be fairly successful when running through Wine. There is a chance through, that it assumes typical paths where Windows keeps files and if it never tries other drives than C, it will only affect Wine prefix and not your actual files.

You can run Bottles in Flatpak and cut out access to any of your files if you’re afraid it can be malicious

Torrent edition worked flawlessly with no need to tinker at all. Just saying

Is HDR now possible for Wine with winewayland.drv or is it still wrapped in Gamescope and use the WSI Vulkan layer?

Microsoft hasn’t changed all that much. They don’t see Linux as an OS to run games or MS Office with. It’s not a consumer platform and never will be, it’s more of a server/container maaybe workstation system for a tech-savvy/developer/scientist. Its UI is meant to open terminals and text editors, not movie players or game launchers. Microsoft loves Linux until it leaves the business area and try to sneak into consumer market. There’s nothing stopping them from doing harm to desktop Linux with all their „love” to Linux the modern mainframe system that happens to be industry standard. They can still patent things and do legality tricks (like in HDMI forums), try to put Windows on devices where Linux could be competition (one Linux handheld console = 10 more new Windows handhelds), bind consumers with something only Windows can run (Xbox Gamepass?) etc

The MS distro you’re talking about already exists - it is called Azure Linux (recently renamed from CBL-Mariner).

Would work better with Fortnite