LibreOffice on KDE4 seems to cause trouble with ibus input. If I run with KDE integration (by using KDE4 as a desktop environment, or by specifing the environment variable OOO_FORCE_DESKTOP to "kde4", without quotes), ibus keyboard events fail (no keyboard input in the input area, no keyboard shortcuts like CTRL+I). If I run *without* KDE integration (by specifying OOO_FORCE_DESKTOP to "gnome"), I can type normally and use keyboard shortcuts properly. Steps to reproduce: 0. Make sure ibus-daemon is running. 1. Open a terminal and set environment variable OOO_FORCE_DESKTOP to "kde4" (without quotes). 2. Launch LibreOffice from the command line (i.e. lowriter). 3. Try to use the keyboard. Actual Results: Keyboard events are ignored. Expected Results: Keyboard should work Workaround: Set the environment variable OOO_FORCE_DESKTOP to "gnome" (i.e. in $HOME/.xprofile) Package Version(s): Arch Linux libreoffice 3.3.0.4-2 ibus 1.3.9-2 KDE 4.6.0-1
The same happens on openSUSE 11.3 using LibreOffice 3.3.0. It must be noted that if ibus is restarted after LibreOffice is running, keyboard input will be accepted normally.
Linking it with the downstream bugzilla.
Please expand step 0 in the steps to reproduce. I don't even really know what ibus is besides what google says, let alone know how to configure or use it. Also, LibreOffice 3.3.0 is quite old and I think I might have already fixed this problem. Please try with a more recent version.
iBus is an input method used for many Asian languages, but other than that I'm not too sure of the details on how it's implemented. Usually after installing iBus along with some input method (i.e. ibus-hangul) you specify the following environment variables: export XMODIFIERS=@im=ibus export GTK_IM_MODULE="ibus" export QT_IM_MODULE="ibus" One method of doing this is to put the above lines in the file ~/.xprofile ibus-daemon, if it is not automatically launched, can be launched from the command line like so: ibus-daemon -d You should see a tray icon that has a keyboard with a globe in the bottom left corner. Inside a text box of an application (say kwrite) you can "enable" iBus mode by some configurable shortcut like ctrl+space. Assuming ibus-hangul is enabled, if you type "gksrmf" you should see "한글". Regarding the LibreOffice version, at the moment I'm unable to get iBus enabled with 3.4.4, even with OOO_FORCE_DESKTOP set as "gnome." I see only latin characters. I haven't had to type in non-latin recently, so I'm not sure if it's due to the version of KDE I have (KDE 4.8 RC) or due to the newer LibreOffice build. I'll try to check.
Sorry for the delay; I found out what was going wrong. IBus works if my installation of LibreOffice includes Gnome integration (plus KDE integration, since we're talking about using LO in KDE here). It did not work a couple weeks ago since I had only KDE integration installed, but not Gnome. Maybe this is because ibus by default is a gtk3 application? I'm not sure why. In short, iBus WORKS in KDE if libreoffice-gnome is (also) installed.
RESOLVED WORKSFORME per comment 5. Do not hesitate to reopen in case of mistriage.
Installing the libreoffice-gnome on my KDE OpenSuse installation indeed solves the problem. But this has a lot of impact on the looks of LibreOffice. I do not think that this is the right solution for 2 reasons: 1. If the libreoffice-kde package requires the libreoffice-gnome package to work correctly, then the libreoffice-kde should depend on libreoffice-gnome and it should be installed automatically. 2. Installation of libreoffice-gnome should not be necessary in the first place. This is a serious bug! I can not type accented characters! Typing ë or é with the dead keys on my azerty keyboard gives a simple e. My locale is en_GB.UTF-8. Others describe the problem similarly, see e.g.: http://codeverge.com/opensuse.org.help.applications/ibus-don-t-work-in-libreoffice/1919824 https://forums.opensuse.org/showthread.php/497767-Dead-keys-on-LibreOffice
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.