[EDGY] Composed keys not working

[Christophe Dumez]

I'm using edgy and I've just realized that composed keys are not working. I thought the problem came from open office at first but I experienced the same problem with Kate.

If I type <'^'+e> keys I get : "^e" instead of "ê".

I'm using FR-UTF8 with a standard French keyboard.

localhost# locale
LANG=fr_FR.UTF-8
LANGUAGE=fr_FR:fr:en_GB:en
LC_CTYPE=fr_FR.UTF-8
LC_NUMERIC=fr_FR.UTF-8
LC_TIME=fr_FR.UTF-8
LC_COLLATE=fr_FR.UTF-8
LC_MONETARY=fr_FR.UTF-8
LC_MESSAGES=fr_FR.UTF-8
LC_PAPER=fr_FR.UTF-8
LC_NAME=fr_FR.UTF-8
LC_ADDRESS=fr_FR.UTF-8
LC_TELEPHONE=fr_FR.UTF-8
LC_MEASUREMENT=fr_FR.UTF-8
LC_IDENTIFICATION=fr_FR.UTF-8
LC_ALL=

[Mateusz Drożdżyński (matid)]

Thanks for your bug report. Are you sure you have Compose key enabled in Keyboard Preferences? You have to choose a compose key trigger to make it work. If you have any further problem, please make sure to leave a comment here.

[Michael Bienia (geser)]

An other solution is to select a keyboard layout without dead keys.

[Evgeny Kuznetsov (nekr0z)]

I have the like problem: compose key is set up and working in GNOME, but not in Qt applications I run from GNOME. For example, compose key works in Firefox and Gedit, but would not work in Amarok or Psi.

[trollord (trollenlord)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

The issue that you reported is one that should be reproducable with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at [WWW] http://www.ubuntu.com/testing/

[Christophe Dumez (hydr0g3n)]

I'm using latest GUTSY and I don't experience this problem since a long time. This was fixed some time after I reported this bug and I forgot to update my report: sorry. Anyway, you can close it. Thanks for your hard work.