search

ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.25k stars 175 forks source link

Steam beta crashes on start #7511

Open framingnoone opened 3 years ago

framingnoone commented 3 years ago

Your system information

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist Expected to happen: Type "steam" to launch steam. Steam runs, and lets me pick games Did happen: Type "steam" to launch steam. Steam starts, displays "pins may be out of date rebuilding", and finds libraries it needs. Then it crashes out after finding everything.

Steps for reproducing this issue:

Run steam. Output to console in gist below. https://gist.github.com/framingnoone/b42c03e4515adabd0ecf322ac51fb41e

It appears that a crash log was uploaded somewhere as well, though I can't be sure that's what the last line meant.

WanBatkong745 commented 3 years ago

This also started happening to me since yesterday, I'm on Linux mint 20 and I keep getting this error despite previous commands

cat: '/home/user1/.steam/debian-installation/ubuntu12_32/steam-runtime.tar.xz.part*': No such file or directory
tar: This does not look like a tar archive
xz: (stdin): File format not recognised
tar: Child returned status 1
tar: Error is not recoverable: exiting now
find: ‘/home/user1/.steam/debian-installation/ubuntu12_32/steam-runtime’: No such file or directory

I've tried everything on https://askubuntu.com/questions/1038754/steam-wont-start-on-18-04 and I've also tried completely uninstalling and re-installing. This just started happening to me somebody please help :\

Thanks in advance.

kisak-valve commented 3 years ago

Hello @WanBatkong745, you've described the issue mentioned at https://github.com/ValveSoftware/steam-for-linux/issues/7467#issuecomment-727225721 instead of the issue reported here.

TTimo commented 3 years ago

Looks like this gentoo does not have a VERSION_ID entry in /etc/os-release like our steam.sh seems to expect, but I don't think it's related to the crash.

kisak-valve commented 3 years ago

The unbound VERSION_ID scenario has been known for years and is a red herring. Specific feedback from a Gentoo user: https://github.com/ValveSoftware/steam-for-linux/issues/3695#issuecomment-578406539

TTimo commented 3 years ago

The fatal assert is pretty widespread and not distro specific. Our crash database is seeing it happen on ubuntu and manjaro installs as well.

TTimo commented 3 years ago

@framingnoone how reproductible is this? Happens occasionally, or 100% preventing you from starting steam?

If this is 100%, can you make it happen a few more times and provide the CrashID upload entries that went with it?

Do you have a VR headset setup, or connected at all?

framingnoone commented 3 years ago

Answer to first and second questions: At the time of original posting, this crash was 100% of the time I tried to run steam, no matter how many times I tried to start steam. I would say it's 99% of the time though as I did manage to login and run steam successfully once during the several attempts I made to provide more CrashIDs.

assert_20201210172110_15.dmp[10802]: response: CrashID=bp-762db570-f0b5-4af6-bcb1-5345b2201210 assert_20201210172110_15.dmp[10802]: file ''/tmp/dumps/assert_20201210172110_15.dmp'', upload yes: ''CrashID=bp-762db570-f0b5-4af6-bcb1-5345b2201210''

Steam did let me log in once, looked like it was working normally, aside from multiple copies of these warning messages in the log (probably 5?)

--begin warning messages-- TagLib: Could not open file /home/larry/.local/share/Steam/steamapps/common/PAYDAY 2/PAYDAY 2 the Soundtrack/FLAC_versions/OVERKILL Soundtracks - The 12 Days of Xmas.flac TagLib: FileRef::audioProperties() - Called without a valid file. TagLib: FileRef::tag() - Called without a valid file. TagLib: Could not open file /home/larry/.local/share/Steam/steamapps/common/PAYDAY 2/PAYDAY 2 the Soundtrack/FLAC_versions/OVERKILL Soundtracks - The 12 Days of Xmas.flac TagLib: FileRef::audioProperties() - Called without a valid file. TagLib: FileRef::tag() - Called without a valid file. --end--

More CrashIDs from testing: src/common/pipes.cpp (839) : Assertion Failed: fatal stalled cross-thread pipe src/common/pipes.cpp (839) : Assertion Failed: fatal stalled cross-thread pipe src/common/pipes.cpp (839) : Fatal assert; application exiting src/common/pipes.cpp (839) : Fatal assert; application exiting assert_20201210173540_15.dmp[13522]: Finished uploading minidump (out-of-process): success = yes assert_20201210173540_15.dmp[13522]: response: CrashID=bp-08c96b9e-3482-471a-a75e-6162c2201210 assert_20201210173540_15.dmp[13522]: file ''/tmp/dumps/assert_20201210173540_15.dmp'', upload yes: ''CrashID=bp-08c96b9e-3482-471a-a75e-6162c2201210''

[same] CrashID=bp-fb969de1-4ee0-4f42-8d68-6da372201210 CrashID=bp-ed8ef2ef-e5b8-49e1-b677-c81972201210 CrashID=bp-90aab476-362a-48d6-9da8-4956f2201210

Answer to question 3: I have no VR headset (connected or otherwise).

TTimo commented 3 years ago

Thank you for the additional CrashIDs.

So were you able to update to the latest beta, and the problem still occurs (version 1607563631 atm)?

framingnoone commented 3 years ago

Yes, still happens with 1607563631

TTimo commented 3 years ago

I think Steam is getting stuck (or at least very very slow) while doing the initial parsing through of your installed games.

Steam's output would have something like this once this task is done and unblocks the rest of the startup: CApplicationManagerPopulateThread took 249 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)

And your ~/.steam/steam/logs/content_log.txt would have entries like this (one line per Steam library):

/home/timo/.steam/steam/logs/content_log.txt:764:[2020-12-11 10:06:08] Loaded 24 apps from install folder "/home/timo/.local/share/Steam/steamapps\appmanifest_*.acf".
/home/timo/.steam/steam/logs/content_log.txt:765:[2020-12-11 10:06:08] Loaded 14 apps from install folder "/opt/SteamLibrary/steamapps\appmanifest_*.acf".

It may be just one corrupted game install causing this. You will likely need to move aside the *.acf files under steamapps/ in your library (rename to .acf.off for instance) to find the culprit.

framingnoone commented 3 years ago

I did get a "you have two directories called steamapps and SteamApps this will cause issues" warning a while ago, and attempted to combine the two directories carefully. Perhaps not carefully enough. Some .acf files are "rw-" permission, and some are "rwx", which is probably an artifact of the merging attempt.

Might be worth trying just changing either the "rw-" or the "rwx" permission ones?

Without making any changes, tried with new 1607650432 build, got ''CrashID=bp-7148dcc3-48ba-4ae6-ab55-74c022201211''.

Moving every .acf to .acf.off, and steam started OK this time (Hurrah!).

What are the main issues I'll get from renaming these acf files?

framingnoone commented 3 years ago

I've looked more closely, and there are several appmanifests pointing to directories like "Rust", where "steamapps/common/Rust" exists, but is empty (containing no files). That's almost definitely part of the problem.

Also there's at least one empty directory ".local/share/Steam/steamapps/common/Satisfactory", with another directory "/mnt/movies/steamapps/common/Satisfactory" with the actual install in it.