[BUG] SteamVR Dashboard doesn't work
After restarting my PC a few more times and upgrading/downgrading in and out of SteamVR Beta, I seem to have gotten games working again.
The SteamVR overlay/dashboard still doesn't seem to open.
On my system, the dashboard opens, but the lower area (where it normally gives you the option to exit the game or enter the settings) is filled with artifacts to the point where I can't reasonably be expected to interact with it. This is with the SteamVR beta. I do not have the same issue when I am not using the beta. Seems like a clear regression to me.
System information: https://pastebin.com/Q8ch0JER
Hello @Lyle-Tafoya, you're most likely looking for #253 instead of this issue report.
I think you are correct. My apologies.
I've got the same issue - just to be sure: you also get nothing at all, not even the overlay like in https://github.com/ValveSoftware/SteamVR-for-Linux/issues/244 ?
When i'm in SteamVR Home and press the system button, the sound fades out and in again, as if it is attempting to open the dashboard, but fails.
I've already tried completely uninstalling steamVR according to https://steamcommunity.com/app/250820/discussions/2/1640917625015598552/ but the issue persists.
System Information (please complete the following information):
- Distribution: Manjaro KDE
- SteamVR version: 1.8.6
- Steam client version: 1569883362 from Sep 30
- Opted into Steam client beta?: yes
- Graphics driver version: Mesa 19.3.0-devel (git-3c966fd688) (LLVM 10.0.0) on 5700XT
- Gist for SteamVR System Information: https://gist.github.com/Termuellinator/be41f6abf92575447f03f01b48c4df0b
I've noticed that I don't even get an IPD adjustment overlay anymore.
This happens to me, too. No dashboard and no IPD adjustment overlay. Games work and start fine though (except for #246 sometimes, but that's probably not related). I have to note that this doesn't happen every time I start SteamVR but also only sometimes.
System Information (please complete the following information):
- Distribution: [Arch/Manjaro/Ubuntu/etc.] Manjaro KDE
- SteamVR version: [E.g. 1.7.2] 1.8.6
- Steam client version: [build number or date] 1569883362
- Opted into Steam client beta?: [Yes/No] Yes
- Graphics driver version: Mesa 19.3.0-devel (git-34be977f80) (LLVM 10.0.0)
- Gist for SteamVR System Information: https://gist.github.com/Zamundaaa/37d5780b568d62b045d9058278a493ab
I can confirm that the IPD overlay is missing for me, too.
On my first launch of 1.8.7, everything worked except I couldn't use the desktop overlay to control anything.
After a few hours, Steam crashed with SDL_GetWMInfo failed (or something similar) and now the overlay isn't working.
Can confirm. For the most partt least. The desktop overlay was there but the pointer just went straight through, not interacting. As Blade&Sorcery didn't stop loading and didn't display anything (#246 I guess) I exited SteamVR. The exit menu in the dashboard was smaller than I'm used to and more importantly didn't react at all, no hover effect and nothing. Exiting it on the desktop I see a unresponsive Steam, not even the window could be grabbed anymore. Minimizing that the same message "SDL_GetWindowWMInfo failed" was there. Pressing OK exited Steam.
After starting Steam and SteamVR the dashboard worked again though. That is, until the same error window popped up again and Steam crashed...
IPD slider is there again. The "next up" game notification works, too.
Now the dashboard stopped SteamVR from exiting. The process stays alive even after killing vrmonitor (the only other process still running) and constantly uses 12-13% of the CPU.
The problem "SDL_ GetWindowWMInfo failed" also occurs in 1.8.9.
With 1.8.9, the overlay worked a few times, but then stopped working.
KB/M input still doesn't work on the Desktop view. It seemed to stop around the time that the "Prefer real KB/M input" change was made,
I am using the Steam Client Beta.
The IPD adjustment seems to work still. Steam notifications still pop in, but just have the notification box and Steam icon, no text.
Interestingly, last night the Steam notifications started working properly, but the dashboard overlay still wouldn't open.
Steam (and the dashboard) is still crashing with 1.8.10 and the latest Steam beta. No SDL_GetWindowWMInfo failed anymore though.
With 1.8.11 the dashboard worked great, apparently until I had the desktop view open for too long. Then the desktop view became invisible and the Steam overlay unresponsive. Settings still worked. After hiding the dashboard and showing it again all the other UI elements except for Steam and the settings were invisible, too. I could still interact with them, at least for a while.
Then performance of the compositor got really bad until when moving the head it felt like 3fps. SteamVR didn't crash but looking at the desktop the message SDL_GetWindowWMInfo had appeared again; Steam crashed.
Now something in the dashboard crashed again, but it didn't crash Steam at first. More specifically, the desktop view was empty and the display settings were not working again. Every time I exit the display settings it shows the controller bindings page for a split second, and when it now crashed it showed the bindings page until I got back. It wasn't responsive though (the back button of the actual display settings worked).
Because it somehow didn't recognize my left controller I then shut down SteamVR, and that seemed to trigger the SDL_GetWindowWMInfo message combined with the Steam crash again.
directly after starting SteamVR again: https://gist.github.com/Zamundaaa/6c5091e0be124c57913d78564c61425e
I've had several interesting combinations happen over the last few days over multiple versions of SteamVR:
Dashboard doesn't work, notification popups do
No overlays at all (no popups, no dashboard)
Dashboard works, Steam notification popups appear but are empty
Everything works properly
Dashboard doesn't work, notification popups appear but are empty
Since the IPD interface update, the IPD overlay seems to consistently work every time I've tried it (I generally don't mess with my IPD much once set)
I haven't really found a rhyme or reason for it working or not working. Maybe a race condition? Sometimes it works when I start SteamVR, sometimes it doesn't. Generally, it seems to not work more than work. The first 1-2 launches after SteamVR updates generally seem to work.
Wanted to confirm that this is still an issue on 1.8.13.
@Goofybud16 Do you still have STEAMVR_WEBHELPER=0 %command% as your launch options?
The dashboard in 1.8 is rendered by vrwebhelper, so without it you won't be able to see the dashboard.
Would that also introduce new dependencies so that the missing dashboard could be cause by missing deps?
All the required dependencies for vrwebhelper are bundled as part of SteamVR or as part of the Steam runtime. Or at least that is the intended way for it to operate. If you find it behaving differently that would be a bug.
I removed STEAMVR_WEBHELPER=0 at some point previously. It has not been there for several versions at least.
The dashboard does work sometimes, just not all the time. It's inconsistent; I've yet to figure out how to make it work or break. Sometimes I can launch it 3 times in a row and the Dashboard will work, but the notifications may or may not work properly. Sometimes I launch it, no dashboard, relaunch, and there's a dashboard.
I've also noticed I never get the SDL WMInfo error that crashes Steam if the dashboard isn't working. It usually seems to pop-up when interacting with the Steam (big picture VR) tab in the dashboard, and then the big-picture view locks up. Steam will usually keep going for 5-15 minutes afterwards [if I don't click "OK", which immediately exits Steam), but then eventually does crash (which takes out some other games-- Like VRChat).
It seems the WMInfo error is related to using the Big Picture overlay after the first time opening/closing the overlay. Possibly related to opening/closing on a different tab (eg Desktop) and switching back after opening/closing. That seems to trigger it almost immediately.
If I just leave the Desktop view open all the time, it doesn't seem to pop up very often.
The overlay worked perfectly every time for me on 1.8.14. The Steam notifications worked (although sometimes the images would be slow to load in for profile pictures, but they worked). The only issues was the WMInfo error.
It hasn't worked at all for me on 1.8.15 or 1.8.16. Not just inconsistently like it was, but I just haven't been able to get the overlay open at all.
KB/M support was still broken in 1.8.14 as well. Within the first half-second of opening it, I could sometimes get the mouse input to work, and sometimes scrolling would work too. After that, the KB/M input would just stop.
Well, I just got it working on 1.8.16. Not sure what changed, if anything, but it started working.
Also managed to get the KB/M input on the Desktop view working today as well. Steam updated at one point, so it's possibly related to that.
The dashobard opens just fine every time for me, too. The WMInfo error pops up practically immediately though, and the desktop view seems to only be interactive on the lower half or something (can't really see it properly because of #262 though)
The dashboard still seems to be inconsistent for me. Sometimes it works, sometimes it doesn't.
Something to note is that I always get the "Setup Failed" message, because getcap and setcap aren't on the PATH of a standard user. [Fairly new Debian Testing system] Since I manually ran the appropriate setcap command, I've just changed the function in the shell script to return 0 before the actual code (since I just click OK every time every time). I'll see if that results in the dashboard working more consistently.
With 1.8.16 and the latest Steam, the desktop overlay seems to work fine on my system. The area for the mouse input appears to be wonky (doesn't align with the actual window). In case it matters, this is my screen layout [3x1080p60]:
For me it still doesn't work at all, same for the IPD-Adjustment HUD.
When in SteamVR-Home, the Audio briefly pauses, thats it :/
As it is working for others now - has somebody got any advice on how to "reset" SteamVR besides what i tried (as posted in https://github.com/ValveSoftware/SteamVR-for-Linux/issues/255#issuecomment-537451128 )?
With the latest SteamVR (1.8.18 Beta) I've found the following to work:
- Start SteamVR from Steam with the "Launch" button
- Use the headset system button to check for the overlay
- If it doesn't open, exit SteamVR and restart from 1.
I don't know if it matters, but SteamVR is loading off of a 5400RPM 10TB HDD (shucked from an EasyStore). Could it be a timing issue? I've found the dashboard usually doesn't work on the first load, but if I immediately restart SteamVR, it usually loads on the second try. Could it be things getting cached in RAM causing faster loading fixing the timing/race condition?
@Goofybud16 - I'm curious as to that too. I'm running off a surplus 4TB 5400RPM drive from Ebay.
Currently running Ubuntu Mate 19.10 and can't say the upgrade from 19.04 changed much of anything, though I was hoping it would.
with 1.9.3, i still get no dashboard/IPD at all :/
Steam and all is on a samsung 960 evo plus, so shouldn't be a timeout issue.
As others get the dashboard (at least sometimes), i suppose there is something wrong on my side.
I already tried reinstalling steam completeley (only kept /steamapps/common and /compatdata) without success - any more hints to what i can try?
It sometimes works for me, sometimes it doesn't. At least from what I've tried it seems like it always works the second time I start SteamVR.
I don't really think that there's something you can do. It's something the devs should finally fix...
@Termuellinator Sometimes switching between beta/normal and letting SteamVR reinitialize, then trying it works. But hasn't been for the latest update...
haven't tried it yet but changelog from most recent update from today looks promising:
Linux:
Fixed a vrwebhelper crash that could make the dashboard disappear.
Fixed the pairing UI window content not showing up the first time it was opened.
Fixed a few behaviour quirks in vrwebhelper's desktop windows.
Started SteamVR a few times now and the dashboard always showed. Seems like fixed :+1:
Okay, it always seems to work at start but after playing a round of Sairento just now it just didn't show up anymore. The process didn't crash and showed nothing in the log indicating anything went wrong though...
Didn't work at first launch of 1.9.4 for me.
Did work on the second.
The SDL GetWMInfo error still appears every now and then, usually when I switch back to the Steam tab in the overlay. Keeping it in other tabs (settings, Desktop) all the time seems to 'fix' the issue.
still an issue here. It is especially annoying when you want to exit a game without an exit option (so most of all games) or if you want to test a new game in VR.
The GetWMInfo error happens rather often for me with 1.9.7.
Still having it sometimes not appear on 1.9.7.
The "Start SteamVR, check for the dashboard, restart if it isn't there" still works, and it's always there on the second try.
Switching between Desktop and Steam views in the overlay seems to cause the GetWMInfo error. If I accidentally hit the system button when a notification pops up, it will usually pop back to the Steam tab, and that is usually the cause of my crashes (I usually keep it on Desktop to avoid crashing and because I use the desktop overlay).
Also noticed the new keyboard seems to be totally broken. If I'm typing "hello" it types like this:
hhehellhello
Although I've heard similar reports from friends on Windows so that may not be a Linux-specific issue, and is likely worthy of it's own report if it is.
Switching between Desktop and Steam views in the overlay seems to cause the GetWMInfo error
I it consistently every time switching from the Desktop to the Steam view.
The Desktop view stopped being responsive a few times for me now, without switching between tabs or triggering Steam to crash.
just noticed that the "Need Retest" label was removed 14 days ago.
what does this mean exactly? Is the bug officially reproducible now?
with the current steamvr beta 1.9.13 nothing has changed (maybe obvious when no linux related fix is mentioned in the changelog(?)).
would be great if this will be fixed soon, as currently vr on linux is absolutely no joy with it.
trial and error if dashboard is available -> if yes: yay, chances are good that I can play a game; if not -> fear that you can at least start one game, knowing that you can't exit most of them anyway. very likely you can't start another one because you have exit the first one forcefully on the desktop triggering SDL GetWMInfo on the next try and so on. especially annoying when you have bought an index recently after 1 year htc vive and barely can't use it.
Hello @frostworx, the "Need Retest" label is used to make sure issues that may be fixed or outdated don't get forgotten and left open. Since you gave feedback that there's still an issue to evaluate, it was removed.
thank you for the explanation and for your continous support in general, kisak!
heh, that is timing.
SteamVR 1.9 stable fixes this bug!:
https://steamcommunity.com/games/250820/announcements/detail/3150762393108758897
haven't tried it yet.
edit: tried it, no dashboard. the description probably was a changelog entry from a previous beta.
AFAIK a stable update is always just the latest beta update, there will never be changes only on a stable update.
1.9.15 breaks the dashboard entirely for me
It worked on the linux_temp 1.8.21 branch first try.
linux_temp branch would have been nice, but it didn't help here.
I wiped out my steam vr settings, setup my index from scratch. after a restart afterwards dashboard was available. started "To the Top" after nothing happened I opened the dashboard and I had to accept a licence agreement (don't ask - haven't read it). after accepting steam crashed again with the beloved "SDL_GetWMInfo" requester.
btw interesting that different libSDL2-2.0.so.0 versions/builds are shipped with SteamVR
tools/steamvr_environments/game/bin/linuxsteamrt64/libSDL2-2.0.so.0
is different to
bin/linux64/libSDL2-2.0.so.0 and bin/vrwebhelper/linux64/libSDL2-2.0.so.0
reverting back to steamvr beta and mostly playing pancake games until this is gets fixed
happy holidays all together!
linux_temp branch didn't fix the issue for me either.
The dashboard doesn't just not show with 1.9.16 but the IPD slider also doesn't show. It's likely that overlays in general are broken again.
If I restart SteamVR a few times, I can get the IPD and Steam notification overlays to work.
XRDesktop also works.
So Overlays aren't broken in general, it's specifically the Dashboard overlay that isn't working.
Possibly whatever condition it would sometimes hit before is now always being hit, causing it to never show up.
Interesting. So it's both, overlays pretty much broken and the dashboard completely. Cool.
Until just now, I've had SteamVR Home disabled. Without Home running, nothing would happen if I pressed the system button. However, since I have a new graphics card and Home performs better (from RX 580 to 5700 XT) I've re-enabled Home.
So now, when I'm in Home and press the system button, the overlay appears... for like one frame, and then freezes, and then the displays go black and I have to restart SteamVR.
EDIT: Just now I was able to get the overlay working within DeoVR... But then when I exited the overlay, the visuals of DeoVR were horribly corrupted in one eye. And then when I tried it again, the other side got messed up too.
But now the overlay is working fine otherwise. (In which there seems to be texture issues, the floor is blurry and vibrating and several graphics within the Home Settings is low res and blurry. I'll probably post a separate issue for that though.)
I can get the IPD and Steam notification overlays to work.
So Overlays aren't broken in general, it's specifically the Dashboard overlay that isn't working.
Agreed, also experiencing the same "Dashboard" issue though the "IPD" adjustment display appears to work as expected.
System Information:
- Distribution: Ubuntu 18.04 LTS
- SteamVR version: 1.9.16
- Steam client version: Dec 20 2019, at 23:41:30
- Opted into Steam client beta?: Yes
- Graphics driver version: NVIDIA 440.44
- Link to Gist for SteamVR System Information
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.
I was also missing the Dashboard, lowering my refresh rate from 120Hz to 90Hz brought it back.
no change here, not with 90Hz, not with SteamVR 1.10.1. The IPD slider now sometimes works for me, too.
confirming still an isue with 1.10.1. sure, it doesn't help to rant, but until this bug is not fixed it is really extremely annoying to use steamvr on linux. searching and playing only games with a builtin exit in order to play another one afterwards is not too convenient. Manually quitting/killing a game on the desktop isn't as well. Also license agreements waiting for you forever because you can't see them is not the fun I expect for my money. Wouldn't be a major issue if at least linux_temp 1.8.21 would be in a proper usable state, but it isn't as well.
won't help anything but:
Steam/SteamVR beta
Distro:Arch Linux
Kernel:5.4.10-arch1-1
RAM:16 GB
GPU Driver:NVIDIA 440.44
GPU:NVIDIA GeForce RTX 2080
CPU:Intel Core i7-8700K @ 3.70GHz
https://steamcommunity.com/games/250820/announcements/detail/1699479856183140332
Linux:
Fixed blank settings page.
Fixed a case where the dashboard would disappear.
Fixed a vrwebhelper crash on shutdown.
On first start of 1.10.2 no overlay at all would show up and I created the system overlay to look at some logs then like 10-20 seconds later it experienced some error and just closed after 3 seconds.
System Report from the start after: https://gist.github.com/Zamundaaa/c1815a8b681793467cdf35b1f9a45b98
on that next start there still was no overlays, including the dashboard.
Edit: On every start of SteamVR it produces two coredumps with this message in the journald log
Edit edit: opted into Manjaro unstable, updated, and now the dashboard appears as wanted. I sometimes get the GetWindowWMInfo error when switching around between the tabs and the desktop view doesn't really work but the rest does.
thanks for deeper testing, Zamundaaa! gave it a quick try and can confirm that it is still totally broken...
looks like mapping a generic oneliner killing (proton-)game to a amazon dash button and putting it into the pocket for playing vr is currently the most convenient way to exit a vr game \o/
Testing done on Pop!_OS 19.10
Changed from linux_temp (where the dash worked for me) to regular beta (where prior it didn't work). Now it seems to work as intended, at least the bringing up and dismissal-part of the dashboard, even on 120Hz which seems like what borked it initially for me.
Changing volume/muting in the dash doesn't work.
I was able to quit out VR-apps using the dash, but not able to turn off steamvr from the dash.
Settings are missing from the Dash (probably intentionally), but are accessible and works from the desktop steamvr-app.
Shutdown of SteamVR from the desktop also seemed faster and cleaner, no leftover steamvr-processes.
Slackware64-current with KDE Plasma.
Dashboard works on beta 1.10.2. It didn't on 1.10.1 yesterday, so it looks fixed for me. Previously the dashboard only worked on the linux_temp branch.
Settings page works, both on the desktop and on the dashboard. In the dashboard it's sometimes slow to load.
The little pop up menu you get from holding the system button for a few seconds doesn't work, but with the dashboard working it's not important.
Quitting SteamVR from the dashboard still doesn't work, but you never want to quit SteamVR and continue wearing the powered off headset, so that's not important either.
now the dashboard appears as wanted
Agreed, the initial issue is now resolved though the general functionality is still limited as others have mentioned.
System Information:
- Distribution: Ubuntu 18.04 LTS
- SteamVR version: 1.10.3
- Steam client version: Jan 18 2020, at 03:34:03
- Opted into Steam client beta?: Yes
- Graphics driver version: NVIDIA 440.48
- Link to Gist for SteamVR System Information
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.
With 1.10.3, I still have issues with the dashboard not starting reliably every time.
I haven't noticed any change in the behaviour of the dashboard since this issue was opened.
Running 1.10.4 and still no dashboard. It just feels as if the buttons did nothing.
SteamVR System Info: https://gist.github.com/jug007/b935122c96a2800375a3ff029cbee186
"surprisingly" still an issue with 1.10.7...
my dash button workaround mentioned above works fine btw.
maybe useful for someone else until this gets fixed:
basic bash command to stop the currently running proton game is:
PFX=$(lsof | grep compatdata | grep 'pfx$' | awk '{print $NF}')
WINEPREFIX=$PFX wineserver -k
- lsof is a bit heavy for this, but works
- grep 'pfx$' find the single line ending with pfx - and awk cuts your WINEPREFIX from it
(of course multiple hits - f.e. multiple proton instances ujnning will fail ¯_(ツ)_/¯) - "shutting down windows" for that WINEPREFIX "gracefully" stops the running game
- of course this could be a oneliner as well
- also mapped it to a hotkey via xbindkeys
- (for the dashbutton it needed some extra voodoo)
The dashboard has randomly started working for me again and seems to reliably start every time now.
i am also having this bug. the error is "SDL_GetWindowWMInfo failed"
this error also crashes steam. once i press ok on the error window.
steam vr linux_temp 1.8.21
system information
https://gist.github.com/mathew2214/3b3b3ecc6a1fb71806b7d09a8e86a95a
At time of writing: broken in release version, working in beta.
Edit: adding version nr of SteamVR beta that works for me: 1.10.14.
in addition to fixing the dashboard it also fixed the showing of the settings as this was stuck on Loading... before.
It does seldomly also not work in the beta. The desktop overlay is completely non-interactive but I think I haven't got the WindowWMInfo with the new dashboard
with 1.10.17 the issue still occurs, but it feels like it happens less often than before since the last minor version bumps. maybe it is just me because I haven't played VR as much as before and therefore was simply less angry about it.
Even with the new overlay, it doesn't reliably start.
I've also noticed that the keyboard sometimes won't appear when the overlay does work.
And I haven't been seeing any Steam notifications at all in recent versions.
With 1.10.30, I've noticed that the overlay, and the keyboard, do not reliably start.
Sometimes the overlay will work, but the keyboard will not be able to be opened, preventing any text from being entered anywhere in the overlay.
not sure how useful those bumps are, but still an issue with 1.11.9
edit: meant latest beta, not latest "stable"
still on 1.11.9: I recently moved the SteamVR installation from a (hdd) library dir to my (ssd) default library dir (~/.steam/steam/steamapps). It might be a coincidence, but maybe not and it is simply timing related: since then I haven't had even one single failing dashboard - it always worked ootb. haven't played that much but it was 10/10 times for sure (before first SteamVR launch had a very high fail rate). might help. good luck! (nvidia-440.82 currently, so they changed as well)
If it's any help, I have SteamVR installed on my default SteamVR library which lives on my 10TB internal drive-- which is a shucked WD EasyStore from BestBuy.
I believe it's a 5400RPM drive with either 128 or 256MB cache.
Does SteamVR work properly when in a non-default library location? I seem to recall seeing some bugs around that, but if I remember, I'll try to move it to my second library that lives on my NVMe drive and see if that helps.
Still, seems that it shouldn't break it trying to run it off an SSD.
I thought about it, and tried it, and moved SteamVR to my SSD.
It's a 1TB Samsung 970 Evo Plus, so it should be plenty fast.
I still have issues with the dashboard not starting, and even when it does start, the IPD overlay/keyboard not starting properly.
played a bit more since last comment and can confirm that it is not completely fixed with the ssd. so maybe it really was a coincidence. anyway it starts more reliable since some time for me
The overlay stopped working for me again. In Home or in a game, overlay just won't come up, ever.
I find that the overlay still works.
I quit using the overlay, though, because I mostly used it for the desktop view functionality, and found that it was pretty regularly crashing Steam, SteamVR, and/or the game I was playing when I used it.
Not to mention that some days it took me 15 minutes of restarting SteamVR to even get the desktop overlay + keyboard to both actually appear, and then usually restarting Steam 2-3 times because when the overlay finally was starting to work, Steam had bugged out and wouldn't actually send the desktop feed. If I didn't restart it, it would usually crash.
There seems to be a lot of race conditions happening surrounding the overlay and desktop view starting up and shutting down-- I find Steam eating 100% of one CPU core after closing SteamVR pretty often, but when the overlay doesn't start, or I don't use desktop view, it doesn't seem to do it.
I tried it again recently and the overlay worked that time. Forgot to come back here and mention it...
But just now I tried again. Twice, SteamVR made my PC freeze up and the display go blank. Trying a third time, will edit...
EDIT: Forgot to mention, the first two times I got a freeze was when I had forgotten to activate my base stations (I have one on a switch). The third time, I didn't get a freeze, but the game did seem to fail to launch... I think? (I didn't check the task manager, but I didn't see any sign it was trying to start.) But it never sent me back to Home, I just stayed in the... OpenVR environment, whatever it's called. I was able to bring up the dashboard, though it wasn't very responsive and was missing some button graphics at one point.
Eventually, the game did launch, but then it took a minute or two before it showed "loading...". Once I finally got into the game, it seemed to run normally.
I was running System Monitor by that point, and shortly after I exited VR I checked the CPU history graph. Was surprised to see cores weren't usually going above 50%? Is that normal?
For me at the moment the overlay fails to open the first time I run SteamVR, but always opens fine if I close and restart it once.
@yaomtc I used to get the blank screen crashes, but haven't had one since I started using the mainline kernel (https://aur.archlinux.org/packages/linux-mainline/)
@duckbytes Hopefully this reduces the frequency of crashes, but it's not looking promising as I've already had two since installing mainline - one after starting SteamVR for the first time since the first mainline boot, and the second while I was using Whirligig. Oof.
@yaomtc Are you using kernel 5.6+ with amdgpu?
I am currently using linux-mainline 5.7rc7-1 with vulkan-radeon 20.0.7-3 and xf86-video-amdgpu.
Then this might be the error you are getting: https://bugzilla.kernel.org/show_bug.cgi?id=206987
Oh, @farmboy0 I see you there... You even have the exact same GPU I have. Yeah, that seems likely. Thanks!
Some people were reporting similar issues due to a radv issue (#278) that could be resolved by unset mesa_glthread
I found that, in my case, it does not fix the issue to launch steam as
$ unset mesa_glthread
$ steam
And then SteamVR.
EDIT: Apologies for closing and re-opening, managed to click the wrong button on accident.
@Goofybud16
Some people were reporting similar issues due to a radv issue (#278) that could be resolved by
unset mesa_glthread
#278 differs from this issue: mesa_glthread=true with mesa/RADV causes consistent vrwebhelper crashes with SIGABRT. Randomly missing dashboard without any crashes and without any error messages is a different bug IMO.
I found that, in my case, it does not fix the issue to launch steam as ...
mesa_glthread is disabled by default. It is enabled only for selected applications by the default drirc (usually /usr/share/drirc.d/00-mesa-defaults.conf), may be enabled manually using custom drirc (/etc/drirc or $HOME/.drirc), or may be enabled by setting the mesa_glthread environment variable to true.
So, if you do not have mesa_glthread=true in the environment when launching SteamVR, unsetting it should not have any effect.
And I also confirm this issue: dashboard sometimes doesn't work. It is 50/50 when launching SteamVR: dashboard either will work after launch, or it will not show up at all. Completely random.
System Information (please complete the following information):
- Distribution: Fedora 32 x86_64
- SteamVR version: Beta 1.12.5
- Steam client version: Built Jun 1 2020, at 20:22:35 / package versions: 1591052255
- Opted into Steam client beta?: No
- Graphics driver version: Mesa 20.1.0 (LLVM 10.0.0), with
RADV_PERFTEST=aco - Gist for SteamVR System Information: https://gist.github.com/im-0/da5d2518b1c510e323eee4abec1687a2
- GPU: AMD Radeon VII
Seems I'm having the same issue.
System Information (please complete the following information):
- Distribution: Linux Mint
- SteamVR version: Both 1.12.5 and Beta 1.12.5
- Steam client version: Jun 1 2020, at 20:22:35
- Opted into Steam client beta?: No
- Graphics driver version: Nvidia 440.82
- Gist for SteamVR System Information: https://gist.github.com/TiagoTiago/25b217bfe4a158cab3ffcdd90a11bee8
Here's what I wrote in the SteamVR forum the other day about my situation:
When I boot up steam VR, very frequently I can't access the dashboard, it will not show when SteamVR finishes booting up, and pressing the menu button on the controllers will have no effect.
Possibly related issues I'm having:
Settings window will frequently not load fully, I can only see the Startup/Shutdown tab
Individual app video settings will not load interface after selecting an app, seems to fail more often if I do anything other than open it before doing anything else in VR
Can't launch any apps/games from the dashboard; an empty splash screen sometimes shows but nothing load; can only launch from the desktop interface
Can only launch SteamVR from the Launch button on the library or the Start SteamVR command on the View menu; the "VR" rectangle button on the top-right corner of the window does nothing
Occasionally the Desktop View will stop working, showing just empty space when activated, and remains so until SteamVR is restarted.
A while ago, the dashboard issue would only happen on the first launch after loading Steam, but it would work just fine on subsequent launches; but now it fails to work more often than not. Same thing with the Settings window issue.
The launching from the dashboard issue is a little older.
The Desktop View failure is also older but got more frequent.
The "VR" button never worked.
Nothing changes between regular and beta SteamVR.
I've noticed that more recently, the overlay seems to be a bit more stable, but still sometimes doesn't start up.
I've also noticed that some time recently, the Desktop view quit working entirely.
I'm back on the Steam client release branch, not the Beta branch, if that matters.
It seems to show the zoom button below, which it didn't use to do on Linux, except when it was broken and Steam needed a restart.
Latest 1.13.9 non-Beta.
Still having this issue. I can't seem to find any sort of error when it doesn't launch. Pretty annoying since it makes it harder to switch games and exit VR and stuff.
- Distribution: Arch
- SteamVR version: Beta 1.14.2
- Steam client version: Jul 23 2020 at 11:01:27
- Opted into Steam client beta?: Yes
- Graphics driver version: NVIDIA 450.57
- Gist for SteamVR System Information: https://gist.github.com/YungDaVinci/76458038cac7c92902d7a1b423c355f0
Just wanted to note that with 1.14.6, the Desktop Overlay seems to be working again.
Didn't have a keyboard, but at least mouse input and video was working.
Update: It worked once, but decided to not work after that night. Seems that it's very inconsistent, and I'm not sure why. It's not totally and completely broken, but I'm guessing there is a race condition or something that prevents it from working properly. Possibly only works on the first launch of SteamVR? Or freshly after a reboot?
Currently working here with Mesa 20.2.0-rc4.– started SteamVR a few times, present and functional each time. The desktop display is working too (though the mouse button mapping could use some work, and it's decidedly unfriendly towards focus-follows-mouse; but those things aren't relevant here).
I've noticed it's a lot more consistent lately. I think it also helped that I switched to using Steam Runtime rather than Native. The VR View is broken for me with Steam Runtime though, and works fine in Native.
Steam Linux Runtime
For me, that causes it to immediately stop working. Running with konsole --hold -e %command% I get:
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
pressure-vessel-wrap: Cannot find ldconfig in PATH
pressure-vessel-locale-gen: No locales need to be generated
+++ dirname /opt/steamapps/steamapps/common/SteamVR/bin/vrstartup.sh
++ cd /opt/steamapps/steamapps/common/SteamVR/bin/
++ pwd
+ VRBINDIR=/opt/steamapps/steamapps/common/SteamVR/bin
+ [[ -n '' ]]
+ exec /opt/steamapps/steamapps/common/SteamVR/bin/vrenv.sh /opt/steamapps/steamapps/common/SteamVR/bin/vrstartup.sh
++ readlink -f /opt/steamapps/steamapps/common/SteamVR/bin/vrenv.sh
+ export STEAMVR_VRENV=/opt/steamapps/steamapps/common/SteamVR/bin/vrenv.sh
+ STEAMVR_VRENV=/opt/steamapps/steamapps/common/SteamVR/bin/vrenv.sh
+++ dirname /opt/steamapps/steamapps/common/SteamVR/bin/vrenv.sh
++ cd /opt/steamapps/steamapps/common/SteamVR/bin/..
++ pwd
+ export STEAMVR_TOOLSDIR=/opt/steamapps/steamapps/common/SteamVR
+ STEAMVR_TOOLSDIR=/opt/steamapps/steamapps/common/SteamVR
++ cd /opt/steamapps/steamapps/common/SteamVR/../runtime
/opt/steamapps/steamapps/common/SteamVR/bin/vrenv.sh: line 5: cd: /opt/steamapps/steamapps/common/SteamVR/../runtime: No such file or directory
++ pwd
+ RUNTIMEDIR=/opt/steamapps/steamapps/common/SteamVR
++ cd /opt/steamapps/steamapps/common/SteamVR/../sdk
/opt/steamapps/steamapps/common/SteamVR/bin/vrenv.sh: line 6: cd: /opt/steamapps/steamapps/common/SteamVR/../sdk: No such file or directory
++ pwd
+ SDKDIR=/opt/steamapps/steamapps/common/SteamVR
+ case $(uname) in
++ uname
+ '[' -z '' ']'
+ exec /home/stephen/.steam/root/ubuntu12_32/steam-runtime/run.sh /opt/steamapps/steamapps/common/SteamVR/bin/vrenv.sh /opt/steamapps/steamapps/common/SteamVR/bin/vrstartup.sh
Definitely do have ldconfig, although am on Debian, and it appears to be in /usr/sbin/
Are we talking about the same runtime? When I say native I'm talking about launching steam with steam-native or STEAM_RUNTIME=0 steam, and runtime as just running steam, not the Steam Linux Runtime under Steam Play options.
I've found that if my computer isn't connected to the Internet, or if I switch Steam to offline mode, the odds of the dashboard showing up increases significantly; still not 100% reliable though. And it seems to have a similar beneficial, but still not 100% working, effect on issue #328 , suggesting they may be related.
The repro is not very reliable, so you might need to restart SteamVR with and without Internet several times to gather more accurate statistics.
I've noticed that the dashboard is way more likely to pop up if I have Big Picture running in the background before launching SteamVR.
I've noticed with the later 1.15.x series, the desktop and dashboard seems to show up reliably. Had good luck this whole week, worked every time.
The latest Beta 1.16.1, it started showing "No Desktops Found". Reverted off of the beta back to 1.15.19, and the desktop is back again.
The keyboard is finnicky and sometimes won't show up, but the desktop does appear and mouse control works.
Can confirm, the dashboard wasn't working on the beta. I switched back to 1.15.9 and it also worked.
yaomc-steam-system-info.txt
SteamVR-2021-01-20-PM_11_58_20.txt
Still was having no luck on Arch. However, I think I found a workaround that has seemed to work almost every time.
I found out that the crash seemed to be happening in vrwebhelper. I think it's in part due to the Qt plugins that SteamVR ships and in part due to the proper libraries not being loaded when VR starts up. What I changed:
In [SteamVR install location]/bin/vrwebhelper/linux64/vrwebhelper.sh:
- Changed whatever the default
LD_LIBRARY_PATHline was to
export LD_LIBRARY_PATH="$HOME/.steam/steam/steamapps/common/SteamVR/bin/linux64:$HOME/.steam/steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64:${STEAM_RUNTIME_HEAVY}${LD_LIBRARY_PATH+:$LD_LIBRARY_PATH}"
In [SteamVR]/bin/linux64/qt/:
- Rename
pluginstoplugins.old - create a symlink to my system's Qt plugins (
ln -s /usr/lib/qt/plugins plugins)
In /usr/bin/steam-native:
- Changed the default
LD_LIBRARY_PATHline to
export LD_LIBRARY_PATH="/usr/lib/steam:/usr/lib32/steam:$HOME/.steam/steam/steamapps/common/SteamVR/bin/linux64:$HOME/.steam/steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64:${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
(this change also allowed me to start VR by pressing my system button again)
I think that was all I did. Since doing it the dashboard consistently pops up. Also if you don't want to use steam-native you can probably just make the same changes to steam.
@Supreeeme I'll try it out in the weekend. If it works this is a huge find, both in regards to the dash and starting steamvr with your controllers (if I read it correctly).
Has anyone else had an issue with the Desktop Overlay causing intermittent GPU lockups?
I'm on a 3900X + 5700XT [Mesa 20.3.4].
Seems that every now and then, the opening the desktop overlay will either
- Crash [and take Steam with it, sometimes the game as well due to Steam crashing]
- Lock up my GPU, and cause the driver to reset it [and thus I have to reboot my system.] This is usually accompanied by the screens flashing after a minute or so, followed by the slightly corrupted visuals and things being generally broken.
@Supreeeme I tried out your solution and it seems to work, at least in regards to the dash and the powering on of the headset with the controllers.
The solution, though, breaks SteamVR for me as it doesn't spawn the SteamVR window, making it hard to shut off the HMD and controllers. Basically I can start up any game and play just fine (with dashboard and wake on controller working just fine), but shutting down the headset from within VR doesn't work, and since there's no SteamVR-window I have to kill the processes in task-manager, roll back the solution, turn steamvr on and off again to shut off the HMD and controllers.
Nice find though. My guess is that when you click "Exit VR" from within VR, all it does is kill the SteamVR-window on the desktop. Since it doesn't spawn with your solution (neither through wake on controllers or manually starting SteamVR), clicking "Exit VR" from within VR doesn't do anything. In other words, all we need now is for the SteamVR-window to spawn when starting SteamVR and everything should be peachy. Or am I the only one experiencing the missing steamvr-window with this solution?
Hmm, I get the monitor popup just fine. After starting SteamVR, could you go to your SteamVR directory and run vrmonitor.sh? Should be in [SteamVR location]/bin/vrmonitor.sh.
@Supreeeme Full output of vrmonitor.sh after enabling the solutiom:
`++ readlink -f /home/myusername/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh
- export STEAMVR_VRENV=/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/vrenv.sh
- STEAMVR_VRENV=/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/vrenv.sh
+++ dirname /home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/vrenv.sh
++ cd /home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/..
++ pwd - export STEAMVR_TOOLSDIR=/home/myusername/.local/share/Steam/steamapps/common/SteamVR
- STEAMVR_TOOLSDIR=/home/myusername/.local/share/Steam/steamapps/common/SteamVR
++ cd /home/myusername/.local/share/Steam/steamapps/common/SteamVR/../runtime
/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh: line 18: cd: /home/myusername/.local/share/Steam/steamapps/common/SteamVR/../runtime: No such file or directory
++ pwd - RUNTIMEDIR=/home/myusername/.steam/steam/steamapps/common/SteamVR/bin
++ cd /home/myusername/.local/share/Steam/steamapps/common/SteamVR/../sdk
/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh: line 19: cd: /home/myusername/.local/share/Steam/steamapps/common/SteamVR/../sdk: No such file or directory
++ pwd - SDKDIR=/home/myusername/.steam/steam/steamapps/common/SteamVR/bin
- case $(uname) in
++ uname - '[' -z '' ']'
- exec /home/myusername/.steam/root/ubuntu12_32/steam-runtime/run.sh /home/myusername/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh vrmonitor.sh
++ readlink -f /home/myusername/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh - export STEAMVR_VRENV=/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/vrenv.sh
- STEAMVR_VRENV=/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/vrenv.sh
+++ dirname /home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/vrenv.sh
++ cd /home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/..
++ pwd - export STEAMVR_TOOLSDIR=/home/myusername/.local/share/Steam/steamapps/common/SteamVR
- STEAMVR_TOOLSDIR=/home/myusername/.local/share/Steam/steamapps/common/SteamVR
++ cd /home/myusername/.local/share/Steam/steamapps/common/SteamVR/../runtime
/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh: line 18: cd: /home/myusername/.local/share/Steam/steamapps/common/SteamVR/../runtime: No such file or directory
++ pwd - RUNTIMEDIR=/home/myusername/.steam/steam/steamapps/common/SteamVR/bin
++ cd /home/myusername/.local/share/Steam/steamapps/common/SteamVR/../sdk
/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh: line 19: cd: /home/myusername/.local/share/Steam/steamapps/common/SteamVR/../sdk: No such file or directory
++ pwd - SDKDIR=/home/myusername/.steam/steam/steamapps/common/SteamVR/bin
- case $(uname) in
++ uname - '[' -z /home/myusername/.steam/root/ubuntu12_32/steam-runtime ']'
- VRSTARTUP=/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrstartup
- QT_DIR=/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/qt
++ pwd - export LD_LIBRARY_PATH=/home/myusername/.steam/steam/steamapps/common/SteamVR/bin:/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/qt/lib:/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/linux64:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_32:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_64:/usr/lib32:/usr/lib/openmpi:/usr/lib:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib/i386-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib
- LD_LIBRARY_PATH=/home/myusername/.steam/steam/steamapps/common/SteamVR/bin:/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/qt/lib:/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/linux64:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_32:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_64:/usr/lib32:/usr/lib/openmpi:/usr/lib:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib/i386-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib
- export VRCOMPOSITOR_LD_LIBRARY_PATH=/home/myusername/.steam/steam/steamapps/common/SteamVR/bin:/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/qt/lib:/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/linux64:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_32:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_64:/usr/lib32:/usr/lib/openmpi:/usr/lib:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib/i386-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib
- VRCOMPOSITOR_LD_LIBRARY_PATH=/home/myusername/.steam/steam/steamapps/common/SteamVR/bin:/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/qt/lib:/home/myusername/.local/share/Steam/steamapps/common/SteamVR/bin/linux64:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_32:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_64:/usr/lib32:/usr/lib/openmpi:/usr/lib:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib/i386-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/lib:/home/myusername/.steam/root/ubuntu12_32/steam-runtime/usr/lib
- exec vrmonitor.sh
/home/myusername/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh: line 44: exec: vrmonitor.sh: not found`
Not sure if this will work, but could you try changing the last line in vrenv.sh, which is
exec "$@"
to:
exec $(realpath "$@")
exec $(realpath "$@")
That's… broken. Instead of this:
exec foo bar baz
you'll get something like this:
exec /path/to/here/foo /path/to/here/bar /path/to/here/baz
And that's ignoring the fact that the output of realpath isn't quoted.
You would need this instead:
CMD="$(realpath "$1")"
shift
exec "$(realpath "$CMD")" "$@"
Good find @Supreeeme. Thanks a lot!
Seems to work very fine for me so far.
I hacked a little script together which automates the whole process.
Works for me, but ymmv.
Pretty harmless, it also creates backups and tries to make sure it wasn't used before but use at your risk
Usage:
just start it (only applies the changes in SteamVR)
Optional parameters (use sudo)
if you want to expand the 'steam' script in your $PATH (usually /usr/bin/steam) append s as command line parameter
if you want to expand the 'steam-native' script in your $PATH (usually /usr/bin/steam-native) append sn as command line parameter
I also have the same issue as @ZarathustraDK after applying @Supreeeme’s workaround on Ubuntu 20.10 (fresh install from a week ago), AMD 5600X, Nvidia GTX 1060 (waiting for a new one…) with driver 460, Valve Index:
- vrmonitor does not show (is it the same as #209 ?)
- exit from within VR doesn’t do anything
- no desktops found (#426 ?)
- cannot stop SteamVR from Steam
- I also tried configuring SteamVR to close after 10 minutes, it seems to work but Steam still says SteamVR is running. If I try to close Steam before the 10 minutes it hangs and propose to force close it.
Compared to @Supreeeme’s workaround, since I am on Ubuntu, I tried to modify ~/.steam/debian-installation/steam.sh to change LD_LIBRARY_PATH, however as soon as I launched steam, it reverted the script to a version of 14/10/2021.
Exporting LD_LIBRARY_PATH before launching Steam does not seem to make a difference though.
Here is the output of ./vrmonitor.sh, with export QT_DEBUG_PLUGINS=1:
$ ./vrmonitor.sh
+++ dirname ./vrmonitor.sh
++ cd ./
++ pwd
+ VRBINDIR=/home/didier/.steam/steam/steamapps/common/SteamVR/bin
+ [[ -n '' ]]
+ exec /home/didier/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh ./vrmonitor.sh
++ readlink -f /home/didier/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh
+ export STEAMVR_VRENV=/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/vrenv.sh
+ STEAMVR_VRENV=/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/vrenv.sh
+++ dirname /home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/vrenv.sh
++ cd /home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/..
++ pwd
+ export STEAMVR_TOOLSDIR=/home/didier/.steam/debian-installation/steamapps/common/SteamVR
+ STEAMVR_TOOLSDIR=/home/didier/.steam/debian-installation/steamapps/common/SteamVR
++ cd /home/didier/.steam/debian-installation/steamapps/common/SteamVR/../runtime
/home/didier/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh: line 18: cd: /home/didier/.steam/debian-installation/steamapps/common/SteamVR/../runtime: No such file or directory
++ pwd
+ RUNTIMEDIR=/home/didier/.steam/steam/steamapps/common/SteamVR/bin
++ cd /home/didier/.steam/debian-installation/steamapps/common/SteamVR/../sdk
/home/didier/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh: line 19: cd: /home/didier/.steam/debian-installation/steamapps/common/SteamVR/../sdk: No such file or directory
++ pwd
+ SDKDIR=/home/didier/.steam/steam/steamapps/common/SteamVR/bin
+ case $(uname) in
++ uname
+ '[' -z '' ']'
+ exec /home/didier/.steam/root/ubuntu12_32/steam-runtime/run.sh /home/didier/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh ./vrmonitor.sh
++ readlink -f /home/didier/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh
+ export STEAMVR_VRENV=/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/vrenv.sh
+ STEAMVR_VRENV=/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/vrenv.sh
+++ dirname /home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/vrenv.sh
++ cd /home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/..
++ pwd
+ export STEAMVR_TOOLSDIR=/home/didier/.steam/debian-installation/steamapps/common/SteamVR
+ STEAMVR_TOOLSDIR=/home/didier/.steam/debian-installation/steamapps/common/SteamVR
++ cd /home/didier/.steam/debian-installation/steamapps/common/SteamVR/../runtime
/home/didier/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh: line 18: cd: /home/didier/.steam/debian-installation/steamapps/common/SteamVR/../runtime: No such file or directory
++ pwd
+ RUNTIMEDIR=/home/didier/.steam/steam/steamapps/common/SteamVR/bin
++ cd /home/didier/.steam/debian-installation/steamapps/common/SteamVR/../sdk
/home/didier/.steam/steam/steamapps/common/SteamVR/bin/vrenv.sh: line 19: cd: /home/didier/.steam/debian-installation/steamapps/common/SteamVR/../sdk: No such file or directory
++ pwd
+ SDKDIR=/home/didier/.steam/steam/steamapps/common/SteamVR/bin
+ case $(uname) in
++ uname
+ '[' -z /home/didier/.steam/root/ubuntu12_32/steam-runtime ']'
+ VRSTARTUP=/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrstartup
+ QT_DIR=/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/qt
++ pwd
+ export LD_LIBRARY_PATH=/home/didier/.steam/steam/steamapps/common/SteamVR/bin:/home/didier/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/didier/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/qt/lib:/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64:/home/didier/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_32:/home/didier/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_64:/usr/lib/x86_64-linux-gnu/libfakeroot:/lib/i386-linux-gnu:/usr/local/lib:/lib/x86_64-linux-gnu:/lib:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib/i386-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib
+ LD_LIBRARY_PATH=/home/didier/.steam/steam/steamapps/common/SteamVR/bin:/home/didier/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/didier/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/qt/lib:/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64:/home/didier/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_32:/home/didier/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_64:/usr/lib/x86_64-linux-gnu/libfakeroot:/lib/i386-linux-gnu:/usr/local/lib:/lib/x86_64-linux-gnu:/lib:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib/i386-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib
+ export VRCOMPOSITOR_LD_LIBRARY_PATH=/home/didier/.steam/steam/steamapps/common/SteamVR/bin:/home/didier/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/didier/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/qt/lib:/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64:/home/didier/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_32:/home/didier/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_64:/usr/lib/x86_64-linux-gnu/libfakeroot:/lib/i386-linux-gnu:/usr/local/lib:/lib/x86_64-linux-gnu:/lib:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib/i386-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib
+ VRCOMPOSITOR_LD_LIBRARY_PATH=/home/didier/.steam/steam/steamapps/common/SteamVR/bin:/home/didier/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/didier/.steam/steam/steamapps/common/SteamVR/bin/bin/linux64:/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/qt/lib:/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64:/home/didier/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_32:/home/didier/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_64:/usr/lib/x86_64-linux-gnu/libfakeroot:/lib/i386-linux-gnu:/usr/local/lib:/lib/x86_64-linux-gnu:/lib:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib/i386-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu:/home/didier/.steam/root/ubuntu12_32/steam-runtime/lib:/home/didier/.steam/root/ubuntu12_32/steam-runtime/usr/lib
+ exec ./vrmonitor.sh
+++ dirname /home/didier/.steam/steam/steamapps/common/SteamVR/bin/vrmonitor.sh
++ cd /home/didier/.steam/steam/steamapps/common/SteamVR/bin/
++ pwd
+ VRBINDIR=/home/didier/.steam/steam/steamapps/common/SteamVR/bin
+ [[ -n /home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/vrenv.sh ]]
+ case $(uname) in
++ uname
+ VRMONITOR=/home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrmonitor
+ exec /home/didier/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrmonitor
Using breakpad crash handler
Setting breakpad minidump AppID = 250820
Forcing breakpad minidump interfaces to load
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
QFactoryLoader::QFactoryLoader() checking directory path "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms" ...
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqeglfs.so"
"Plugin verification data mismatch in '/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqeglfs.so'"
not a plugin
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqlinuxfb.so"
"Plugin verification data mismatch in '/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqlinuxfb.so'"
not a plugin
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimal.so"
"Plugin verification data mismatch in '/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimal.so'"
not a plugin
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimalegl.so"
"Plugin verification data mismatch in '/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimalegl.so'"
not a plugin
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqoffscreen.so"
"Plugin verification data mismatch in '/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqoffscreen.so'"
not a plugin
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqvnc.so"
"Plugin verification data mismatch in '/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqvnc.so'"
not a plugin
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so"
"Plugin verification data mismatch in '/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so'"
not a plugin
This application failed to start because it could not find or load the Qt platform plugin "xcb".
Reinstalling the application may fix this problem.
crash_20210403012158_1.dmp[11876]: Uploading dump (out-of-process)
/tmp/dumps/crash_20210403012158_1.dmp
Aborted (core dumped)
I don’t understand what that Plugin verification data mismatch means though, is it related to some bundled version of Qt?
So, I reverted everything and… well the dashboard is still working, the monitor as well and I can properly exit SteamVR. Only thing that doesn’t seem to work is the desktop – it was working yesterday however, when I tried launching the tutorial (which never starts). Then I played Half Life: Alyx, I think I launched it directly from Steam, and I didn’t have the dashboard anymore. And now it’s back…
@DidierLoiseau I have a similar experience shortly after having posted above script - it is a moving target, so it could be anything and nothing though.
Might be a good idea to link this in this context:
https://github.com/ValveSoftware/SteamVR-for-Linux/issues/231#issuecomment-813100568
@frostworx Yeah it seems very random for me. It seems most of the time the dashboard works, sometimes even the desktop view, sometimes I don’t have the monitor but it seems manually running it fixes it.
Depending on from where SteamVR is started it is also started by a different program, so expanding the LD_LIBRARY_PATH needs to be in multiple places (most do probably already know this, but doesn't hurt to mention it again imho)
To make the search engine happy here are some stdout errors which possibly can occur:
vrcompositor: symbol lookup error ... common/SteamVR/bin/linux64/vrcompositor: undefined symbol: VRVirtualDisplay
vrmonitor: symbol lookup error ... common/SteamVR/bin/linux64/vrmonitor: undefined symbol: VRControlPanel
SteamVR/bin/vrenv.sh: line 18: cd: ... common/SteamVR/../runtime: No such file or directory (harmless cosmetical glitch)
SteamVR/bin/vrenv.sh: line 19: cd: ... common/SteamVR/../sdk: No such file or directory (harmless cosmetical glitch)
vrstartup: error while loading shared libraries: libsteam_api.so: cannot open shared object file: No such file or directory
I tried if renaming the affected binaries vrcompositor, vrmonitor and vrstartup to "(*.bin)" and creating corresponding LD_LIBRARY_PATH expanding scripts would help, but it is not enough (SteamVR doesn't start correctly - haven't tested more into that direction)
What works best for me (Dashboard works, start VR with HMD button, knuckles and autostart it from starting a VR game from the desktop client - I hope this always works now, until we see an official fix) is starting steam like this:
STEAMVR_TOOLSDIR="$HOME/.local/share/Steam/steamapps/common/SteamVR"
LD_LIBRARY_PATH="${STEAMVR_TOOLSDIR}/bin/linux64/:${LD_LIBRARY_PATH}" exec /usr/lib/steam/steam "$@"
and expand the LD_LIBRARY_PATH in vrwebhelper.sh like this:
export LD_LIBRARY_PATH="${DIR}:${STEAM_RUNTIME_HEAVY}${LD_LIBRARY_PATH+:$LD_LIBRARY_PATH}"
(so only added ${DIR}:)
Everything else (including the qt stuff) is left untouched. So generally a slim variant of @Supreeemes findings.
SteamVR/bin/vrenv.sh: line 18: cd:...common/SteamVR/../runtime: No such file or directory(harmless cosmetical glitch)
SteamVR/bin/vrenv.sh: line 19: cd:...common/SteamVR/../sdk: No such file or directory(harmless cosmetical glitch)
Not glitches at all, but bugs: lines 17, 18 and 19 have unquoted subshell expansions. Using "$(…)" instead of $(…) will fix the errors.
I poked around in the SteamVR folder and I cannot find any folder named "sdk" or "runtime".
[develon@FoatOS SteamVR]$ find ~/.local/share/Steam/ -name "sdk"
[develon@FoatOS SteamVR]$ find /steamdrive -name "sdk"
[develon@FoatOS SteamVR]$
As you can see, I checked the main steam folder (where SteamVR resides) and my separate steam drive (where my other games are installed), and there's no sdk folder anywhere to be found. So even applying the fix above this comment doesn't resolve these errors because these folders don't exist on my machine.
Replying to https://github.com/ValveSoftware/SteamVR-for-Linux/issues/255#issuecomment-813534065
Thank you so much for posting this solution, it has completely solved my dashboard issues!
For others that are trying to implement this fix, you'll need to find the primary steam script (which for on Arch was /usr/bin/steam-runtime) to add the changes mentioned. I looked at my /usr/share/applications/steam.desktop file to track this down, and then added the extra lines into the script:
STEAMVR_TOOLSDIR="$HOME/.local/share/Steam/steamapps/common/SteamVR"
LD_LIBRARY_PATH="${STEAMVR_TOOLSDIR}/bin/linux64/:${LD_LIBRARY_PATH}"
exec /usr/lib/steam/steam "$@"
@frostworx I was hoping you could explain the ${LD_LIBRARY_PATH+:$LD_LIBRARY_PATH} syntax that's used in vrwebhelper.sh. I realize that this was already there, but I've never seen the +: syntax used before. Any insight would be appreciated.
I was also curious how we could get an official fix for this upstream. This is probably one of the most annoying bugs with Steam VR for Linux today.
Hey @rstube
Personally I wouldn't have use it the +: myself, I simply left it untouched.
I'd assume a regular expand like
export LD_LIBRARY_PATH="${DIR}:${STEAM_RUNTIME_HEAVY}:$LD_LIBRARY_PATH}"
would work as well.
TBH I've never seen that syntax before as well and do not know if it actually makes sense or simply is a harmless useless glitch (or bug, if that makes some people happy)
Indeed it would be nice to get some official bugs fixed upstream, not only this issue, but several others as well which seem to be ignored for years.
${FOO+value_if_set} expands to value_if_set if FOO has a value, else to the empty string. Use of it in this case is not a bug; it's defensive coding. (Similarly, there's ${FOO-value_if_unset} which is exactly the reverse – if FOO has no value, value_if_unset. else $FOO.)
The intent here, why …${LD_LIBRARY_PATH+:$LD_LIBRARY_PATH} rather than …:$LD_LIBRARY_PATH, is used, is to avoid the new value of LD_LIBRARY_PATH ending in :.
${FOO+value_if_set}expands tovalue_if_setifFOOhas a value, else to the empty string. Use of it in this case is not a bug; it's defensive coding. (Similarly, there's${FOO-value_if_unset}which is exactly the reverse – ifFOOhas no value,value_if_unset. else$FOO.)The intent here, why
…${LD_LIBRARY_PATH+:$LD_LIBRARY_PATH}rather than…:$LD_LIBRARY_PATH, is used, is to avoid the new value ofLD_LIBRARY_PATHending in:.
Ah that makes sense. Thanks for taking the time to explain this. I'm still learning shell scripting hence my confusion.
I had the exact same problem - VR Dashboard was not loading in game at all.
I noticed errors in ~/.local/share/Steam/logs/vrwebhelper_pairing.txt (and other log files):
Sun Jul 11 2021 18:45:47.771954 - CEF Local Resource Load Error: http://localhost:27062/fonts/get_font?font=motiva-sans-regular.ttf -> 404 (Not Found)
Sun Jul 11 2021 18:45:47.773010 - CEF Local Resource Load Error: http://localhost:27062/fonts/get_font?font=motiva-sans-regular.ttf -> 404 (Not Found)
These fonts are located in ~/.local/share/Steam/steamapps/common/SteamVR/resources/webinterface/fonts directory but it seems Valve has made a boo boo with putting these fonts with the incorrect case - this works on Windows but surely it won't work on Linux case sensitive filesystems.
The fix was to simply create copies of these files (and maintain these when upgrading so better prepare a script to run every now and then):
cd ~/.local/share/Steam/steamapps/common/SteamVR/resources/webinterface/fonts
cp Motiva-Sans-Bold.ttf motiva-sans-bold.ttf
cp Motiva-Sans-Regular.ttf motiva-sans-regular.ttf
After restarting SteamVR the dashboard is now visible and fully functional.
I have other issues but none related - a serious flickering on SteamVR dashboard (none in games, amdgpu), Pavlov multiplayer not working with EOS_InvalidUser error when creating lobby but these are for another day.
Hello @t00, I don't recall hearing of a font-related stability issue before with vrdashboard and it can work with the case mismatched on those fonts (but that issue may lead to text unexpectedly missing or using a fallback font). I suspect you got lucky in your testing, and it would be nice if a Valve dev could evaluate that separately.
Please open a new issue report with your findings.
cd ~/.local/share/Steam/steamapps/common/SteamVR/resources/webinterface/fonts
cp Motiva-Sans-Bold.ttf motiva-sans-bold.ttf
cp Motiva-Sans-Regular.ttf motiva-sans-regular.ttf
Better to use ln.
I tried using the suggested workaround (expanding LD_LIBRARY_PATH) but the dashboard still doesn't show up. Worse I can't even get a game to run. Which log files were you inspecting to find the errors? I suspect most people posting here are on debian based distros so I thought I'd tag my specs.
Fedora 35 kernel 5.15.6 AMD 5950X/5700XT.
Saw this in the logs (steam's stderr):
/usr/lib/libfreetype.so.6: undefined symbol: hb_ot_tags_from_script_and_language
Downgraded freetype2 (on Arch) from 2.11 to 2.10 and the dashboard appears again. Not familiar with Fedora's packaging but it might be worth a try @minionprocyk
You can also compile the 2.10.4 version of freetype and place the libfreetype.so.6 file into SteamVR/bin/linux64 so you don't need to downgrade it globally.
Hello @Supreeeme, @Kirottu, the issue you're discussing is being tracked at #465, and is newer than this issue report.
I'm also unable to open up the overlay menu in all my apps; I'm on EndeavourOS (arch kernel 5.15.11) running steamvr beta.
System Info: https://gist.github.com/TheDrawingCoder-Gamer/fda5bd8c29bcaac65ff11333820333f1
Implementing these fixes borks my install; I can launch steamvr but it has no computer ui, and the dashboard still doesn't work
Using the fixVRDash script also borks my steamvr ui (I did a fresh install of it by uninstalling then deleting the SteamVR folder in steamapps/common) and it still doesn't fix my overlay
A friend of mine who uses Windows seems to be reporting a similar error. Their screen gets pixelated, but the actual dashboard does not appear. So, this may be a SteamVR error in general, rather than a Linux-specific one.
Pinging this thread, since its the one that's open.
Can't get Overlay, Settings, Tutorial or Development Tools to open, except Webconsole which is completely empty.
Running Arch, Linux redacted 5.18.14-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 23 Jul 2022 11:46:17 +0000 x86_64 GNU/Linux
Proud new owner of Valve Index.
Attempted all the fixes from previous threads:
- STEAM_RUNTIME_HEAVY fix
- LD_LIBRARY_PATH adaptation
- libfree2 downgrade local
- steam-native + downgrade global
Controller and headset firmware are updated. Base stations didn't ask for one.
Added the setcaps fix to allow it to do superuser stuff it wants to do.
Logs don't show any library mismatch errors (I deleted the whole director and tried lookign for anything suspicious). It seems like everything is running smoothly yet, except this - it seems as if its logging my system button clicks, and doesn't know what to do with it:
Thu Jul 28 2022 06:48:18.421481 - ================================================================================================
Thu Jul 28 2022 06:48:18.421518 - vrdashboard 1.23.6 startup with PID=316362, config=/home/john/.local/share/Steam/config, runtime=/home/john/.local/share/Steam/steamapps/common/SteamVR
Thu Jul 28 2022 06:48:18.421577 - vrclient type=VRApplication_Overlay
Thu Jul 28 2022 06:48:18.423089 - [Settings] Load Default Json Settings from /home/john/.local/share/Steam/steamapps/common/SteamVR/drivers/htc/resources/settings/default.vrsettings
Thu Jul 28 2022 06:48:18.423174 - [Settings] Load Default Json Settings from /home/john/.local/share/Steam/steamapps/common/SteamVR/drivers/lighthouse/resources/settings/default.vrsettings
Thu Jul 28 2022 06:48:18.423250 - [Settings] Load Default Json Settings from /home/john/.local/share/Steam/steamapps/common/SteamVR/drivers/null/resources/settings/default.vrsettings
Thu Jul 28 2022 06:48:18.423568 - [Settings] Load Default Json Settings from /home/john/.local/share/Steam/steamapps/common/SteamVR/resources/settings/default.vrsettings
Thu Jul 28 2022 06:48:18.424350 - [Settings] Load Json Settings from /home/john/.local/share/Steam/config/steamvr.vrsettings
Thu Jul 28 2022 06:48:18.438357 - CIPCPipe::ConnectPipe(SteamVR_Namespace) attempting connect to steamvr:SteamVR_Namespace
Thu Jul 28 2022 06:48:18.438473 - CSharedResourceNamespaceClient::Init(): received namespace data 316278
Thu Jul 28 2022 06:48:18.438545 - CIPCPipe::ConnectPipe(VR_ServerPipe_316278) attempting connect to steamvr:VR_ServerPipe_316278
Thu Jul 28 2022 06:48:18.446248 - Received success response from vrserver connect
Thu Jul 28 2022 06:48:18.751775 - App key after connect message:
Thu Jul 28 2022 06:48:18.767927 - CIPCPipe::ConnectPipe(VR_CompositorPipe_316278) attempting connect to steamvr:VR_CompositorPipe_316278
Thu Jul 28 2022 06:48:18.768168 - Received success response from vrcompositor connect
Thu Jul 28 2022 06:48:18.768193 - Initializing the limited version of CVRCompositorClient
Thu Jul 28 2022 06:48:30.769115 - Unable to find input 'z' in filter click_button_actions_legacy_17_user_hand_left_input_thumbstick
Thu Jul 28 2022 06:48:30.774655 - Unable to find input 'z' in filter click_button_actions_legacy_17_user_hand_left_input_thumbstick
Thu Jul 28 2022 06:49:10.243811 - Unable to find input 'z' in filter click_button_actions_legacy_17_user_hand_left_input_thumbstick
Thu Jul 28 2022 06:49:10.243877 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Jul 28 2022 06:53:55.361636 - VR_Shutdown called
Thu Jul 28 2022 07:02:53.646518 - //==============================================================================================
As some games require overlay keyboard, I'd really appreciate some help. Sorry if I failed to include some specific info, first time posting bugs here - ask me and I shall post what's needed.
vrwebhelper is failing with
./vrwebhelper: symbol lookup error: /usr/lib/libharfbuzz.so.0: undefined symbol: FT_Get_Transform
I think libharfbuzz is missing from the steam runtime used by vrwebhelper
Moving libpango* and libharfbuzz* into pinned_libs_64 fixed the problem for now.
Attempted this, no change.
Moved libpango-1.0.so and libharfbuzz.so to ~/.steam/steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/steam-runtime-heavy/pinned_libs_64.
In which logfile did you see undefined symbol message? I've gone through all logs, and didn't spot any errors.
Will attempt moving to ubuntu12_64/steam-runtime-heavy as this is the runtime that logs show is being used, and see if it works. Will edit the message if it does.
Edit: doesn't work in second directory either.
Edit 2: just to ensure problem isn't the keyboard operator - I actually copied libpango* and libharfbuzz* to both directories containing pinned 64bit libraries, and still no dice :sob:
Sorry for doubleposting, but this seemed important:
I have been scouting the logs to find, again, any error I might've missed, and all logs point out to vrwebhelper being happily started (which would eliminate all undefined symbol errors that would prevent startup).
Indeed - every process is running (filtered for vr)
I am nearly convinced the issue is with the log line in vrclient_steam.txt:
Sat Jul 30 2022 20:04:10.406448 - Unable to find input 'z' in filter click_button_actions_legacy_17_user_hand_left_input_thumbstick
If I'm pieceing this together well - it seems that the button that is supposed to summon the dashboard, is mapped to z input, rather than dashboard opening. the whole click_button_action.... part actually changes from left to right depending on which controller I click with.
The vrserver.txt shows a lot of log lines about Excessive bindings some some legacy bindings being NOT empty:
...
2796 Sat Jul 30 2022 20:06:26.711613 - Excessive binding loads from steam (15599): crc=4054094268 lc=6 Reload=F res=2
2797 Sat Jul 30 2022 20:06:26.711669 - ===== indexhmd: state=4, NOT empty, uri=file:///home/john/.local/share/Steam/steamapps/common/SteamVR/resources/config/legacy_bindings_generic_hmd.json
2798 Sat Jul 30 2022 20:06:26.711741 - ===== knuckles: state=4, NOT empty, uri=file:///home/john/.local/share/Steam/steamapps/common/SteamVR/drivers/indexcontroller/resources/input/legacy_bindings_index_controller.json
...
There's a lot of these. I tried removing the mentioned JSON files, and it didn't change the outcome.
The webserver itself is running on stated port, but trying to navigate to URLs from logs gives an empty page in browser. I expected at least to see the keyboard, but nay.
Out of ideas :shrug: :disappointed:
Would really love to play SkryimVR, but unless I can type in character's name - which requires vr overlay with an onscreen keyboard... ain't gonna happen.
@machinedgod You might be experiencing a different problem unfortunately. The undefined symbol problem happens for me on ArchLinux, and after I fixed it the dashboard works fine.
On Manjaro the dashboard is not working anymore since a few weeks. This might be due to a system update... Any idea what to try ?
vrwebhelper is up and running.
On Manjaro the dashboard is not working anymore since a few weeks. This might be due to a system update... Any idea what to try ?
vrwebhelperis up and running.
try getting into ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64 and copying your libfreetype.so.6 (e.g. /usr/lib/libfreetype.so.6.18.3) over the one that's in there. Worked for me on Arch.
Thanks @Patola, that did the trick !
$ cd ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64
$ mkdir backup
$ mv libfreetype* backup
$ ln -s /usr/lib/libfreetype.so.6.18.3
I haven't had any issues with the dashboards for quite some time. I am on Arch Linux with testing repository and I don't really use any of the workarounds posted here.
I haven't had any issues with the dashboards for quite some time. I am on Arch Linux with testing repository and I don't really use any of the workarounds posted here.
From my own research, it turns out that Dashboard seems to dynamically load some of Gnome libraries, or depend on Mutter in some way.
I don't use Gnome, but installed it just for a test, and lo and behold - it all works just fine. Never even realized that controllers actually have battery indicators on them in VR.
However, even with Gnome installed, running SteamVR in my normal manager (xmonad) - nada.
Never figured out what's the thing that needs to be loaded.
I can't seem to reproduce this at all anymore-- SteamVR 2.8.4 Beta + Steam Beta Client. Every time SteamVR starts, it seems the overlays start up with it. The Desktop views don't seem to work reliably, but that isn't the scope of this issue (which was... The dashboard just plain doesn't show up at all). The IPD overlay works, all the stuff SteamVR provides by itself seems to work properly.
Launch options
RADV_PERFTEST=aco`**x1 2020-06SDL_Gx7 2020-02WINEPREFIXx1 2020-01WINEPREFIX=$PFXx1 2020-01
Launch lines
STEAMVR_WEBHELPER=0 %command%x1 2019-10
Describe the bug
When SteamVR launches, the empty grid successfully loads. After that, nothing seems to work. Games will not launch (fail to connect) and SteamVR intermittently crashes and shuts down. Games hang at startup, at various levels of initialization (VRChat doesn't even get a window open, Beat Saber makes it to a window but never draws anything)When pressing the System button on a controller, no overlay opens.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
SteamVR works. The dashboard opens, games launch successfully.
System Information (please complete the following information):
nvidia-settingsorvulkaninfo | grep driverInfo: driverInfo = Mesa 19.1.6 (LLVM 8.0.1)Screenshots
Additional context
Seems to have started after rebooting my system.
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.