Bug 226556

Summary: composed special characters fail in kde applications
Product: [I don't know] kde Reporter: Delphine Ménard <notafishz>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Delphine Ménard 2010-02-12 15:55:14 UTC 
Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    Ubuntu Packages

Informations about the system: 
*Kubuntu Karmic
*Regional and languages settings set to French
*Keyboard map set to French (setxkbmap -model pc104 -layout fr -variant )
*Compose key enabled (left window key)


Problem: Special characters that require to be combined (with two keys on the keyboard but NOT with the compose key) do not work anymore. This happens ONLY in KDE applications.

Steps to reproduce:
* Open KDE app (Konversation, Kopete, Kate, Korganizer...)
* Type ^+e 
* obtain ^e 

Expected behaviour:
* The combination of key should give ê

Note: Settings unchanged since using KDE SC 4.4 beta. Last update through kubuntu ppa broke the behaviour.

Non KDE apps work fine (Firefox, Thunderbird, Open Office etc.)

There must be a setting KDE took over and is forcing onto the apps that depend on it, I guess. Thanks for your help.
Comment 1 Andrew Crouthamel 2018-11-02 23:03:22 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-16 05:34:13 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Nate Graham 2020-09-28 23:30:47 UTC 
No response; assuming it was fixed since then. Works for me FWIW.