- Run SteamVR and see if it notices...
How are you launching SteamVR?
Could you also try launching SteamVR in the following way and let me know if that works:
/tmp/SteamVRLauncherSetup.logI typically launch using the VR button on the top-right of the Steam client.
/tmp/SteamVRLauncherSetup.log:
Tue Jun 25 01:17:15 AEST 2019 - Error: user declined superuser request.
Okay, there's some funkiness going on under Arch... "steam-runtime" presents no dialog, but "steam-native" does.
+ zenity --no-wrap --question '--text=SteamVR requires superuser access to finish setup. Proceed?'
(zenity:31378): Gtk-WARNING **: 01:27:27.150: Unable to locate theme engine in module_path: "adwaita",
(zenity:31378): Gtk-WARNING **: 01:27:27.155: Unable to locate theme engine in module_path: "adwaita",
** (zenity:31378): WARNING **: 01:27:27.156: Could not load ui file /usr/share/zenity/zenity.ui: /usr/share/zenity/zenity.ui: required gtk+ version 3.0, current version is 2.24
(zenity:31378): Gtk-CRITICAL **: 01:27:27.156: IA__gtk_builder_get_object: assertion 'GTK_IS_BUILDER (builder)' failed
(zenity:31378): Gtk-CRITICAL **: 01:27:27.156: IA__gtk_builder_get_object: assertion 'GTK_IS_BUILDER (builder)' failed
+ pErr 'Error: user declined superuser request.'
++ date
+ echo 'Tue Jun 25 01:27:27 AEST 2019 - Error: user declined superuser request.'
+ return 1
+ '[' 1 '!=' 0 ']'
+ zenity --no-wrap --info '--text=SteamVR setup is incomplete, some features might be missing. See /tmp/SteamVRLauncherSetup.log for details.'
Thanks for the detailed troubleshooting, that makes your issue the same as https://github.com/ValveSoftware/steam-runtime/issues/104.
Hello @SketchStick, per "Use the host's zenity program when available for basic dialogs during startup" in the SteamVR 1.6.3 beta update, please retest this issue.
"too soon" (tm)
The fix also requires an update to Steam client beta to work. Steam beta should update soon, I'll flag this again.
Please restest this issue - make sure to use the Steam Beta client as well.
The prompt opened upon starting SteamVR and added cap_sys_nice to vrcompositor-launcher. Thank you for the fix!
Tested with SteamVR beta 1.6.3 and Steam client beta built: Jul 11 2019, at 22:28:23
Not sure why this was closed, it doesn't pop up. @SketchStick did you launch SteamVR from within steam or directly (vrstartup.sh)? For VR if I understand the intent behind the logic in vrstartup.sh, it requires cap_sys_nice rather then suggest it. I still see errors popup in /tmp/SteamVRLauncherSetup.log though it doesn't prompt.
Not sure about the other uses.
@h1z1
It's closed because on my end this bug is fixed and works as intended in steam client beta and steamvr beta, when starting steamvr from within both steam-native and steam-runtime.
If you want to debug things on your end, you can repeat the same steps I did. Just make sure you opt in to both Steam beta and SteamVR beta before doing so.
The steps I took are:
sudo updatedb && locate vrcompositor-launchersudo setcap -r <vrcompositor-launcher-path-here>steam or steam-runtime from a terminalgetcap <vrcompositor-launcher-path-here> to see if cap_sys_nice was set/tmp/SteamVRLauncherSetup.logSteamVRLauncherSetup and grab the text until exec <steamvr-path-here>/vrstartup (or just generally run a search for "zenity")If you get the required gtk+ version 3.0 message then it might be a similar issue, or at least some conflict regarding zenity.
Your system information
Please describe your issue in as much detail as possible:
This assumes that vrcompositor-launcher should have cap_sys_nice set on it (as that allows async reprojection on AMD) and I do recall SteamVR running a script once to set some privileges, but I only saw it once.
vrcompositor-launcher has been silently losing cap_sys_nice on multiple occasions, I can only assume it's due to SteamVR updating? The problem is that once it loses those privileges, I get no warnings and that script that set it up initially doesn't kick in again. So async reprojection just doesn't work until I set those privileges manually.
Steps for reproducing this issue: