Same problem here... I tested it with Blender and it said there was no active runtime.
System Information:
This bug might be due to the openxr runtime manifest directory not existing. Can you try creating the following dir and trying again:
mkdir ~/.config/openxr/1/
If you have your XDG configuration directory configured to a different location, then create openxr/1 there instead.
Yes, that did it. Thanks!
Blender now finds the runtime but can't connect (it uses OpenGL, so no surprise there) but hello_xr with Vulkan worked without a problem.
Can also confirm this allows "set to default" to work.
In what circumstance would this directory already exist?
This bug might be due to the openxr runtime manifest directory not existing. Can you try creating the following dir and trying again:
mkdir ~/.config/openxr/1/If you have your XDG configuration directory configured to a different location, then create
openxr/1there instead.
This command fails if the openxr directory itself doesn't exist. Recommended command instead:
mkdir -p ~/.config/openxr/1
This command fails if the openxr directory itself doesn't exist. Recommended command instead:
mkdir -p ~/.config/openxr/1
I can also confirm that creating these directories fixed this issue for me, on Arch Linux.
This also worked for me, Ubuntu 20.04 (upgraded from previous Ubuntu 19.10 install).
I am also curious what if anything should be creating this folder to start with?
Thanks, this was puzzling me too. On Debian unstable if it matters.
Hello, it looks like a fix for this might have slipped in under the radar. Please retest.
Yes, this is fixed! I deleted ~/.config/openxr/ then launched SteamVR. Once I clicked "set as default", the prompt went away and openxr/1/active_runtime.json was created again.
I have /home/docmax/.config/openxr/1/active_runtime.json
{
"file_format_version": "1.0.0",
"runtime": {
"name": "Monado",
"library_path": "../../../lib/wivrn/libopenxr_wivrn.so",
"MND_libmonado_path": "../../../lib/wivrn/libmonado.so"
}
}
But OpenXR runtime "none". When i try to set
This bug might be due to the openxr runtime manifest directory not existing. Can you try creating the following dir and trying again:
mkdir ~/.config/openxr/1/
If you have your XDG configuration directory configured to a different location, then createopenxr/1there instead.This command fails if the openxr directory itself doesn't exist. Recommended command instead:
mkdir -p ~/.config/openxr/1
haha! This worked! on bazzite, iirc is redhat based, but thanks!
Nothing extracted yet.
Describe the bug
When I launch the latest SteamVR beta, I see the following message:
Clicking "Set as default" doesn't seem to do anything -- there is no password prompt to modify a system file, and the message doesn't go away (unless I hit Dismiss) and it comes back the next time I start SteamVR.
This appears in the terminal output when "Set as default" is clicked:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
"Set as default" makes an observable change.
System Information (please complete the following information):
Screenshots

Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.