Closed mytdragon closed 10 months ago
Sorry for taking such a long time to reply. I don't think this is an issue with the Rust crate, but with the underlying C library. There is an issue that seems relevant to your issue already: https://github.com/wmww/gtk4-layer-shell/issues/24 Have you tried using the most recent version of gtk4-layer-shell (the C library)? If you continue to have issues, please open an issue in their repo: https://github.com/wmww/gtk4-layer-shell
Hi @pentamassiv, it seems it was fixed with the last version of gtk4-layer-shell. So yeah it seems to be on the underlying C library, my bad sorry.
Bug description
Segfault only occurs after using
init_layer_shell()
to setup a window. Usinggtk::ApplicationWindow.destroy()
(or close() then cause a segfault. I've included a minimal repro to create a window with a button to open a window, initialize it with layer shell, and then destroying it on "esc" event that will trigger the segfault.If the layer shell part on build_window_2 is commented, the win.destroy won't cause a segfault.
Reproducible code
(Note that I'm a beginner in both rust and gtk, after asking for assistant on the rust server, some people told me that it shouldn't have trigger a segfault and that it might be useful to fill on issue.)
EDIT 1: I ported this example to gtk3 and gtk-layer-shell, it doesn't trigger a segfault. It only occurs with gtk4 and gtk4-layer-shell