[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#248940: Processed: Re: Bug#248940: xlibs: strange caps lock lag

[Mr. Xu not mailed directly because his mail server has my mail host

retitle 248940 kernel: caps lock key events delayed on Toshiba Libretto L5 laptop [BUG STALLED BECAUSE HERBERT XU WILL NOT PERMIT IT TO BE REASSIGNED TO THE KERNEL; cf. #121335]

On Sat, May 29, 2004 at 02:08:43PM +1000, Herbert Xu wrote:
> reassign 248940 xlibs
> quit
> On Fri, May 28, 2004 at 09:03:04PM -0700, Debian Bug Tracking System wrote:
> > Processing commands for control@bugs.debian.org:
> > 
> > > reassign 248940 kernel
> > Bug#248940: xlibs: caps lock takes time to disengage with xfree86/pc101/dvorak on Toshiba Libretto L5 laptop
> > Bug reassigned from package `xlibs' to `kernel'.
> Please cc <pkg>@packages.debian.org when reassigning.

I did.

  From: Branden Robinson <branden@debian.org>
  To: 248940-submitter@bugs.debian.org, control@bugs.debian.org
  Cc: kernel@packages.debian.org
  Subject: Re: Bug#248940: xlibs: strange caps lock lag
  Date: Fri, 28 May 2004 22:59:58 -0500
  Message-ID: <20040529035958.GS3676@deadbeast.net>

> In the BTS entry I've found no evidence to indicate that this is a kernel
> bug.

No, it's been suggested that it's a hardware bug, and the OS is the
abstraction layer for the hardware.

> In fact, in raw mode it is up to the user-space appliation to keep track
> of things like caps-lock state.

That's not what's being complained about.  Please read the original
report carefully.

> Therefore it is mostly likely to be an X bug a priori.

Raw mode is supposed to expose an abstract keyboard interface unseasoned
by terminal-related concerns, not every defect in the underlying

As the 2.6 kernel likes to tell people, "XFree86 should not access the
hardware directly."  Raw mode is not "accessing the hardware directly".

It's not XFree86's job to work around hardware bugs.  It's the kernel's.

However, I am supremely disinterested in playing your favorite sport
(bug tennis), so I guess this bug will languish until a kernel
person can be troubled to look at it, just like the last Toshiba laptop
keyboard problem you insisted wasn't the kernel's business to deal
with[1][2].  As you said, "There is no way that this patch can be
accepted...Don't bother reassigning it back to me because I will simply
reassign it again with no warning."[3]

Mr. Belmonte, you may want to take your concern directly to the
linux-kernel mailing list, as Mr. Xu is likely, given his past behavior,
to blockade any efforts to resolve this in Debian's kernel.  That his
conception of the meaning of "raw mode" differs from that of the
upstream kernel maintainers does not stop him from imposing his vision
of it on Debian's kernel packages, even after his resignation from the
Debian Project[4].

I apologize for the inconvenience his uncooperative attitude is causing

[1] http://lists.debian.org/debian-x/2003/01/msg00197.html
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=121335
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=121335&msg=39
[4] http://lists.debian.org/debian-boot/2004/05/msg00568.html

G. Branden Robinson                |       The software said it required
Debian GNU/Linux                   |       Windows 3.1 or better, so I
branden@debian.org                 |       installed Linux.
http://people.debian.org/~branden/ |

Attachment: signature.asc
Description: Digital signature

Reply to: