Repository navigation
[Crash]: GTK 4.23 causes duplicate ext-background-effect-v1 objects on Wayland #13578
Issue DescriptionGhostty currently crashes at startup under KWin with GTK 4.23.3:
Both GTK and Ghostty are creating an KWin (afaik) allows only one background-effect object per surface, so it disconnects Ghostty with a Wayland protocol error. The regression appears to have been introduced when GTK added native support for
Ghostty already implements this protocol itself: The following workaround resolves the crash by preventing GTK from binding the protocol, leaving Ghostty’s implementation active: GDK_WAYLAND_DISABLE=ext_background_effect_manager_v1 ghosttyI am unsure of whether Ghostty should just remove its implementation or disable GTK's by default. Expected BehaviorGhostty should open a window without issue. Actual BehaviorGhostty crashses on startup with the above error. Reproduction Steps
Ghostty LogsGhostty VersionOS Version InformationCachyOS Linux (Linux only) Display ServerWayland (Linux only) Desktop Environment/Window ManagerKDE Plasma 6.7.3 Minimal Ghostty ConfigurationNot relevant (background-blur = false does not fix this)Additional Relevant ConfigurationNo response I acknowledge that:
|
Replies: 1 comment 1 reply
|
Oh great, so they finally did what we've been asking for years at this point. The good news is GTK's implementation of blur is far more intelligent than what we're doing here. The bad news is that it will require a significant amount of tweaking. I for one welcome an "official" way to do this, but before we can figure out how to do that I think it's better to just disable our custom blur on GTK >=4.23 for now... |
Accepted as #13581