-
Notifications
You must be signed in to change notification settings - Fork 48
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
egl-wayland > 1.1.13 causes looking glass window to disappear #149
Comments
If it works in 1.1.13 and doesn't work with the latest do you know what commit caused it? If not I can reproduce and bisect. |
It was broke in 1.1.15, if I remember correctly. |
Do you have an easier reproduction app than looking glass? Something where I don't have to set up an entire VM to reproduce this? How much time is "a short while"? Also, does this happen on other wlroots compositors or is it specific to hyprland? Can you run with WAYLAND_DEBUG=1? I'd like to check the output of that to ensure that buffers are still getting sent to the compositor. |
I know, it's so hard to repro but I can't remember what was the other app that did it as well, it is very consistent on Looking Glass though. I'm happy to help debug closer I just don't know how. |
Thanks for the details, unfortunately I couldn't find anything obviously incorrect and it looks like we are still sending valid buffers. There is one spot in the middle where it seems to recreate the buffers and such, I wonder if that's where the issue starts. What are you doing in looking glass when this happens? Just using a VM or at the loading page? You could also try disabling explicit sync using I would definitely test with two other compositors if you're able to. From what I can see it seems like valid buffers with valid sync data are being sent to the compositor. |
Just from using the VM, it happens more when I move the mouse. I was gonna try sway but it kinda requires me to switch drivers off propietary, do you have any suggestions on what else should I try? Not sure if Plasma or Gnome is way overkill. |
Running with the explicit sync env var: https://gist.github.com/blackxored/dbba96818f69e36bb09bed3fd6e6d8a5 |
It still reproduces with explicit sync disabled? Either Gnome or Plasma are good comparisons. I've run sway fine with proprietary drivers using the vulkan renderer and disabling hw cursors. |
It happens the same in Plasma, it just takes longer.
|
This looks like a different issue:
The above does not appear in your hyprland+looking glass log afaict. This is caused by the in-progress commit for surface 43 getting interrupted by some The error happens because the timeline points are being sent, but the app does some commits simultaneously so only the release_point ends up in the final commit:
|
Yeah, most likely different, but so far happening in Sway (default drivers), Plasma and the original (Hyprland). EDIT: to add more to the probably placebo effect I'm having with it being mouse related, it looks like if I choose to capture inputs on Looking Glass it takes noticeably longer to surface. Still happens though. |
Using egl-wayland 1.1.17 (driver version 565.77) This is what I get with
OpenGL renderer in Looking Glass
|
Please let me know how to get a proper debug log and I'll more than happily go through the steps and add it to the post.
This might happen on more applications, but it shows up consistently while using Looking Glass.
Any version greater than 1.1.13 makes the window disappear after a short while, and I believe it happens consistently if you move your mouse around a lot (might be placebo effect, but sometimes I can play games on a controller for hours without it closing, the second I touch the mouse it starts happening again).
Relevant system info:
OS: Both Arch and NixOS unstable
WM: Hyprland
Versions affected: > 1.1.13.
I've asked both in Looking Glass and Hyprland discords and they seem to point this to upstream, so here I am hoping we can get to the bottom of it somehow.
In the case of Looking Glass, I can still hear the audio coming from the VM, while the window is nowhere to be found, not sure if that helps.
Pinning 1.1.13 definitely gets rid of the issue.
The text was updated successfully, but these errors were encountered: