https://bugzilla.redhat.com/show_bug.cgi?id=2081055
--- Comment #14 from fujiwara <tfujiwar(a)redhat.com> ---
(In reply to Daniel from comment #13)
Thank you very much for your contact.
My ibus-ui-gtk3 crashed again today and here is what gdb showed to me:
Thread 1 "ibus-ui-gtk3" received signal SIGSEGV, Segmentation fault.
0x00007f135881d6c9 in g_type_check_instance_is_fundamentally_a
(type_instance=0x31, fundamental_type=0x50) at ../gobject/gtype.c:4091
Downloading 0.03 MB source file
/usr/src/debug/glib2-2.72.2-1.fc36.x86_64/redhat-linux-build/../gobject/
gtype.c
4091 if (!type_instance || !type_instance->g_class)
Is this useful?
That check should be correct in the source code.
To get the root cause, I need to get the stack trace at least beside that SEGV
point.
Seems now you could try gdb with the debug packages and could you try "where"
command to get the stack trace?
% ps -ef | ibus-ui-gtk3
...
% gdb --pid $PID
....
Thread 1 "ibus-ui-gtk3" received signal SIGSEGV, Segmentation fault.
...
(gdb) where
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2081055