us intl keymap not working in kde

Bug #162407 reported by Martin Adler
18
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Invalid
High
Harald Sitter

Bug Description

Binary package hint: kdebase

Switching from gusty to hardy destroyed something in kdebase. It could have been the switch to xorg 1.4 aswell.

Symptoms are similar to #69045. That means, that there seam to be no dead key listener to create umlauts or accents on letters. For example, to make a umlaut A, you would push double qoutes and A, but my state is that hitting double qoutes produces this ¨. This happend to me before but only if I hit double qoutes twice. So it is not waiting for a space to form the normal double qoutes either.

The keys work normally in gtk apps running in the KDE session (as for example firefox).

Revision history for this message
Martin Adler (martin-adler) wrote :

This has something to do with qt3 I believe since entering these characters produces the following in .xsession-errors:

/usr/lib/qt3/plugins/inputmethods/libqimsw-multi.so: undefined symbol: _ZN13QInputContext11sendIMEventEN6QEvent4TypeERK7QStringii
/usr/lib/qt3/plugins/inputmethods/libqsimple.so: undefined symbol: _ZN13QInputContext14x11FilterEventEP7QWidgetP7_XEvent
/usr/lib/qt3/plugins/inputmethods/libqxim.so: undefined symbol: _ZN13QInputContext11filterEventEPK6QEvent
/usr/lib/qt3/plugins/inputmethods/libqscim.so: undefined symbol: _ZNK13QInputContext4fontEv
/usr/lib/qt3/plugins/inputmethods/libqimsw-multi.so: undefined symbol: _ZN13QInputContext11sendIMEventEN6QEvent4TypeERK7QStringii
/usr/lib/qt3/plugins/inputmethods/libqsimple.so: undefined symbol: _ZN13QInputContext14x11FilterEventEP7QWidgetP7_XEvent
/usr/lib/qt3/plugins/inputmethods/libqxim.so: undefined symbol: _ZN13QInputContext11filterEventEPK6QEvent
/usr/lib/qt3/plugins/inputmethods/libqscim.so: undefined symbol: _ZNK13QInputContext4fontEv
/usr/lib/qt3/plugins/inputmethods/libqimsw-multi.so: undefined symbol: _ZN13QInputContext11sendIMEventEN6QEvent4TypeERK7QStringii
/usr/lib/qt3/plugins/inputmethods/libqsimple.so: undefined symbol: _ZN13QInputContext14x11FilterEventEP7QWidgetP7_XEvent
/usr/lib/qt3/plugins/inputmethods/libqxim.so: undefined symbol: _ZN13QInputContext11filterEventEPK6QEvent
/usr/lib/qt3/plugins/inputmethods/libqscim.so: undefined symbol: _ZNK13QInputContext4fontEv
/usr/lib/qt3/plugins/inputmethods/libqimsw-multi.so: undefined symbol: _ZN13QInputContext11sendIMEventEN6QEvent4TypeERK7QStringii
/usr/lib/qt3/plugins/inputmethods/libqsimple.so: undefined symbol: _ZN13QInputContext14x11FilterEventEP7QWidgetP7_XEvent
/usr/lib/qt3/plugins/inputmethods/libqxim.so: undefined symbol: _ZN13QInputContext11filterEventEPK6QEvent
/usr/lib/qt3/plugins/inputmethods/libqscim.so: undefined symbol: _ZNK13QInputContext4fontEv

Revision history for this message
Martin Adler (martin-adler) wrote :

Above errors has nothing to do with it. They appear with every program started and are related to another bug.

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

I have the problem, even in GTK apps. Running an updated Hardy a5.

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Confirming this as high.

Changed in kdebase:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
marko daniel (marko-markodaniel) wrote :

This same problem has recently cropped up on an Intrepid system, where perfectly working deadkeys disappeared. System settings are for GB INTL layout.

Revision history for this message
Harald Sitter (apachelogger) wrote :

The issue on Intrepid was most likely caused by a kbd profile breakage in Xorg.

Is the original issue still a problem on Hardy? If so, which KDE version.
If KDE 4 -> please try with 4.1.2 and/or Intrepid Beta (livecd for example).

Changed in kdebase:
status: Confirmed → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdebase:
status: Incomplete → Invalid
Revision history for this message
nick (nickspacca) wrote :

Hi, I report the same problem on Intrepid system (upgraded from Hardy).
I normally use us-intl layout on both gnome et kde environment. Previously, everything was working fine on Hardy.
The problem is also present in all the applications from kde 3.5.10 and 4.1.3.

Revision history for this message
nick (nickspacca) wrote :

Hi, I still have the same problem as presented before, also after upgrading to Jaunty. If you need more info, please tell me...

Changed in kdebase (Ubuntu):
status: Invalid → New
Revision history for this message
Diego Schulz (dschulzg) wrote :

any news on this issue?

I'm having this problem using KDE 4.3.1

Revision history for this message
Diego Schulz (dschulzg) wrote :

still having this problem in 4.3.2

Revision history for this message
Harald Sitter (apachelogger) wrote :

So I went to systemsettings -> regional stuff -> keyboard layout and set the layout to us intl (command: setxkbmap -model pc104 -layout us -variant intl).
Then I go to the address bar in Konqueror -> press " -> press a -> and ä comes out.

So, now I am wondering. Does this issue still affect Kubuntu 9.10? If so, how exactly would I go about reproducing it?

Some general thoughts: it might still not be working on an upgraded 9.10 if there is some issue in a configuration file, on the other hand the issue might also be related to the keyboard hardware, which I find very unlikely but worth mentioning :)

Changed in kdebase (Ubuntu):
assignee: nobody → Harald Sitter (apachelogger)
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!

Changed in kdebase (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.