Usually I start debugging this type of thing by killing all instances of steam and then launching it from command line. Steam logs a bunch of good stuff and putting it in context of your interactions helps. That said, based on what you’ve described, I would try older versions of proton, targeting releases back when games were launching. Proton/wine versions don’t always work for all games and sometimes you’ll need to launch particular titles with specific versions. Proton has been absolutely revolutionary, but these issues still pop up. ProtonDB might have reports on specific versions for specific games/titles.
But what’s strange is that it worked with proton experimental untill this point and that I had this exact same issue earlier on Windows 7 aswell on this same PC. I however did try using proton 8 but that made no difference. I need to try those other versions too
The last one is from 2017, alas. The current Gentoo GUI ISO only includes KDE and fluxbox ( full package list, just in case someone’s really bored and wants a look).
We spent 1 year negotiating implementation of secure Linux workstation, and now after endless meetings and agreements I can proudly say we have 5 people with fully GNU/Linux laptops! Dell XPS, to be precise.
there was some interest in my lug with the different schedulers but attempts at benchmarking all fell within margin of error from our lay attempts at measuring
Case in point. You think quoting an argument and sneering is a counterargument. Obviously, because you don’t know the first thing about labor theory of value.
Someone asked if you think capitalists or engineers did the engineering, and you revealed you don’t understand the question.
You are once again building a flawed model of the dynamic at play here in an attempt to ease the discomfort you feel from encountering something that doesn’t make sense to you (why did I choose to join this community?). I’m not even attempting to build any counterarguments because the responses I’ve gotten don’t even attempt to understand what I’ve said in the beginning. To be utterly frank I just lack respect for people who think of themselves as any flavour of anarchist while still dreaming of a system as thoroughly rigid as the artificially created Internet. You pretend to hate the system while desperately trying to invent excuses for continuing to make yourself at home within it.
No dude, you demonstrably said ‘I’m going to repeat your argument so you can think about it.’ Projecting some emotional state onto me is not gonna change how you fucked this up.
This is mockery. I am calling you ignorant.
I am trying to highlight how you joined an explicitly leftist server, whilst remaining aggressively unaware of… genuinely the first things people learn about leftism. So when you try smugly posturing your way out of a pointed question, you’re just revealing you know less than nothing.
To be utterly frank I just lack respect for people who think of themselves as any flavour of anarchist while still dreaming of a system as thoroughly rigid as the artificially created Internet.
Anarchists being naked hippies, of course, not organized laborers. The internet was mostly designed and operated by academics. It runs on half a century of “does this sound right?” collaborative standards. Whatever browser you’re reading this in has its origins in anti-monopolist diehards building better software out of spite.
None of which is even addressing the initial failure. Capital didn’t design your computer. Intel’s founders definitely did, but only because they were workers dissatisfied under Fairchild, who were in turn workers dissatisfied under Shockley. The early history of silicon valley is halfway to semiconductor co-ops.
Well you solved that conundrum rightly. Now let’s go linch those dirty Apple and John Deere engineers. Since they’ve designed those machines, they must be the only responsible parties for designing them with their extreme anti-consumer and anti-repair policies. They must get commissions on every licensed repair or something, it’s definitely got nothing to do with capitalists putting restrictions on the design team in order to increase profits, nope…
You’re completely off on what I’m getting at. The idea of “Capitalist” hardware, as though the Capitalist did the labor, is wrong. Engineers are paid for their labor power, they don’t typically get royalties or anything of the sort, just like any other laborer.
Someone saying that FOSS software relies on Capitalist hardware is putting the Capitalist over the Engineer, as though the Capitalist created the hardware, and not the labor of the miners, assemblers, designers, engineers, and so forth, regardless of who owns the Capital the labor is done by the Workers. FOSS is agnostic to whoever owned the Means of Proruction of the hardware using or producing it.
Amazing how every single part of your comment is so wrong.
It’s actually a really good analogy,
Not an analogy, an example. Those two are different things.
because it can only run on
No, it can run on many things, including open source collaborative hardware that exists.
fully-capitalist hardware.
What the hell even is that? Fun fact: until very recently most of the computer hardware was made in communist China. I know, scary. And now that a lot of effort is being made to get that production out of there, those efforts are being sponsored by public money to an incredible degree. Billions of dollars of taxes (you know, community resources) are being poured into that because big corporations are the biggest lovers of government handouts.
Hahaha same on the distcc cluster. It was a rare proud moment for me many years ago. I rememeber when I got the cross compiling working it felt like magic. Good times.
Been daily driving Asahi (first ALARM then Fedora when they transitioned) and it’s been exciting to experience in real time how far the project has come. When I first installed, audio didn’t work, the graphics driver was incomplete, and battery life left a lot to be desired. Skip to today and it’s evident how committed marcan and other contributors are to not just porting, but making everything feel right. Highly suggest following him or Lina on Mastodon.
Sorry a bit let to reply, but I’m running on M1 Air and Mini. Off the top of my head, built-in microphone doesn’t work and external displays don’t work through USB/Thunderbolt. Was also having trouble getting my audio interface to work even in class compliant mode. Otherwise it’s a very polished and easy experience.
Why would you use Debian, it has the oldest packages and kernel of all distros. I would maybe run that on a server, but probably just use Ubuntu LTS instead.
For desktop you should try Pop OS. Really good distro from System 76.
Stay away from Ubuntu, it’s very buggy for desktop. I tried it six months ago, fresh install, and the console app wouldn’t even open on a fresh install. No error message, just didn’t open. Great impression…
Care to explain how you come to your harsh judgment of Debian? I’m not a fan of using it as a desktop OS either, but every other day you hear people talking about Debian having newer packages than Arch on occasion. If anything, Debian, Arch, Fedora and derivatives should give you the most recent packages.
I don’t know which people you are listening to, but Debian does not have newer packages than arch. It has older packages than almost all other distros. You can see this on distrowatch for yourself also.
The idea of Debian is that old = stable, which I don’t agree with personally. As an example, users of Debian are reporting tons of KDE Plasma bugs that was already fixed, but because they are running an ancient version, they still have the bugs.
But it depends. It’s correct that new versions of plasma had new bugs, that was fixed in the coming weeks or months.
I guess a better way of describing Debian is that it has old bugs instead of new ones, since it stays on older versions.
Debian has an effective Rolling distribution through testing than can get ahead of Arch.
At some point they freeze the software versions in testing and look for Release Critical and Major bugs. Once they have shaken everything and submitted fixes where possible. It then becomes stable.
The idea is people have tested a set baseline of software and there are no known major bugs.
For the 4-5 releases Debian has released every 2 years (Similar to Ubuntu LTS). Debian tends to align its release with LTS Kernel and Mesa releases so there have been times the latest stable is running newer versions than Ubuntu and the newest software crown switches between Ubuntu LTS and Debian each year.
For some the priority to run software that won't have major bugs, that is what Debian, Ubuntu LTS and RHEL offer.
Debian has an effective Rolling distribution through testing than can get ahead of Arch.
I wouldn’t call a distro “branch” where maintainers say “don’t use this, it’s not officially supported and may even be insecure” an “effective” distribution. I’d consider it a test bed.
Debian tends to align its release with LTS Kernel and Mesa releases so there have been times the latest stable is running newer versions than Ubuntu
Ubuntu LTS.
Ubuntu’s regular channel releases every 6 months, similar to Fedora or NixOS. That in itself is already a “stable” distro, just not long-time stable (LTS).
So Debian can for a short span of time after release be about as fresh as stable distros which is …kinda obvious? I would not consider a month or so every 2 years to be significant to even mention though, especially if you consider that Debian users aren’t the kind to jump onto a new release early on.
For some the priority to run software that won’t have major bugs, that is what Debian, Ubuntu LTS and RHEL offer.
That’s not the point of those distros at all. The point is to have the same features aswell as bugs for longer periods of time. This is because some functionality the user wants could depend on such bugs/unintended behaviour to be present.
The fact that huge regressions have to be weeded out more carefully before release in LTS is obvious if you know that it’d be expected for those “bugs” to remain present throughout the release’s support window.
As an example, users of Debian are reporting tons of KDE Plasma bugs that was already fixed, but because they are running an ancient version, they still have the bugs.
The idea is that those bug fixes would be backported as patches; old feature version + new security/bug fixes.
In practice, that’s really expensive to do, so often times bug fixes simply aren’t backported and I don’t even want to know the story of security fixes though I’d hope they do better there.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.