SteamVR-for-Linux VS compton

**Links:**Github issue post 1: https://github.com/ValveSoftware/SteamVR-for-Linux/issues/21

When Vulkan drivers are ready maybe the Asahi Linux perhaps also be ready to run some SteamVR apps https://github.com/ValveSoftware/SteamVR-for-Linux/blob/mast...

A guess, but SteamVR can't recover from VR applications crashing causing all future ones to not work, might be Home crashing first. Try turning off Home, and restarting.

steam VR Linux issue tracker

I tried to launch Alyx after the setup, and got a 303 error like described here: https://github.com/ValveSoftware/SteamVR-for-Linux/issues/572

From there I went to the SteamVR for Linux Github to see if any bugs related to this were reported.

Yes, the beta - SteamVR Beta Update also has the same problem, but with extra bugs like this issue for "Shared IPC Compositor Init Failed (303)". The linux_v1.14 - Older build, for Linux users also has the same problem. The None beta version is the only one I can use, as it doesn't show the "Shared IPC Compositor Init Failed (303)" error.

I posted an issue on the SteamVR for Linux Github, but that's basically been abandoned so I'm trying my luck here.

Yeah you need to use a separate compositor along with it, like picom/compton.

The last update to compton was on April 30th 2017 (see https://github.com/chjj/compton).

Or we refer to different things. With "compositor" i mean this, like this. I do have noticed that some Wayland developers like to use "compositor" to mean the window system implementation itself (and then retrofitting the term on Xorg) but while in some way it might be valid with Wayland - since that assumes composition always happen - it is not correct for X.

# Compton Configuration, courtesy of Xubuntu Developers # Please note that Compton is not supported by Xubuntu and may not work # correctly for you. This file is provided as a set of sane defaults and is in # no way endorsed by the Xubuntu team. # # About Compton: https://github.com/chjj/compton # Heavily based on: https://bit.ly/1l5OrzL # Sample settings: https://github.com/chjj/compton/blob/master/compton.sample.conf # --- Backend (OpenGL used by default) # Related Links # https://github.com/chjj/compton/wiki/perf-guide # https://github.com/chjj/compton/wiki/vsync-guide backend = "glx"; paint-on-overlay = true; glx-no-stencil = true; glx-no-rebind-pixmap = true; unredir-if-possible = true; vsync = "opengl-swc"; # --- Shadows (Disable with shadow = false;) # The shadow exclude options are helpful if you have shadows enabled. # Due to the way compton draws its shadows, certain applications (Such as # shaped windows, custom popups, non-standard toolkits) will have visual glitches. shadow = true; # Enabled client-side shadows on windows. no-dock-shadow = true; # Avoid drawing shadows on dock/panel windows. no-dnd-shadow = true; # Don't draw shadows on DND windows. clear-shadow = true; # Zero the part of the shadow's mask behind the window (experimental). shadow-radius = 10; # The blur radius for shadows. (default 10) shadow-offset-x = -15; # The left offset for shadows. (default -15) shadow-offset-y = -12; # The top offset for shadows. (default -12) shadow-opacity = 0.4; shadow-exclude = [ "! name~=''", # "Unknown" windows, including xfwm4 alt-tab "n:e:Notification", "n:e:Plank", "n:e:Docky", "g:e:Synapse", "g:e:Kupfer", "g:e:Conky", "n:w:*Firefox*", "n:w:*Chrome*", "n:w:*Chromium*", "n:w:*VirtualBox*", "class_g ?= 'Notify-osd'", "class_g ?= 'Cairo-dock'", "class_g ?= 'Xfce4-notifyd'", "class_g ?= 'Xfce4-power-manager'", "class_g ?= 'Xfwm4'", # For the "new" xfwm4 alt-tab "_GTK_FRAME_EXTENTS@:c" # GTK+ 3 CSD windows https://github.com/chjj/compton/issues/189 ]; # --- Fading (Disable with fading = false;) fading = true; # Fade windows during opacity changes. fade-delta = 5; # The time between steps in a fade in milliseconds. (default 5). fade-in-step = 0.03; # Opacity change between steps while fading in. (default 0.03). fade-out-step = 0.03; # Opacity change between steps while fading out. (default 0.03). # --- Additional Settings detect-client-opacity = true; # --- Window type settings wintypes: { tooltip = { fade = true; shadow = false; opacity = 0.9; focus = true; }; };

Ok then. Are you sure that you aren't hitting this issue: https://github.com/chjj/compton/issues/402 ?

Mimicking Compiz features with openbox settings and picom: invert (active) window colors

This will depend on the compositor you choose to use. For DIY desktop environments based on X11, you can use Compton to set blur on translucent windows.