Bug 673047
Summary: | [abrt] ibus-1.3.9-2.fc14: ibus_xkb_get_current_layout: Process /usr/libexec/ibus-xkb was killed by signal 6 (SIGABRT) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | kang.junghan | ||||
Component: | ibus | Assignee: | fujiwara <tfujiwar> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 14 | CC: | david, i18n-bugs, shawn.p.huang, tfujiwar | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:f2ce5b80424e0f0c58006ba6bedb2d812d6a0c46 | ||||||
Fixed In Version: | ibus-1.3.9-3.fc14 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-03-14 05:39:31 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
kang.junghan
2011-01-27 07:25:34 UTC
Created attachment 475544 [details]
File: backtrace
kang.junghan: Do you see any warnings or errors when you run ibus-xkb on a terminal by manual? % /usr/libexec/ibus-xkb --get layout: us model: option: Maybe I guess your system might not support XKB. kang.junghan: Do you have any updates? Package: ibus-1.3.9-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start GNOME in a thinlinc (vnc) session As in comment 4, this happens in a VNC session. [david@peregrine ~]$ /usr/libexec/ibus-xkb --get ** (ibus-xkb:5657): WARNING **: Could not get state ** ERROR:xkblib.c:245:ibus_xkb_get_current_layout: assertion failed: (default_layouts != NULL) Aborted (core dumped) According to a Thinlinc developer, the crash happens because their VNC server is combiled without XKB-support. It would be nice for ibus-xkb to handle this case more gracefully than a SIGABRT. (In reply to comment #5) > As in comment 4, this happens in a VNC session. > > [david@peregrine ~]$ /usr/libexec/ibus-xkb --get > > ** (ibus-xkb:5657): WARNING **: Could not get state > ** > ERROR:xkblib.c:245:ibus_xkb_get_current_layout: assertion failed: > (default_layouts != NULL) > Aborted (core dumped) Thanks for the report. It seems the VNC session doesn't use the core keyboard and XkbGetState (xdisplay, XkbUseCoreKbd, &state) was failed. I'll remove it. Also could you check if the _XKB_RULES_NAMES atom is available on your VNC session? % xlsatoms | grep _XKB_RULES_NAMES 262 _XKB_RULES_NAMES Thanks! The atom doesn't seem to be present: [david@peregrine ~]$ xlsatoms | grep _XKB_RULES_NAMES [david@peregrine ~]$ (In reply to comment #8) Oh, it seems the session doesn't support XKB completely. Thanks for your info. ibus-1.3.99.20110228-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/ibus-1.3.99.20110228-2.fc15 ibus-1.3.9-3.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/ibus-1.3.9-3.fc14 ibus-1.3.99.20110228-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. ibus-1.3.9-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |