By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1019

Summary:	[REGRESSION] Compose button does not work in Trinity applications
Product:	TDE	Reporter:	Julius Schwartzenberg <julius.schwartzenberg>
Component:	tdeadmin	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	blocker	CC:	bugwatch, darrella
Priority:	P1
Version:	R14.0.0 [Trinity]
Hardware:	All
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Julius Schwartzenberg 2012-06-04 13:50:33 CDT

This worked properly in Trinity 3.5.13, but does not work with the current nightlies.

To reproduce this, first a compose key needs to be set up. On Ubuntu this can be done either by:
Editing /etc/default/keyboard (or /etc/default/console-setup in older versions) and add "compose:rwin" to the XKBOPTIONS. (This turns the Right Windows key into a compose key, this is the normal position for this key.)

Or in Trinity:
Open System Settings, then Regional & Language, then Keyboard layout, then Xkb Options, check buttons as appropriate (Right Win is usual) to use them as a compose button.

This will enable the use of a compose key to type special characters.

For instance a the sign ½ can be composed by (try it in a GTK/Qt4 app):
press & release: compose
press & release: 1
press & release: 2
A ½ will appear.

Many special characters can be composed in this way like €, ß, ç, ł, á. It is used to type languages like French, German and Polish with a standard US layout.

This will still work in all Qt4 and GTK applications running in Trinity, but not in any Trinity application. It should work as well in Trinity applications, like it used to and works now in other applications.

It seems the compose key is currently completely ignored because after pressing it a regular 1 and 2 appear trying the given example.

Comment 1 Timothy Pearson 2012-06-12 23:59:21 CDT

While I can replicate this bug I am puzzled as to why it is occurring, and what part TDE is playing in the failure.

I know the xkb maps are set correctly, as I can query the maps and get this response:

setxkbmap -query
rules:      evdev
model:      pc104
layout:     us
options:    compose:lwin,grp:ctrl_alt_toggle

Therefore it would seem that TDE (more specifically TQt3) is ignoring the compose event entirely.  This is bolstered by the fact that qtconfig also shows the regression.

Comment 2 Timothy Pearson 2012-06-13 00:39:40 CDT

This might be applicable, though no solution was found:
http://lists-archives.com/kde-devel/16605-compose-key-works-in-xterm-gimp-firefox-etc-but-not-in-any-qt-kde-app.html

Comment 3 Timothy Pearson 2012-06-13 02:50:59 CDT

This bug is fixed in GIT hashes c6db1b3 and 7060490 (Qt3 and TQt3, respectively).  The root cause was input plugins not being loaded due to symbol resolution problems caused by the R14 default change to hidden symbol visibility.

Thanks for reporting!

Comment 4 Julius Schwartzenberg 2012-06-14 05:53:51 CDT

Yep, it works again! :)