I saw that the AUR packages are always at the user's discretion, this does not mean mean downright harmful ones should be mentioned. This package bypasses soname bumps, includes unverified, outdated binaries from dropbox, and has glaring PKGBUILD mistakes such as executable Desktop entries. Do not add it again. -- Alad (talk) 16:07, 23 September 2014 (UTC)AUR package was added again to the article. While
Killing compsitors (Compton)
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
-bswitch to daemonize, making nohup redundant. -- Alad (talk) 14:58, 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"
Native runtime: steam.sh line 756 Segmentation fault workaround
It is currently proposed that the user overwrite package files with files from the Steam runtime. I suggest it would be more elegant to instruct users to copy or link the files into a folder within home which can then be referenced with LD_LIBRARY_PATH.
$ mkdir ~/steamlibs $ ln -s ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libgudev* ~/steamlibs/ $ ln -s ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libusb* ~/steamlibs/ $ LD_LIBRARY_PATH=~/steamlibs STEAM_RUNTIME=0 steam
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)