/usr/share/x11/xkb/symbols/fi: AltGr problem

Troy Korjuslommi tjk at tksoft.com
Tue Aug 21 12:01:00 UTC 2012

I would focus on the input method handling in gnome. 
If you set xim as IM in gnome, things work.
Therefore, the logical starting point for debugging is the default IM
gnome uses. 

I didn't make it clear, but the bugs I filed a couple of years back were
gnome bugs. I am not in front of the right machine right now, but as I
recall the effort didn't produce any results. It might even be that I
never got replies other than "this is not the right place to file a bug.
Please file at XXX," and at XXX I was told to file at YYY. I might be
mistaken, since it's a while back, but I do remember feeling frustrated
at the process.


On Mon, 2012-08-20 at 17:08 +0300, Martin-Éric Racine wrote:
> 2012/8/20 Troy Korjuslommi <tjk at tksoft.com>:
> > I actually filed the same bug a couple of years ago, as I recall. The
> > behavior is the same, so no change seems to have taken place.
> >
> > Some debugging notes first. Always try X11 apps first, to see if the
> > problem is with X11. If X11 works, then the problem is with something on
> > top of X11, usually GTK or KDE.
> >
> > The problem with X11 can be with a number of things such as the key
> > symbols .h file, the Compose file, or the actual file for the specific
> > keyboard.
> >
> > In this case, I tried entering U+0111 (Altgr-§-d) with xkb-data version
> > 1.8-2 on debian stable, and xkb-data version 2.5-1ubuntu1.3 on the
> > latest desktop ubuntu. I got the same results on both.
> >
> > If you try X11 (xterm, xev) everything works. Same for KDE (kaffeine et
> > al).
> >
> > If you open gnome-terminal or some other gnome app, you will first get
> > only a plain d. To rule out font problems, paste § to the gnome app. It
> > should show up just fine.
> >
> > The solution is to change to the XIM input method. You can do this from
> > the right mouse button for some apps, but for others you have to fiddle
> > with the input settings globally. Once XIM is set as the input method,
> > you get your Islandic đ.
> >
> > The behavior is obviously still wrong. GTK apps should work without the
> > users having to fiddle with their input method settings. All input
> > methods (at least the default one) should understand all correct input.
> > However, I hope the above demonstrated conclusively that the problem is
> > not with X11 or its configurations. The problem lies with input methods
> > other than XIM when using GTK.
> I'm begining to wonder if GTK3 or GNOME3 maintain their own
> (presumably outdated) copies of the xkb-data keymaps? At least, what
> is shown whenever selecting "Show keyboard map" from the keyboard
> applet in gnome-shell doesn't quite match what I'm supposed to be
> using (fi-Kotoistus keymap), which might explain other problems such
> as this unability to generate D-slash or L-slash using only compose
> sequences from the Kotoistus keymap within GNOME applications.
> Martin-Éric

More information about the pkg-gnome-maintainers mailing list