Unable to re-start the ALVR server once it has been closed

[tcrass]

Description

After closing the Dashboard, I'm unable to re-start the ALVR server, neither from the start menu, nor from the command line. Sometimes there's a brief flicker, suggesting that the GUI appears, just to disappear again in the next moment. Unfortunately, there's no log or any other messages being printed to the console when directly issuing alvr_launcher from the terminal.

General Troubleshooting

• [x] I carefully followed the instructions in the README and successfully completed the setup wizard
• [x] I read the ALVR Wikis here and here

Environement

Hardware

Note: for Linux, an upload to the hw-probe database is preferred: hw-probe -all -upload

https://linux-hardware.org/?probe=bc0462d8e3

CPU:

GPU:

Audio:

Installation

ALVR Version:

17.0.1+1643781622+0541c19e on both client and server

SteamVR Version:

1.20.4

Install Type:

• [x] Packaged (exe, deb, rpm, etc)
• [ ] Portable (zip)
• [ ] Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):

Debian GNU/Linux 11 (bullseye) (up-to-date)

[subjectdenied]

i see this behaviour if steam and/or steamvr is still open, normally i start steam (revoke its window) and exit it from the menu. after this alvr is working again

[tcrass]

i see this behaviour if steam and/or steamvr is still open, normally i start steam (revoke its window) and exit it from the menu. after this alvr is working again

Confirmed -- after stopping Steam, I can successfully re-launch ALVR! Good to know, but this somehow doesn't seem right, does it?

[Niroc]

it's SteamVR not stopping properly run... ps aux | grep -iE 'steam|vr'

and kill it's runaway processes. (usually there a "reaper" process which is meant to kill this stuff but, it falls over sometimes. just killing that can usually get rid of all the other processes)

[tcrass]

Hi Niroc,

it's SteamVR not stopping properly run... ps aux | grep -iE 'steam|vr'

and kill it's runaway processes. (usually there a "reaper" process which is meant to kill this stuff but, it falls over sometimes. just killing that can usually get rid of all the other processes)

at least in my case following subjectdenied's advice of just closing Steam seems to be sufficient. Not that I'm afraid of using the command line, but two mouse clicks are hard to beat! ;-)

Cheers -- Torsten

[The-personified-devil]

Is this issue still occurring?