Re: Possible input problem with xfree86_4.2.0-0pre1v1 and sawfish-gnome
- To: David Stanaway <firstname.lastname@example.org>
- Cc: email@example.com, firstname.lastname@example.org
- Subject: Re: Possible input problem with xfree86_4.2.0-0pre1v1 and sawfish-gnome
- From: Michel Dänzer <email@example.com>
- Date: 19 Jun 2002 00:09:36 +0200
- Message-id: <1024438176.1254.263.camel@tibook>
- In-reply-to: <1024436147.9395.36.camel@ciderbox>
- References: <1024401121.9198.10.camel@ciderbox> <1024413372.3690.1279.camel@tibook> <1024436147.9395.36.camel@ciderbox>
On Tue, 2002-06-18 at 23:35, David Stanaway wrote:
> On Tue, 2002-06-18 at 10:16, Michel Dänzer wrote:
> > On Tue, 2002-06-18 at 13:52, David Stanaway wrote:
> > > Here is the running problem that I was having:
> > >
> > > There are some regular but intermitant problems with registering mouse
> > > clicks, and some key combinations yeild odd results. All revolving
> > > around change of focus.
> > I've been seeing this on and off for quite some time, but of course I've
> > been running a 4.2 server for a long time as well for its Radeon
> > support. Can you try with a 4.1 server to see if it makes a difference?
> > The problem being that it seems to occur non-deterministically, so one
> > can never be sure it's actually not there...
> I was running 4.1 before and I had no problems. I was also running your
> bare bones 4.2 binaries as well (However, I used the ati driver as per
> your xf86config) and I don't recall any problems.
Well, I've seen the problem with my binaries.
Maybe the server is just a red herring anyway, as I also experienced it
with sawfish. It would be great if anyone could determine a pattern
behind this or even better the cause. :/
One other suspicion I'd like to mention though is sleep. I don't think
I've seen the problems with this new TiBook yet, which I can't put to
> When I was running your binaries I only had Indirect rendering for glx, now when I am am
> using the full package I am using the r128 driver (I couldn't see a
> manpage for ati, and I was puzzled why it worked.) and I have Direct
> OpenGL vendor string: VA Linux Systems, Inc.
> OpenGL renderer string: Mesa DRI Rage128 20010405 M3 AGP 1x
> OpenGL version string: 1.2 Mesa 3.4.2
> I saw from another post that direct rendering is unstable with the M3.
> I did get a system crash last night when changing the display settings
> in quake2 (To use lower detail, as the framerate slowed dramatically
> when an explosion was visible).
> Could this be related? Or is it a completely seperate issue.
The latter. Direct rendering is unrelated to input, and I don't have DRI
enabled in my normal session, where I experienced the problems.
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com