-
Notifications
You must be signed in to change notification settings - Fork 63
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
libGL error: MESA-LOADER: failed to retrieve device information #160
Comments
I am running into a similar issue. I think it's not the network but rather an issue with loading the video driver. I notice you have the Intel i915/iris and I have an issue with the AMD radeonsi some (null) drivers. Additionally, I actually have 2 GPUs, the AMD as mentiononed but also an NVidia GeForce RTX 4060 (Asus ROG Zephyrus GA402). The other thing to note in my case is that I'm running podman not docker. It should be a drop-in replacement but you never know. I can see the pen trail when I hover the pen over the tablet at a close distance and move it around but it stays on the "connecting to remarkable..." screen. And the pen marks my remarkable2 page but doesn't show up in the viewer.
|
The following fix quickly fixed the problem for me: https://stackoverflow.com/questions/71010343/cannot-load-swrast-and-iris-drivers-in-fedora-35/72200748#72200748 I do not have anymore the libGL error: MESA-LOADER, but I still cannot connect share the screen. Probably something related to #146 but not sure... |
Same issue here using Ubuntu 24.04 with Wayland with intel iGPU (MESA drivers). I suspect the previous commenter's fixes worked or happened only with eGPU/iGPU because switching those configurations most likely changed the display server back to X11. startup logs
The This can be solved by overriding the We could probably add support for wayland directly (QT_QPA_PLATFORM=wayland), though. This is most definitely a 'hack'. Changing the command to the following solves the issue: docker run \
--env XDG_SESSION_TYPE=x11 \
--env DISPLAY=$DISPLAY \
--network host \
--volume $CONFIG_DIR:/root/.config \
--volume /tmp/.X11-unix:/tmp/.X11-unix \
rmview |
hey @rgon I pulled your recent MR. When running as is, I still got the same errors
what I did to debug
I added to the dockerfile which does add that argument to my env in my docker container, but still the same issues persist. Local env `XGD_SESSION_TYPE` is x11, so it looks like I have been running X11 this whole time. Can you add any relevant laptop, remarkable details on your end and I can try to compare your setup vs mine? or if there are details on my side you'd like to know i'm happy to provide. |
Remarkable 2 SW version 3.11.2.5
Using VNC branch of rmview,
along with
rmview -v
insidesh docker-run.sh
results in the following behavior
I have the same issues people have described in #156 (red dot but stuck on connecting)
I wonder if they were to run
rmview -v
if maybe they are also having libGL issues?additional docker info
The text was updated successfully, but these errors were encountered: