Xubuntu 20.04 Geany 1.37.1, GTK 3.24.20, GLib 2.64.3 ``` (gdb) run Starting program: /usr/local/bin/geany [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff548c700 (LWP 80774)] [New Thread 0x7ffff4be7700 (LWP 80775)] [New Thread 0x7fffecc9e700 (LWP 80776)] [New Thread 0x7fffe7fff700 (LWP 80777)] [Detaching after fork from child process 80778] [Thread 0x7fffe7fff700 (LWP 80777) exited]
(geany:80770): GLib-GObject-CRITICAL **: 08:43:38.441: g_object_get_data: assertion 'G_IS_OBJECT (object)' failed
Thread 1 "geany" received signal SIGSEGV, Segmentation fault. 0x00007fffedc844e5 in gsdlg_option (label=0x555556413338 "DICT", value=0x555556413308 "dict", key=0x555556412e18 "proto", dlg=0x555556403ed0) at gsdlg.c:479 479 cw=g_object_get_data(G_OBJECT(hbox), DataKey); ``` For test use [complex-dialog.lua](https://github.com/geany/geany-plugins/blob/master/geanylua/examples/dialogs...)
Also I tried GTK2-version (Geany 1.36, GTK 2.24.32 and GLib 2.64.3): works fine.
The search in gsdlg.c looks fragile, its possible GTK3 changed the widget hierarchy so it doesn't return what was expected.
@Skif-off When I use geany/geany-plugins from the Ubuntu 21.04 repository, I get the segfault you describe. However, when I build geany/geany-plugins from git, I do not. So the problem is probably already fixed.
@xiota Thanks for checking. I have tried too and I think I will wait v1.38 and close this issue (if Geany team members will not close it).
Not reproduced with 1.38.
Closed #1027.
github-comments@lists.geany.org