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): gnome-shell-3.36.0-3.fc32.x86_64 How reproducible: Happened once. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: 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? Right Alt.
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.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.