Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
but specifically, everything seems fine until
]
I wish I could help more
Padoka has two PPA: Stable and Unstable (or bleeding edge). The OP has Mesa 17.1.4, so he is using the stable PPA.
OP: Could you run Steam from terminal and then run the game using steam UI? I think that we can get more info that way.
I've already tried that, and this is all the information I got. Running from Terminal provides the above messages, and running from the Steam client, the game runs for a little bit but just crashes in the loading stage of starting the game up.
I believe you mean you ran the game directly from terminal, but x_wing suggested running steam from terminal and the game from that steam client, to see the output in the terminal while steam tries to run the game.
Running in Arch Linux 6.4.2-arch1-1 with an Intel i7-6600U, Intel Graphics 520, and Mesa 23.1.3
Here's the output. Basically the same as OP:
I have followed the exact same steps as OP, including reinstalling the game, with one exception: I'm on Arch, therefore I DO NOT have a PPA installed. So whatever is happening seems to not be related to the OP's PPA.
Before this, The first error I got was that libtcmalloc-minimal.so.4 was missing. This is part of the lib32-gperftools library on the Arch AUR. I had the 64 bit version, but it seems Source requires the 32-bit version.
When launching from steam, the game has around a 10% chance of loading like normal. The other 90% causes the game to freeze immediately after the initial load. This made me suspect a memory overflow issue, but my system profile is showing my memory isn't full at all. (5GB/16GB)
Not sure where exactly this started either, but here's some things that happened around the same time, in chronological order.
Any new information on this would be greatly appreciated!!