From: Rene Herman <rene.herman@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Indan Zupancic <indan@nul.nu>,
teresa@kvitka.net, Andi Kleen <andi@firstfloor.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
CK Mailinglist <ck@vds.kolivas.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dmitry.torokhov@gmail.com, dtor@mail.ru
Subject: Re: Linux Kernel cfs scheduler and xorg kbd
Date: Mon, 06 Aug 2007 15:10:23 +0200 [thread overview]
Message-ID: <46B71DBF.7000000@gmail.com> (raw)
In-Reply-To: <20070806071200.GC5359@elte.hu>
On 08/06/2007 09:12 AM, Ingo Molnar wrote:
> * Indan Zupancic <indan@nul.nu> wrote:
>
>> All right, how would you debug it? Give us some insight in how to
>> solve hard to trigger, happens at most only a few times a day,
>> annoying input bug? I thought the mouse warping was fixed after 23-rc1
>> and that input locking patch, but alas, the third day it happened
>> again.
>
> i've got no idea how to debug such input bugs best, but, as a starting
> point, i've Cc:-ed the current maintainer of the input subsystem :-)
FWIW, I haven't experienced my "stuck delete" key anymore -- "since using
CFS v19.1", but that might very well just be coincedence. If anyone
wants/needs me to, I'll try to debug it, but for now I seem to be fine again.
Now all I need to know is whether or not moving thunderbird's windows around
is expected to leave such an enormous non-repainting visual trail on the
screen...
I believe I'm concluding that I'm not all together fond of the "new" modular
X.org.
Rene.
next prev parent reply other threads:[~2007-08-06 13:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 20:25 Linux Kernel cfs scheduler and xorg kbd <::.. Teresa_II ..::>
2007-07-30 22:49 ` Michal Piotrowski
2007-08-01 6:48 ` Ingo Molnar
2007-08-01 11:31 ` Andi Kleen
2007-08-01 11:01 ` Rene Herman
2007-08-01 12:34 ` Indan Zupancic
2007-08-01 12:50 ` Rene Herman
2007-08-01 13:07 ` Indan Zupancic
2007-08-01 13:26 ` Rene Herman
2007-08-01 13:33 ` <:::.. TeresaII ..:::>
2007-08-01 13:58 ` Rene Herman
2007-08-01 14:44 ` <::.. Teresa_II ..::>
2007-08-01 15:00 ` [ck] " Matthew Hawkins
2007-08-01 15:53 ` <::.. Teresa_II ..::>
2007-08-02 7:11 ` Sébastien Dugué
2007-08-02 12:22 ` Rene Herman
2007-08-02 13:18 ` Indan Zupancic
2007-08-01 15:06 ` Indan Zupancic
2007-08-01 15:09 ` Ingo Molnar
2007-08-01 15:13 ` Rene Herman
2007-08-01 15:20 ` Ingo Molnar
2007-08-01 15:19 ` Rene Herman
2007-08-01 15:26 ` Indan Zupancic
2007-08-06 7:12 ` Ingo Molnar
2007-08-06 13:10 ` Rene Herman [this message]
2007-08-06 15:19 ` Indan Zupancic
2007-08-06 17:46 ` Rene Herman
2007-08-06 18:26 ` OT: enabling Xcomposite [was: Linux Kernel cfs scheduler and xorg kbd] Indan Zupancic
2007-08-07 4:40 ` Linux Kernel cfs scheduler and xorg kbd Kyle Moffett
2007-08-07 6:05 ` Arjan van de Ven
2007-08-07 10:17 ` Indan Zupancic
2007-08-07 13:15 ` Rene Herman
2007-08-09 21:14 ` Mark Lord
2007-07-31 11:18 ` [ck] " <::.. Teresa_II ..::>
2007-07-31 11:42 ` <::.. Teresa_II ..::>
2007-07-31 14:27 ` Ingo Molnar
2007-07-31 16:39 ` <::.. Teresa_II ..::>
2007-07-31 15:06 ` Rene Herman
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=46B71DBF.7000000@gmail.com \
--to=rene.herman@gmail.com \
--cc=andi@firstfloor.org \
--cc=ck@vds.kolivas.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@mail.ru \
--cc=indan@nul.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
--cc=teresa@kvitka.net \
/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.