Bug 10426

Summary:	Keyboard initially unresponsive in gvim - IBUS-WARNING.
Product:	Mageia	Reporter:	Edward d'Auvergne <true.bugman>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	true.bugman
Version:	3
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Edward d'Auvergne 2013-06-04 14:50:50 CEST

Description of problem:

When ibus is running:

$ ps -ef  | grep ibus
me    2952     1  0 09:17 ?        00:00:28 /usr/bin/ibus-daemon-real -d -x
me    2964  2952  0 09:17 ?        00:00:00 /usr/libexec/ibus-dconf
me    2968  2952  0 09:17 ?        00:00:06 /usr/libexec/ibus-ui-gtk3
me    2971     1  0 09:17 ?        00:00:00 /usr/libexec/ibus-x11 --kill-daemon
me    3045  2952  0 09:17 ?        00:00:07 /usr/libexec/ibus-engine-simple

and set to the English (US) input method, the Gvim program is initially unresponsive giving the messages:

(gvim:21984): IBUS-WARNING **: Process Key Event failed: Timeout was reached.

(gvim:21984): IBUS-WARNING **: Process Key Event failed: Timeout was reached.

(gvim:21984): IBUS-WARNING **: Process Key Event failed: Timeout was reached.

This has been widely reported:
https://bugzilla.redhat.com/show_bug.cgi?id=673438
https://bugzilla.redhat.com/show_bug.cgi?id=727385
http://code.google.com/p/ibus/issues/detail?id=1249

Running 'gvim -f' instead suppresses the problem.  This appears to be a vim bug with ibus when the program is forked and detached from the shell.  From the last bug report, it seems that if gvim is aliased to 'gvim -f', then the issue disappears.  Until vim finally comes out with a 7.4 release, which could take a few years, I would suggest adding the alias:

alias gvim='gvim -f'

to /etc/profile.d/60alias.sh (or for a workaround for Mageia users this can be added to /etc/profile or ~/.bashrc).


Version-Release number of selected component (if applicable):

vim-7.3


How reproducible:

100%


Steps to Reproduce:
1.  Log in and make sure IBUS is running.
2.  Open vim by typing 'gvim' in the shell.
3.  Start typing.

Reproducible: 

Steps to Reproduce:

Comment 1 Edward d'Auvergne 2013-06-04 14:57:32 CEST

Here are the Ubuntu users complaining about this same bug:

https://bugs.launchpad.net/ubuntu/+source/vim/+bug/856779

Those comments seem to confirm that the vim patch attached to the Fedora report (https://bugzilla.redhat.com/show_bug.cgi?id=727385) also fixes the problem.

Comment 2 Edward d'Auvergne 2014-04-01 11:20:01 CEST

This bug is not present in Mageia 4.

Edward d'Auvergne 2015-02-07 10:48:50 CET

CC: (none) => true.bugman

Comment 3 Marja Van Waes 2015-03-31 16:05:44 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 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 Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD