protonscr

setpcap/getpcap unavailable, causes SteamVR to fail to launch

steamvrclosed
ValveSoftware/SteamVR-for-Linux#180 · opened 2019-02-27 by Goofybud16 · updated 2023-07-26 · 7 comments · github
GGoofybud16 2019-02-27 github

Your system information

  • Steam client version (build number or date): Feb 18 2019, at 22:09:18, API v018, Package Versions 1550534751
  • Distribution (e.g. Ubuntu): Debian Testing
  • Graphics driver version (run nvidia-settings): Mesa 18.3.2
  • Gist for SteamVR System Information: System Info
  • Opted into Steam client beta?: No
  • Opted into SteamVR beta?: Yes
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

SteamVR 1.3.4 Beta will fail to launch due to the vrstartup.sh file failing. If I change the launch arguments in Steam to konsole --hold -e %command%, I get the following output:

+ '[' '' == '' ']'
+ pkexec setcap CAP_SYS_NICE=eip /home/goofybud16/.steam/steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher
Cannot run program setcap: No such file or directory
+ '[' 127 -ne 0 ']'
+ zenity --question '--text=Failed to finalize SteamVR setup. Continue anyway?'

** (zenity:13652): WARNING **: 15:37:15.456: Could not load ui file /usr/share/zenity/zenity.ui: /usr/share/zenity/zenity.ui: required gtk+ version 3.0, cur

(zenity:13652): Gtk-CRITICAL **: 15:37:15.456: IA__gtk_builder_get_object: assertion 'GTK_IS_BUILDER (builder)' failed

(zenity:13652): Gtk-CRITICAL **: 15:37:15.456: IA__gtk_builder_get_object: assertion 'GTK_IS_BUILDER (builder)' failed
+ exit

If I manually comment out the zenity lines in the vrstartup.sh file, SteamVR will function properly.

My system DOES have getcap and setcap, but they are in sbin, and unavailable to the vrstartup script.

~$ which getcap
~$ sudo which getcap
/sbin/getcap

Steps for reproducing this issue:

  1. Update to SteamVR Beta 1.3.4
  2. Launch SteamVR
  3. Observe that SteamVR does not launch.
GGoofybud16 2019-03-06 github

I just tested with Beta 1.3.7 and this issue no longer appears to be present. SteamVR properly starts up with no additional modifications necessary.

Ddromer 2021-02-18 github

On debian buster I have to manually do a sudo setcap CAP_SYS_NICE=eip ~/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher

Ddromer 2021-06-19 github

On debian buster I have to manually do a sudo setcap CAP_SYS_NICE=eip ~/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher

Still needed, btw.

JJacekJagosz 2022-03-02 github

Can confirm, still an issue.

Sstickmanism 2022-03-28 github

Yes, I have this issue right now in Debian on my avl-mxe linux setup.

FFoxy6670 2022-10-07 github

Can someone re-open this? STILL an issue to this day.
Devuan (SysV) 5.10.140-1, kernel 5.10.0-18-amd64

KKame03 2023-07-26 github

Have you solved this issue, I'm also on devuan?

Nothing extracted yet.