Created attachment 1673547 [details]
thread apply all bt full
Description of problem:
I used the compose key in Tilix but didn't type anything and I think switched to another window, and somehow this time gnome-shell crashed completely. ABRT didn't catch it so reporting manually.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 g_utf8_offset_to_pointer (str=str@entry=0x0, offset=0, offset@entry=1) at ../glib/gutf8.c:358
358 s = g_utf8_next_char (s);
I am seeing the same thing but I am not using Tilix. It seems to happen to me regardless of application. (Or at least, specifically, Firefox and Gnome Terminal. I haven't tried more just yet because I actually have other stuff I need to get done today and can't keep crashing my computer.)
Oh also: this did not happen a week or so ago. Something in some update since the beta.
Which key do you have set as Compose?
So, I just did some experimentation: this issue occurs whenever you use the Compose key to print a character in a native Wayland application. X11 applications using XWayland are not affected (including čhrome which I am using to type thiß).
> Which key do you have set as Compose?
Probably the same as https://bugzilla.redhat.com/show_bug.cgi?id=1816588.
Using Caps as compose key, seems to happen only in terminal emulators. Add gnome-terminal to the list.
Happens after you type the 2nd key (when the transformation is happening). I also noticed that in other apps the transformation in electron apps is a bit laggy the first few times on f32.
(In reply to jtagcat from comment #7)
> Using Caps as compose key, seems to happen only in terminal emulators. Add
> gnome-terminal to the list.
It's not just terminal emulators, it's any native wayland apps. But in any case this appears fixed by latest updates.
It indeed has. The bug may be closed.