Bug 180506

Summary: Deadkeys not working in Qt/KDE applications in GNOME
Product: [Frameworks and Libraries] kdelibs Reporter: Flóki Pálsson <flokip>
Component: qtAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED DOWNSTREAM    
Severity: normal CC: cfeck, hans, kevin.kofler, rdieter
Priority: NOR    
Version: 4.1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Flóki Pálsson 2009-01-12 22:44:38 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Fedora RPMs

Description of problem:
IS keyboard in KDE applications is not working.
Icelandic characters áéóú are not possible to input with keyboard in gnome.


Version-Release number of selected component (if applicable):
qt-4.4.3-8.fc10.x86_64

How reproducible:
always

Steps to Reproduce:
1.
log in use gnome and iceland keyboard
2.
start KWrite  type á 
3.


Actual results:
´a

Expected results:
á

Additional info:
This works in FC9,  and when selecting KDE session when login inn after setting
keyboard in KDE.
It is ok in unbuntu 8.10
See
https://bugzilla.redhat.com/show_bug.cgi?id=468590
Comment 1 Hans Deragon 2009-01-31 11:42:07 UTC
I confirm this problem with USA Intl keyboard layout and Ubuntu 08.04.  None of the accented characters work with KDE/QT applications.
Comment 2 Flóki Pálsson 2009-02-08 17:13:29 UTC
This is also in fedora Fc11 alfa.
qt-4.4.3-16.fc11.x86_64 
Comment 3 Flóki Pálsson 2009-04-19 14:44:46 UTC
Now ok in F11 
qt-4.5.0-14.fc10.x86_64
but not in F10
qt-4.5.0-14.fc11.x86_64
Comment 4 Hans Deragon 2009-06-08 01:29:04 UTC
I still have the problem, but following recommendations on the net, if I run the application (Tora) as root, the problem disappears, suggesting some permission issues.

Also, not all Qt based application have this problem.  kword and kspread work fine.  Tora which I downloaded individually from its website, uses Qt 4.4.0.  I believe that kword and kspread use Qt 3.x; these applications come from Ubuntu's repository.
Comment 5 Kevin Kofler 2009-06-10 22:56:43 UTC
According to the Fedora bug report, this is still reproducible on F11 with SCIM. Note that F11 uses I-Bus by default, not SCIM, this may be why it looks "fixed" for the reporter (note that the Qt build is the exact same one, just the disttag and the buildroot it got compiled in are different).
Comment 6 Kevin Kofler 2009-06-10 22:59:23 UTC
Oh, by the way, the KDE live CD doesn't install any input methods at all.

Flóki Pálsson, what input methods, if any, do/did you have installed on F10? On F11?

(We strongly suspect this is a bug with SCIM, as removing SCIM is reported to fix this. That's why I'm focusing on input methods. There's also a bug filed on the SCIM SourceForge project, getting little to no activity.)
Comment 7 Kevin Kofler 2009-06-10 23:01:00 UTC
Oops, another addendum: The GNOME live CD installs SCIM by default on F10, I-Bus on F11. AFAIK, the installer DVD does the same, at least if "Input Methods" is checked.
Comment 8 Christoph Feck 2009-12-09 23:50:17 UTC
If this is a Qt issue, can you clarify what the exact bug is? Does it happen with Qt 4.6? If yes, please use http://bugreports.qt.nokia.com/ to report the bug.
Comment 9 Flóki Pálsson 2009-12-10 20:07:31 UTC
 Comment #6
>Flóki Pálsson, what input methods, if any
No special input method. Just select Icelandic keyboard during install.

>, do/did you have installed on F10? On
>F11  
I am not sure if I understand the question.
This was always a clean install off gnome version off fedora.
I can not see this problem in F12.
This is ok in F11 and F10 now ( as far I remember ) for me.
I installed fore example Quanta where the problem was.
( late is better than never )
Comment 10 Kevin Kofler 2009-12-11 00:29:03 UTC
As I explained, the GNOME spin of Fedora installs input methods by default. Up to F10, this was SCIM, in F11 and newer it's I-Bus. Only SCIM triggers this bug. So this is effectively solved downstream now by switching away from SCIM in Fedora. The SCIM bug probably needs to be fixed in SCIM. It's not a KDE issue in any case (it's either Qt's or SCIM's fault), so I'm closing this bug.