From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: GTK+, disabled XKB a.k.a. why keymaps/ModeSwitch don't work well in GPE or XFCE
Date: Wed, 13 Jan 2010 09:25:45 +0100 [thread overview]
Message-ID: <hik028$l2q$1@ger.gmane.org> (raw)
In-Reply-To: <1263337290.13906.27.camel@utx.utx.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 13-01-10 00:01, Stanislav Brabec wrote:
> Hallo.
>
> We just spent some time by debugging of an annoying bug - broken
> Mode_Switch key in GPE and XFCE.
>
> Surprisingly, the problem affects only GTK+ applications and it is
> caused by --disable-xkb configure options in OE gtk+ recipes(*).
>
> It
> - made impossible to upgrade to the new version of kdrive on Zaurus
> - now makes impossible to upgrade to Xorg on Zaurus
> - causes keyboard breakage on Always Innovating Touch Book.
> http://bugzilla.alwaysinnovating.com/show_bug.cgi?id=41
>
> So there is a question: Why XKB is disabled in OE GTK+? Does it have any
> reason or it is a relict from the ancient age of kdrive based
> systems(**)? If it is true, I propose a patch to remove --disable-xkb
> not only from gtk+, but also all xorg-app and xorg-lib,
I vote for this option.
> or at least move
> this option to distribution configuration.
I think we can put that burden on xkb haters (if they exist).
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLTYOJMkyGM64RGpERAij5AKCiFh6ugEWa2s9OuaJTQok9EDg6IwCeK6aW
OuAdysqxQeP0SZxLFcbDMxw=
=Sqtj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-13 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 23:01 GTK+, disabled XKB a.k.a. why keymaps/ModeSwitch don't work well in GPE or XFCE Stanislav Brabec
2010-01-13 8:25 ` Koen Kooi [this message]
2010-01-13 19:57 ` Phil Blundell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hik028$l2q$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.