“However, Valve notes the fact that enabling hardware acceleration on NVIDIA GPUs may cause X11 to crash.”
Nvidia strikes again. :)
That was literally my first day experience with new Steam client. :)
I enabled hardware acceleration and it ended up using all of the GPU memory in a relatively short time.
Fantastic news! thanks
beware NVIDIA tho:
However, Valve notes the fact that enabling hardware acceleration on NVIDIA GPUs may cause X11 to crash. As such, hardware acceleration will be disabled by default for NVIDIA systems. In addition, Valve says that DPI scaling may not work correctly when hardware acceleration is disabled.
I have an NVIDIA card on X11 and just enabled it. I’ll keep you informed ^^.
deleted by creator
Yes please :)
6 days in, no crash yet.
I know, but it’s progress none the less. At this point, I’d be nearly insane to expect this to work with NVIDIA out the gate :/
Oh I agree, any progress is welcome and Valve is doing a fantastic job in making gaming on Linux viable.
I just put the alert in case someone doesn’t fully read the article and go straight into enabling acceleration.
What happened to Nvidia open sourcing their graphics driver last year? It seems like nothing came out of it. I know the userland is still closed, but wasn’t there an effort to include the driver in Mesa?
I’m not too sure, but I wish there was more action from the code being open sourced. I remember reading a little while back some newer code was leaked for NVIDIA as well, but pretty much the similar issue as there hasn’t been too much done with the info as far as I know.
Planning on replacing the nvidia card. Fwiw however, enabled it and hey, no crash thus far. Let’s see. =)
Just updated. Wow. I really like the new look, and it feels much snappier and more responsive.
Always love to see Linux grow
Linux gamers will be happy to learn that this update makes it possible to enable hardware acceleration on the Steam Client
:D
However, Valve notes the fact that enabling hardware acceleration on NVIDIA GPUs may cause X11 to crash.
oh :(
I don’t care about hardware acceleration for a game launcher, but I sure wish they would make it use the native system widgets and theme. They need to reduce the bloat by about 95% as well.
And notifications! I’ve been waiting for them since forever, I really dislike how Steam is the only program I use that does its own thing with notifications, they always appear on top (sometimes with broken animations) and don’t respect the do-not-disturb setting.
My biggest worry around Linux gaming right now, even with all the progress we’ve seen, is that Steam is basically becoming Linux gaming, and it is, after all, proprietary. I don’t love our ability to play games moving heavily into the hands of one, ultimately pretty greedy, private company. Sadly companies like that really want control, and that will always include the bloat they deem “necessary.”
Unfortunately, I don’t think we have a choice. In this capitalist society, money is key to get things moving forward.
Griffais says the company is also directly paying more than 100 open-source developers to work on the Proton compatibility layer, the Mesa graphics driver, and Vulkan, among other tasks like Steam for Linux and Chromebooks. https://www.theverge.com/23499215/valve-steam-deck-interview-late-2022
If it weren’t for Valve, Linux gaming would not be at this advanced stage.
For sure, and I’m stoked about it! Just nervous what things will look like in 5-10 years. Also, thanks for the link, I actually didn’t know they were paying open-source devs. That’s pretty cool and sounds better than the typical embrace, extend, extinguish methods.
Native UI? That’s not Gamer™️ enough. To be taken seriously, you need flashy UIs with broken scrolling, useless animations, unresponsive buttons, and inconsistent widgets.
So I just installed the latest version of Steam on Arch Linux and whenever I start it up it has a popup saying “Failure - invalid app configuration”. After I close the popup, I’m able to access Steam normally, but I’d rather not have to do that on every startup.
Anyone having the same issue?
According to the archlinux wiki:
“If you are trying to run a native game using Proton but get a Steam compatibility tool error immediately after starting the game, you might have to reinstall the runtime.
- Navigate to your Steam library.
- In the dropdown above your game list check the Tools option to make them visible.
- Search for Proton, right click on each installed tool, visit Properties, open the Local files tab and click Verify integrity of tool files for each entry.
- Search for Steam Linux Runtime and repeat the same procedure. If none are available, install the latest Steam Linux Runtime - Soldier.”
Link: https://wiki.archlinux.org/title/Steam/Troubleshooting
So the weird thing is that this issue was happening as soon as I opened the Steam client. I wasn’t even trying to launch a game.
But in any case, what I did was I installed the
steam-native-runtimepackage, uninstalled it, and now the regularsteamclient doesn’t show that error anymore. I’m not quite sure what made it work.However, it seems like I have a new issue. When I start the client, the Store page is completely black, and stays that way until I click on some other tab, and then I click back to the Store tab, upon which the Store page does load.
I know it may sound super basic, because it is, but I’ve learned basic is always a solid 1st fix attempt with Linux…I’d just reinstall the whole thing top to bottom. Recently had an update on my OS which kept failing (days), so eventually I reinstalled the associated packages from top to bottom then boom, update and restart to install. I see it kinda as a “did you power off and power back on the machine” IT tip though lol
Edit: In most distro’s, instead of “sudo install xxx” it’s “sudo reinstall xxx”
You don’t lose any of data in my experience, plus it can fix an array of problems!
I was flabbergasted the new steam client was using 4GB of RAM on its own just by existing for a whole day. That ain’t right, I hope Valve optimizes it.
I look forward to trying this out later
