Many terminal apps allow piping a command through. Previously, when trying to capture console logs, I've used Konsole for it. Set the following as the launch args for SteamVR in Steam after installing Konsole:
konsole --hold -e %command%
Putting that in your launch options should wrap the SteamVR launch command inside a Konsole instance, and allow you to see output (at least from the main executable.) --hold makes sure Konsole stays open after the process inside shuts down, so that may help show some useful log output.
Putting that in your launch options should wrap the SteamVR launch command inside a Konsole instance, and allow you to see output (at least from the main executable.)
--holdmakes sure Konsole stays open after the process inside shuts down, so that may help show some useful log output.
Yeah, so that didn't work unfortunately. It crashes basically as soon as it launches, so it doesn't have enough time to even open a konsole instance
same problem
same problem
I have a fresh install (EndeavourOS with hyprland) with the same issue, let me know if you need any logs.
QT_QPA_PLATFORM=xcb %command%
Fixed this for me
QT_QPA_PLATFORM=xcb %command%Fixed this for me
Well, well, well, the dashboard finally appeared and it's not crashing. This did it for me too. Thank you.
Closing thread
QT_QPA_PLATFORM=xcb %command%x2 2025-08
Describe the bug
After a fresh installation of SteamVR, it asks for sudo privileges to change a variable for a file. The app then "launches", nothing gets displayed on screen, then it crashes. I would provide terminal logs, but I don't know how to.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
SteamVR launches properly
System Information
Screenshots
n/a
Additional context
For my desktop environment/ window manager, I use Hyprland, which runs on Wayland.
My initial setup for arch was as minimal as possible with the HyDE project installed afterward.
As for if my Steam client is the flatpak version. I don't know. I used the AUR to install the latest stable release.
Browsing through the bug reports, a solution I came across was to start SteamVR with this launch option: steam-runtime-launch-options -- %command%.
The problem I ran into with that was that no matter what options I changed, it would still not launch and the options would not save.