Summary: | x11-libs/gtk+:3: app-office/gnucash segfaults on keyboard input (GTK_IM_MODULE, gdk_window_has_impl) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cyp <cyp561> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED WONTFIX | ||
Severity: | major | CC: | titanofold, tsmksubc |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://gitlab.gnome.org/GNOME/gtk/issues/61 | ||
See Also: | https://bugs.gnucash.org/show_bug.cgi?id=795014 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Cyp
2018-03-13 15:03:12 UTC
Based on the external links, my first question would be - what input method do you use? Like any ibus stuff going or, or just your usual latin? Also would be good to know what version of wxGTK:3.0-gtk3 you have installed I think it's the normal input method, whatever that is. I don't have ibus installed. I have a .XCompose file, but renaming it and starting gnucash didn't make a difference. Doing “echo $GTK_IM_MODULE” gives “xim”. Installed x11-libs/wxGTK:3.0-gtk3 is 3.0.3-r300, which is currently the only available version. I tried recompiling it in case – didn't help, though. (In reply to Cyp from comment #3) > Doing “echo $GTK_IM_MODULE” gives “xim”. Running “GTK_IM_MODULE='' gnucash” seems to suppress the crash. grepping /etc finds /etc/env.d/99local:export GTK_IM_MODULE=xim I think that might have had something to do with fixing the compose key in openoffice, don't remember. Anything I've been able to find regarding xim indicates that it was already obsolete years ago[1]. You could give app-i18n/uim a go, and see how that works out for you. As I understand it, uim supports the .XCompose file. [1]: https://unix.stackexchange.com/questions/260601/understanding-setting-up-different-input-methods You shouldn't need any of that with gtk3. I believe this is the default method, in lack of any overrides via the envvar (and almost certainly is, as the new emoji stuff comes by default via there): https://developer.gnome.org/gtk3/stable/GtkIMContextSimple.html I have been experiencing the same issue. My tests have confirmed, that it is caused by this setting: > export GTK_IM_MODULE=xim The reason I have this setting, is to allow complex compose key sequences in gtk+:2 applications. Without them the official firefox binary would warn: > [...] The max number of sequences is 7: <Multi_key> <u> <u> <KP_2> <KP_7> <KP_1> <KP_3> <space> : "✓" U2713 # CHECK MARK See also https://wiki.neo-layout.org/ticket/100 (german). I can also confirm that installing app-i18n/uim and setting > export GTK_IM_MODULE=uim is a suitable work-around. It allows the usage of long compose sequences and it does not cause gnucash to crash. It is also true, that the long compose sequences from .XCompose work out-of-the-box in gtk+:3 applications. For the time being we still have to content with some gtk+:2 applications though. Can somebody please add https://gitlab.gnome.org/GNOME/gtk/issues/61 as upstream URL. It gets easily overlooked in the report above. Upstream has determined the bug lies in GTK. I wouldn't expect any solution anytime soon, if ever. The "fix" is to stop using xim. (In reply to Mart Raudsepp from comment #9) > I wouldn't expect any solution anytime soon, if ever. The "fix" is to stop > using xim. This is a good enough reason to close the bug. Since first reporting, xim has just gotten even more obsolete. Use app-i18n/uim. |