THE FIX: Ubuntu and Steam install issues, including exit after accepting agreement

During testing for the Linux build of Alarameth TD, I fired up a Ubuntu 14.04 “live cd” a number of times before finally breaking down and tossing another hard drive in the machine to save the time of downloading the Steam client over and over (and to give the game a test on an upgraded 15.10).

In every case, I ran into hiccups when trying to install Steam. So I’m putting this here for my own future reference (and maybe it’ll help you!).

Problem 1: Steam not starting at all after the downloaded client has been installed and run for the first time.


Solution: For whatever reason, starting Steam through the command line works here, where it fires up the full updater (which grabs the ~224MB client).




Problem 2: After the full ~224MB client has been downloaded and installed, Steam runs and then immediately exits after accepting the agreement / EULA. Will not start up again.


Trying to run manually from the terminal results in a number of libGL errors as follows…

Steam immediately exiting after accepting the agreement.

Solution: Credit goes here for the solution. Since it usually takes me 3 searches with slightly different keywords to find it, the gist is that the libraries that come with Steam are older than the OS’s, causing issues. So removing the ones included with Steam is the solution. To do so, one one of the following chunks pasted into Terminal will remove the necessary files (each set is for a different version, so it’s easiest just try each set – the proper one won’t give “file not found” messages):

rm ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/
rm ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/
rm ~/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/lib/x86_64-linux-gnu/
rm ~/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/
rm ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/
rm ~/.steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/
rm ~/.steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/
rm ~/.steam/ubuntu12_32/steam-runtime/amd64/lib/x86_64-linux-gnu/
rm ~/.steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/
rm ~/.steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/
rm ~/.steam/bin32/steam-runtime/i386/usr/lib/i386-linux-gnu/
rm ~/.steam/bin32/steam-runtime/i386/lib/i386-linux-gnu/
rm ~/.steam/bin32/steam-runtime/amd64/lib/x86_64-linux-gnu/
rm ~/.steam/bin32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/
rm ~/.steam/bin32/steam-runtime/i386/usr/lib/i386-linux-gnu/

…Steam should then fire right back up (try running from the Terminal if not and hopefully you’ll get an indication as to the issue).

Note that similar issues happened when trying within a VM. In any case, issue #2 was the most common for me, with issue #1 only happening when I installed the OS to a hard drive in a bare-metal install.

As a final note, I did run into the same issue with Steam on a few other distros (Fedora, etc), and in some cases the locations are a little different. In those cases, browsing around within the ~/.steam/ directory will eventually result in finding the location of,, etc and they can be removed manually.

Hopefully that helps someone! If it works, doesn’t work, or if you have come across better solutions, feel free to leave a comment below!


 | Leave a Comment

    Leave a Comment

    You can use an alias and fake email. However, if you choose to use a real email, "gravatars" are supported. You can check the privacy policy for more details.

    To reduce spam, I manually approve all comments, so don't panic if your comment doesn't show up immediately.