Crash when switching to Design Mode on xorg
In Builder 3.34.1 (on Solus 4, Xorg), opening an .ui file from the sample Python template and switching to Design Mode crashes the whole Builder, with the log below:
11:47:00.8608 dzl-signal-group[ 16181]: CRITICAL: dzl_signal_group_connect_full: assertion 'g_signal_parse_name (detailed_signal, self->target_type, &signal_id, &signal_detail, TRUE) != 0' failed
11:47:00.8609 dzl-signal-group[ 16181]: CRITICAL: dzl_signal_group_connect_full: assertion 'g_signal_parse_name (detailed_signal, self->target_type, &signal_id, &signal_detail, TRUE) != 0' failed
11:47:00.8609 dzl-signal-group[ 16181]: CRITICAL: dzl_signal_group_connect_full: assertion 'g_signal_parse_name (detailed_signal, self->target_type, &signal_id, &signal_detail, TRUE) != 0' failed
11:47:00.8609 dzl-signal-group[ 16181]: CRITICAL: dzl_signal_group_connect_full: assertion 'g_signal_parse_name (detailed_signal, self->target_type, &signal_id, &signal_detail, TRUE) != 0' failed
(gnome-builder:16181): Gdk-WARNING **: 11:47:01.747: gdkwindow-x11.c:5633 drawable is not a native X11 window
(gnome-builder:16181): Gdk-ERROR **: 11:47:01.748: The program 'gnome-builder' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 134176 error_code 3 request_code 20 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
fish: 'gnome-builder' terminated by signal SIGTRAP (Verfolgungs- oder Haltepunkt erreicht)