I also seem to be having the same issue.
Although I can't be sure that it's the cause, the issue also began for me after updating SteamVR to the 1487886215 beta.
Also worth noting is the fact that I can launch the Dota 2 VR hub and Destinations separate from SteamVR and still have them work, minus the vr dashboard and other things I suspect are provided by SteamVR.
On the first launch after updating SteamVR to version 1487904548 Steam didn't crash. However, every attempt since still crashes Steam.
This could have just been a fluke, but either way at one point I did have both Steam and SteamVR running. (until Steam crashed afterwards, when I tried to run Portal 2 in VR theatre mode.)
I'm still experiencing this with 1487904548 as well.
I have been experiencing similar behavior to @tizzir where the first time worked but subsequent runs of SteamVR fail. rm -rf ~/.steam/, re-setting up Steam, opting into the Steam and SteamVR betas, then again works for only one time before the same behavior happens. On an Ubuntu 16.10 box.
I have this problem also, first run is fine but a second run of SteamVR just hangs on "Preparing to launch SteamVR". I have to delete the installation folder as uninstall option wont work.
I have this problem also, first run is fine but a second run of SteamVR just hangs on "Preparing to launch SteamVR". I have to delete the installation folder as uninstall option wont work.
@ryantux Do you reliably get this every time? If so, can you try turning off Steam cloud support before running it for the first time and see if the problem persists? To do this, right click on the game in your Steam library, select Properties, then in the Updates tab, uncheck the "Enable Steam Cloud synchronization for SteamVR" box.
Running with Steam stable client (opting out of the beta) seems to fix the issue, though I agree this is a poor workaround.
@Cheeseness, it happens every time on second launch after a clean install of SteamVr.
Disabling the steam cloud option does fix this so long as it's done before running it for first time as you say.
Thanks
@ryantux Thanks for confirming my suspicions! Smells like maybe the Steam client gets stuck thinking it's uploading something to to the cloud when SteamVR crashes (might be crashing on exit if you're not noticing crashes?)
It might be worth making a separate issue for this problem, though I'm not certain whether the SteamVR bug tracker or the Steam client bug tracker is the best place for it to go.
I have the same SIGSEGV in Steam client as OP. Same stack trace. The solution to use STEAM_RUNTIME=0 worked. But then SteamVR would SIGSEGV in vrcompositor, the stacktrace pointed to some Vulkan initialization, even though I had the Vulkan loader 1.0.39 like the Steam runtime. I tried to trick the launch script of SteamVR to force using the Steam runtime, but that did not help. The solution I have found was to copy .steam/steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/libvulkan.so.1 into a separate directory and start the Steam client with STEAM_RUNTIME=0 and LD_LIBRARY_PATH pointing to that directory. Now it works. Both Steam client and SteamVR can start without crashing. However Steam crashes when I stop SteamVR. But it is less annoying.
Fixed with today's SteamVR update 1489563880.
Nothing extracted yet.
Archlinux, RX 480
When started with
STEAM_RUNTIME=0 steamit doesn't crash. With the runtime enabled, steam crashes when start steamvr, but vrmonitor and vrcompositor keep running and working.steamvr system report
https://gist.github.com/ChristophHaag/e5ba90319a9d706a037a56e8b853a591
backtrace: