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

Bug#142569: [lkcl@samba-tng.org: interaction between kernel and xfree86 v 4]

hi there herbet,

count me in as a guinea-pig!

i can manage recompiling kernels if someone would like
to send me a patch.

... what i can't manage [by myself] is recompiling Xfree86 
except possibly under strict supervision and by someone
prepared to wield a Big Stick.

so yeh, send me some patches, instructions, place some
big files on a web site somewhere for me to pick up
(i only have a 56k dialup at home, evenings).


p.s. i'm using linux kernel 2.5.3 ... um ... does that
make a difference?

On Tue, Mar 11, 2003 at 06:54:32PM +1100, Herbert Xu wrote:

> On Tue, Mar 11, 2003 at 12:14:07AM +0000, Luke Kenneth Casson Leighton wrote:
> > 
> > it was suggested to me after conversations with branden that
> > i relate to you a story that may be of assistance to you.
> As I have stated before, all we need to resolve #142569/#156563 is for
> someone who can readily reproduce the problem to tap into the kernel
> driver to produce a list of events, and then do the same for the X server.
> Now comparing the two should make the problem obvious.
> Unfortunately it seems that no one has been willing to do that as of yet.
> Until we have some hard facts, hypothesising is not going to help.
> BTW Branden, you should disconnect #121335 from the rest.  The issue
> of dupliate release events have been worked around in 2.4.21pre.  It
> is also said that 2.5's new software repeat mechanism also prevents it
> from happening.
> -- 
> Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
> Email:  Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

this message is private, confidential, and is intented for
the specified recipients only.  if you received in error,
altered, deleted, modified, destroyed or interfered with
the contents of this message, in whole or in part, please
inform the sender (that's me), immediately.

if you, the recipient, reply to this message, and do not
then receive a response, please consider your reply to have
been lost or deliberately destroyed: i *always* acknowledge
personal email received.  please therefore take appropriate
action and use appropriate protocols to ensure effective

thank you.

Reply to: