-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
python3 / gtk3 client crashes under wayland #1925
Comments
With r20066 + r20067, the GTK3 client no longer crashes under wayland, but this changeset turns off ALL the code which calls the X11 bindings:
Some of those things will need to be replaced with native wayland API calls. And even with these fixes, the forwarded window now lack decorations and rendering is a mess too. |
The decorations problem is caused by CSD (Client Side Decorations). From Suboptimal window drawing on Windows:
KWin maintainer not happy about Gtk+ handling of CSD bugs: If you have to change your WM to support a new protocol to make things work, then it's clearly going to break everybody elses WM when you introduce this feature without warning. - exactly what happens here. GTK3 CSD on gtk_window_resize() also counts client side decorations size - is why we end up painting at the wrong location, painting over the window decorations. Client-Side Decorations Initiative Introducing the CSD Initiative: The only way to solve this problem long-term is to patch applications upstream to not use title bars. So this is what we’ll have to do - nothing said about if we do want to use the title bars? Time to drop GTK, at least under wayland? |
So, it turns out that what they've changed (in Fedora 28?) is the default GDK backend, now set to "wayland". Minimal backport: 20072 + 20073. |
Follow up: #2243. |
According to [https://bbs.archlinux.org/viewtopic.php?id=219796] this is a well known issues when running Gnome on Wayland. Discussed plenty of times
The text was updated successfully, but these errors were encountered: