From: Wakko Warner <wakko@animx.eu.org>
To: Domen Puncer <domen@coderock.org>
Cc: Rene Herman <rene.herman@keyaccess.nl>,
Vojtech Pavlik <vojtech@suse.cz>,
Linux Kernel <linux-kernel@vger.kernel.org>,
akpm@osdl.org
Subject: Re: 2.6.12-rc2: Compose key doesn't work
Date: Thu, 26 May 2005 11:45:09 -0400 [thread overview]
Message-ID: <20050526154509.GB9443@animx.eu.org> (raw)
In-Reply-To: <20050526122315.GA3880@nd47.coderock.org>
Domen Puncer wrote:
> Still true for 2.6.12-rc5. Should probably be fixed before final.
I also have a problem with 2.6.12-rcX and ps/2 keyboard. I would say it's
the same key we're talking about. It does not work at the console nor in X
(showkey at the console does not see it). It works with a USB keyboard. My
"compose" is mapped to the menu key beside the right windows key.
I do wish they'd fix it, because I use this key (kinda like another ALT key)
more than my compose key (again, the menu key, not the right win logo key)
> > On 10/04/05 11:52 +0200, Rene Herman wrote:
> > > Hi Vojtech.
> > >
> > > I have mapped my right windows key to "Compose" in X:
> > ...
> > >
> > > This worked fine upto 2.6.11.7, but doesn't under 2.6.12-rc2. The key
> > > doesn't seem to be doing anything anymore: "Compose-'-e" just gets me
> > > "'e" and so on.
> >
> > I can confirm this, right windows key works as scroll up, so it might
> > be related to recent scroll patches.
> >
> > A quick workaround is to:
> > echo -n "0" > /sys/bus/serio/devices/serio1/scroll
> >
> > serio1 being the keyboard here.
> >
> > Btw. is that "-n" really necessary? Had too look at the code to figure
> > out why it's not working :-)
> >
> > >
> > > X is X.org 6.8.1, keyboard is regular PS/2 keyboard, directly connected.
> >
> > Same here.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2005-05-26 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 9:52 Rene Herman
2005-04-14 10:04 ` Domen Puncer
2005-05-26 12:23 ` Domen Puncer
2005-05-26 12:27 ` Vojtech Pavlik
2005-06-03 21:16 ` Wakko Warner
2005-06-03 21:37 ` Dmitry Torokhov
2005-05-26 15:45 ` Wakko Warner [this message]
2005-05-26 15:53 ` Vojtech Pavlik
2005-05-26 16:09 ` Wakko Warner
2005-05-30 14:25 ` Wakko Warner
2005-05-30 14:39 ` Vojtech Pavlik
2005-05-30 23:03 ` Rene Herman
2005-04-14 11:18 ` Kees Bakker
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=20050526154509.GB9443@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=akpm@osdl.org \
--cc=domen@coderock.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
--cc=vojtech@suse.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®