I've been running steamboat. Linux for a while now and have never had any issues running g it. Sure, there aren't a huge number of games for like us, but that has more to do with the game development ecosystem at the moment. Developing on Windows or Mac is just easier. You have access to all the 3d packages from autodesk and other companies.
https://www.google.no/webhp?sourceid=chrome-instant&ion=1&es...
env LD_PRELOAD='/usr/$LIB/libstdc++.so.6' steam
I have no idea why Valve doesn't make that command the default.Make sure you download Steam from official website, not the version packaged with the distro.
From your link: If you have a 64-bit system, you must install the 32-bit Multilib version of your graphics driver, lib32-alsa-plugins to enable sound, and lib32-curl, lib32-libgpg-error to enable update at first run.
Maybe someone can explain why I need a GPU driver for what is in essence a browser and install wizard? Not being facetious, I honestly want to know why drivers have anything to do with the Steam client working or not.
And is it not time for 64bit Steam client on Linux so that users of 64 bit systems can be free of all these hacks?
Somehow I managed. 'dpkg add-architecture i386' ? Also, the steam client never asked for a driver on my machine. Proprietary nvidia does the magic I need for everything to run.
pebkac?
pebcak yourself, I linked to a very long list of google results for this very problem, suggesting quite strongly that the problem does not just lie with me but with the way in which Valve choose to roll out the Steam client. Or are you suggesting that dpkg -i steam.deb and resolving some dependencies is beyond all of those Linux users? Or maybe the problem does actually lie with Valve.
At this stage in Steam use on Linux, I would say it exists, but it does not appear "supported" by Valve.