-
-
Notifications
You must be signed in to change notification settings - Fork 498
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
linux build and its crashing. I am not sure why, but this did not happen with the appimage #2070
Comments
Odd, i have a similar setup (Ryzen Processor, RTX card running proprietary, SteamVR 2.4.4) on an Ubuntu Based OS, but everything works perfectly for me. I wonder if it has anything to do with you running Wayland on Kwin, as I had to drop it for Gnome X11 due to my card hating it. I don't see any wayland natives here, so that might be one reason. |
Huh, I don't think I am on wayland:
|
Your hardware probe said Wayland, odd. |
Perhaps its wayland only in sddm?
SDDM is the login manager. perhaps its misreading. Also tested xeyes. that also works. so its X for sure. |
Hey, updating that its fixed, I see that its released in ALVR v20.8.1 |
Description
as requested by @Meister1593 opening a separate issue on comment #2056 (comment)
I downgraded for now to 20.6.1 where alvr does work for me (is there way to hold two versions on Quest 2? )
General Troubleshooting
Environment
Hardware
Note: for Linux, an upload to the
hw-probe
database is preferred:hw-probe -all -upload
https://linux-hardware.org/?probe=21882b12a8
CPU:
AMD Ryzen 9 4900HS with Radeon Graphics
GPU:
TU106M [GeForce RTX 2060 Max-Q]
GPU Driver Version:
nvidia 535 (proprietary)
Audio:
Installation
20.7.1:
ALVR Settings File:
SteamVR Version:
2.4.4
Install Type:
exe
,deb
,rpm
, etc)zip
)OS Name and Version (
winver
on Windows orgrep PRETTY_NAME /etc/os-release
on most Linux distributions):Ununtu 23.10
might be related to this: #2068
output of
ldd bin/alvr_dashboard
:output of
ldd lib64/alvr/bin/linux64/driver_alvr_server.so
:I also installed the flatpak and not sure where that went.
The text was updated successfully, but these errors were encountered: