From ArchWiki
Jump to: navigation, search

Mention steam-native-runtime in main wiki?

Hello, new contributor here, so I am wanting to gather opinions on what would be my first contribution to the wiki.

In my experience, the steam-native-runtime was incredibly useful back when I was using mesa on an AMD graphics card, and to help solve some issues with specific games.

Would this be worth mentioning in the main Steam wiki page? It's only mentioned in the troubleshooting page, so it could be missed by some new users to Arch. Murnux (talk) 00:56, 29 June 2017 (UTC)

steam-native-runtime was originally used as a workaround for issues in the Steam runtime. However recent Steam updates and changes to the Arch package have largely made such workarounds unnecessary. The native runtime package is also not a perfect workaround: its monolithic so you end up installing tons of packages you might not need, it may break certain games that expect older runtime libraries, and it might be missing certain libraries that are present in the Steam runtime but not in the Arch package potentially breaking games as well. For these reasons, I recommend that Arch users try installing just steam first and running with the Steam runtime. If issues arise, we have the troubleshooting subpage.
The native runtime still has its uses: some Arch users like using newer libraries than Steam packages, and newer libraries might actually fix bugs in certain games. But I don't think it needs to be mentioned in the main installation section.
Silverhammermba (talk) 05:34, 29 June 2017 (UTC)

Killing compsitors (Compton)

Instead of

killall compton && %command%; nohup compton &


killall compton; %command%; nohup compton &

be better as it does not rely on compton running when you start up a game? I've been frustrated more than a few times when I'd start a game, forgetting that compton wasn't running and the steam game would hang. —This unsigned comment is by Wartz (talk) 15:38, 9 March 2015‎. Please sign your posts with ~~~~!

I think both are terrible. The proper way would be to to read the compton manual and adjust the configuration accordingly (i.e unredir-if-possible = true). But if you did use a command like this, know that compton has a -b switch to daemonize, making nohup redundant. -- Alad (talk) 14:58, 9 March 2015 (UTC)
Thanks for pointing me in that direction. unredir-if-possible seems to work fine with fullscreen games instead of outright killing the compositor. I'm not sure how much of an effect the compositor has on windowed games though. Wartz (talk) 17:30, 9 March 2015 (UTC)

Hardware decoding for In-Home Streaming

For Intel Graphics


For NVIDIA Graphics

First, make sure that lib32-libva-vdpau-driver is installed from the AUR. Then, move the old steam vdpau folder out of the way:

mv ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/vdpau/ ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/vdpau.bak

Then, link in the vdpau folder from your system:

ln -s /usr/lib32/vdpau ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/.

To prove to yourself that it's working properly, make sure you have "Display performance information" ticked in your steam settings on the client under In-Home Streaming/Advanced Client Options. Now when you start streaming, press F6 on the client. The "Decoder:" line should show "VDPAU hardware decoding"

An update of the steam-runtime will likely overwrite these changes. Greyltc (talk) 12:29, 15 April 2015 (UTC)

How to read Minidumps?

Set up Steam and have been playing around with a runtimeless install. It seems to work okay sometimes, other times it seems to randomly crash, giving minidumps that sit in /tmp. I'm familiar with using gdb to backtrace coredumps but these minidumps are something else, and I'm having a hard time finding out how to actually use them to figure out what's going on. Anyone have any clues? If so, that's perhaps something to add to this page. Insidious611 (talk) 16:10, 28 April 2016 (UTC)