Fedora Account System
Red Hat Associate
Red Hat Customer
When trying to input with ibus in KDE inside GTK apps. Input sometimes seems to stop working or cause the application to crash. Reproducible: Always Steps to Reproduce: 1. zenity --entry 2. input Japanese text 3. input into gtk4-demo Actual Results: 2. zenity sometimes crashes 3. Committing text may cause the demo app to segfault. (Somehow I cannot input into gtk4-demo-application.) Expected Results: Input to work normally (and no crashes). Additional Information: I can attach a backtrace later, though this shouldn't hard to reproduce. Akira Tagoh also mentioned similar problems to me last week.
This also happens in Rawhide KDE. I think this is potential F45 Blocker material.
(In reply to Jens Petersen from comment #0) > 3. Committing text may cause the demo app to segfault. I don't see any SEGV. > (Somehow I cannot input into gtk4-demo-application.) I see the input does not work in some cases in case I start IBus with `ibus start` command. I thought KDE Plamsa 6.7 now supports to run IBus command directly, i.e. `ibus start --type wayland` but actually I see the input problems and IBus needs to be run in the KDE component. The workaround is to run IBus with systemsetting or `ibus start --type kde-wayland` for my issue. I hope your issue is same with me. > I think this is potential F45 Blocker material. I don't think so since I have a plan to fix my issue in the beta release. I can make the next release once ibus-1.5.35~beta2-2.fc45 and cldr-emoji-annotation-49~alpha2-1.fc45 are moved to the stable repo.
I agree this is possibly a blocker. If we fix it soon it's academic I guess, but in future, if a bug is blocker-worthy it's usually good to propose/track it as a blocker even if we think we'll fix it before any freezes / deadlines.
AGREED AcceptedFinalFreezeException Discussed at the 2026-09-14 (blocker / freeze exception) review meeting: This is a significant problem for input method users that may affect live sessions and thus cannot be entirely fixed with a post-release update. https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-09-14/f45-blocker-review.2026-09-14-16.01.log.txt
Strange I can no longer reproduce my problem: slightly puzzled, but it seems okay to me today. Even retesting Fedora-KDE-Desktop-Live-45-20260910.n.0.x86_64.iso seems okay, hm and further Fedora-KDE-Desktop-Live-45-20260909.n.0.x86_64.iso :shrug: Unfortunately I didn't leave a lot of version details above in my original description. I will come back if I should find anything more, but perhaps this can be closed.
I wonder you might use an old IBus version which had a SEGV issue with GTK4 and it has been fixed with ibus-1.5.35~beta1-1.fc45 in case your issue is different from mine.
(In reply to fujiwara from comment #6) > I wonder you might use an old IBus version which had a SEGV issue with GTK4 > and it has been fixed with ibus-1.5.35~beta1-1.fc45 in case your issue is > different from mine. Yeah it is possible that I somehow messed up. (I think ibus restart should be a different problem? - ibus worked fine in KDE apps anyway.) Anyway I suggest we close this for now - I don't think anyone is still seeing this?
It's just a your test failure. *** This bug has been marked as a duplicate of bug 2512529 ***