-
Notifications
You must be signed in to change notification settings - Fork 16
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
(not so) harmless "Couldn't map window as subsurface" warning #38
Comments
It doesn't seem to happen with my Ubuntu 20.04 system GTK. Might have been introduced in GTK v3.24.21 |
I think this bug is what's causing an issue in the waybar project. Alexays/Waybar#859 |
Unlikely. It really is harmless (AFAIK) |
In my WIP port of PCManFM's desktop manager to Wayland using GTK Layer Shell, I'm getting You could reproduce this by compiling it yourself (preferably in combination with my fork of LibFM), starting it with When I add a |
All right, so my assessment is this warning is usually harmless, but in some cases (such as yours) it's possible to create a subsurface that actually fails to map property. Can you point me to where in your pcmanfm fork the troublesome search box subsurface is created? I'll want to write an integration test with a minimal example of this behavior so once it's fixed it stays fixed. |
However if I understand the GTK code I linked in my previous comment correctly, it thinks the parent (i.e. my full-screen GTK Layer Shell window) is not mapped. Like I said, if I change it so that it returns true even if the parent isn't mapped (for testing purposes, normally that wouldn't be a good idea of course), it's able to correctly map the Thanks for looking into it! |
With that code sample the issue was easy to reproduce, and with just one more |
When some popups appear (such as tooltips), the following warning is shown:
I believe this to be a harmless GTK bug (there's a lot of questionable logic around custom surfaces). Considering it's not causing any other problems, it's not worth trying to fix at this time.
The text was updated successfully, but these errors were encountered: