Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setpcap/getpcap unavailable, causes SteamVR to fail to launch #180

Closed
Goofybud16 opened this issue Feb 27, 2019 · 7 comments
Closed

setpcap/getpcap unavailable, causes SteamVR to fail to launch #180

Goofybud16 opened this issue Feb 27, 2019 · 7 comments

Comments

@Goofybud16
Copy link

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.
@Goofybud16
Copy link
Author

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.

@dromer
Copy link

dromer commented Feb 18, 2021

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

@dromer
Copy link

dromer commented Jun 19, 2021

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.

@JacekJagosz
Copy link

Can confirm, still an issue.

@stickmanism
Copy link

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

@Foxy6670
Copy link

Foxy6670 commented Oct 7, 2022

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

@Kame03
Copy link

Kame03 commented Jul 26, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants