[BUG] Failure to unpack steamrt-heavy (and maybe more prerequisites) on some distribution (Void), cause SteamVR to not be able to start #511
Comments
|
Did it show you a prompt to finish SteamVR setup on first launch? |
yes First launch after installing it did showed the prompt and then asked for my sudo passwd, which i did. And then nothing happened just "crashed", after reinstalling it it asked again but yea nothing |
|
And just to be clear, it keeps asking you to finish setup on every launch now or? |
oh no sorry i miss phrased, it just asked me once after first launch after install and then only once after first launch after a reinstall |
|
Oh gotcha, can you run |
|
|
You're missing almost a thousand files compared to my Linux SteamVR beta install, verify the integrity of the tool files in Steam |
I already did that more than once, and it's just say "all 5129 files successfully validated" |
|
Thats... unusual to say the least, anything interesting in the Steam console when you start it? It should usually say the reason for the crash there |
Nothing interesting but so the dump, that i already shared here in my issue (and the missing folder runtime and sdk) |
|
Strange, i'll check out the dumps tomorrow, but if it fails on startup it's probably missing something/something is setup incorrectly |
|
This is happening to me as well, I just installed SteamVR today. Looks like the sdk and runtime dirs in the SteamVR folder don't exist. @okawo80085 do you happen to have those dirs in your SteamVR folder? I'm not seeing the dirs in your diff, which I think would show up? If it's worth anything, I had to manually run setcap on vrcompositor-launcher in order to get past the initial setup popup. EDIT: I don't think the directories not being there is a problem actually. Looks like it's finding the runtime elsewhere. |
Im pretty sure I have them, so I'll follow up on that tomorrow |
oh? how do you to this? |
|
@Naia-love If you don't get an error when trying to launch SteamVR, you're probably fine. When you launched SteamVR for the first time, did it pop up with something asking about superuser access? If it was successful, you're all good. Mine wasn't, so I had to set it manually. #234 |
https://gist.github.com/kedodrill/0a10efe0a6213240b3376d5cc38bb716 I do not have |
|
@kedodrill Yeah Altho it's strange, i remember a similar bug when SteamVR just failed to load |
Actually, I switched to beta because it wasn't working on stable for me, and so I wanted to try if beta was actually working or not ^^' |
|
I tried unpacking manually the steam-runtime-heavy.tar.xz, I now seems to have all the files you have in your own steam-runtime-heavy folder? but I still get exactly the same error |
|
in the terminal when starting it, but it still complain about the sdk but I have no idea if i'm on the right track to make it work |
|
It still fails to find the runtime, but the more pressing issue is that the runtime should've been present from from the start. @kisak-valve any idea on what went wrong during the setup or how to fix it? |
Naia-love
changed the title
|
any update on that? |
|
I don't see any mentions of fixes in the recent SteamVR beta updates, im assuming it's still not working on your end as well |
Yep, tried to update to last beta, uninstall and reinstall, but nothing for now ^^' |
|
There has been a few Linux related updates, is your issue still present? |
Hi sorry Also i just realised, I dont know how I missed that all the others times (but now that i realised it, Ido recall it happening lasts times^^; ) I'm guessing this is related, I could try installing it again with like steam running in a terminal to try and check if errors appears here |
Please do just that. |
for some reason it didn't crashed this time :^) and I still have this issue |
|
Another Void user here having this exact same issue. Same error, same missing files, same behavior, so on and so forth. |
|
...so of course, once I've said I'll try to get a log from it, it stops happening. Go figure. |
|
@kedodrill I have the exact same segfault in dmesg, down to the same code |
|
@Orthestral @kedodrill I also have the exact same message on Void Linux. It used to work at least a month or so ago. |
Yeah, it hasn't happened once since then. No idea what changed. |
|
Steam also has a chance to crash a few moments after starting up, giving me this error in dmesg: |
|
Is there a workaround for this issue? I've been playing around with using an open-source stack to replace SteamVR (OpenComposite + Monado + libsurvive), which works-ish for some games, but it'd be nice to be able to play Alyx with my shiny new Index controllers. |
There might be, try to play around with beta versions of SteamVR, it has a few old releases for Linux, but those are like old old, somewhere around 1.15.x iirc |
Finally caught it in action: https://pastebin.com/jpxLkezz If there's a particular file in steam/steam/logs or something that might be useful, someone let me know and I'll post it too. |
|
From steam/logs:
|
|
Hmm... a lot of these logs, including vrserver.txt, don't have anything in them past last March 11. I guess that's the last time I used it before it broke or something. (Yikes.) vrserver.txt in its entirety is too big for pastebin, but here's the last part after vrmonitor initiates a quit all: And here's vrmonitor.txt: Not sure, but this all looks like maybe it's just a normal shutdown to me. Elsewhere, vrclient_steam.txt seems to be looking for oculus drivers, despite the fact that I don't have an oculus. (Maybe that's normal?) Then post March 20, all the entries are just sort of empty? All of the log files that have entries more recent than March 11 are like that. vrhw_*.txt don't even exist. There's only a couple of .vdf files. |
|
This still appears to be a issue, I am getting the same errors on a void system. |
|
Not sure if this has anything new in it, but I tried running Steam with Prior to that, before I've done anything, it does say: |
|
No more useful info from Going off of the log timeline from @DeepwaterCreations, the issue seems to have started with update 1.21.12 |
|
I just tried it today, and it seems to work now! Will update if anything goes wrong. |
|
For me seems that it got fixed! I read here and there that valve pushed a lot of linux fix recently, |
|
Matches my experience: It's been working for me, too. |
|
Ok so i was not able to reply to this for a while cuz of literal war, but i can now and i got a void distro now with SteamVR on it, the catch is that for it to work properly (or at all with nvidia drivers) the Steam package needs to be installed properly, its often missed by users when just installing using Without them either Steam wont start or SteamVR wont be able to complete initial setup -> wont be able to start either. I've tested my particular build of void for a few months now, SteamVR is more or less stable, i have tracking, all of my devices are working, apps that launch under proton work fine as well, there is some tracking jittering, but im pretty sure thats cuz the nvidia curse broke motion smoothing for me (not sure why exactly, dunno if i'll get the time to debug it). |
while what you're talking is true, this issue was about an actual bug preventing the install, despite all the prerequisite correctly installed, and that was fixed along with the big steamvr linux patch around 1.27 (i guess, dont know exact version fixed) |
|
Closing per the last several comments. |
Describe the bug
SteamVR just don't even want so start for me, I click on start and after a few seconds it just "crash" (the button get back to play again)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
To run
System Information (please complete the following information):
additional context
As far I know I have all needed libs as i can run games (natives or proton one) without any problems.
the vrclient_vrstartup log file only have
No other log file exists (for some reason the vrmonitor logfile actually got created and have only one entry out of my idk 20+ tries):
Also trying to launch steamvr directly with
~/.local/share/Steam/steamapps/common/SteamVR/bin/vrstartup.shI learned that it create dump, here my /tmp/dumps folder (nb: it doesn't have dumps of all my tries as i restarted my pc meantime)dumps.tar.gz
The text was updated successfully, but these errors were encountered: