Subject: Re: and yet more weirdness with XFree86-4.5.0 on NetBSD/sparc
To: NetBSD/sparc Discussion List <port-sparc@NetBSD.org>
From: Greg A. Woods <firstname.lastname@example.org>
Date: 12/06/2006 12:05:43
Content-Type: text/plain; charset=US-ASCII
At Wed, 6 Dec 2006 11:42:24 +0000,
Julian Coleman wrote:
> > The next thing I noticed was that the keyboard focus wasn't following
> > the mouse cursor as it normally should with ctwm.
> I have noticed both these on sparc and sparc64 when using Xsun. When
> using XFree86, these problems aren't there. (This bit me again recently
> on sparc because we have X -> Xsun by default).
> So, I guess the simplest fix is to add support for the other framebuffers
> to XFree.
That's simply not true. It might be the most _desirable_ fix (for
some), at least until Xorg came along, but it's not likely the simplest
fix by any definition of "simplest". I'm not even convinced yet that
it's the "right" fix in terms of being the most elegant and secure and
such (i.e. that using the XFree86 Xserver on sparc hardware is the
The "old" Xsun code used to work just fine w.r.t. focus follows mouse,
even on MUCH slower machines (I was happy once upon a time with an SS-1
on my desktop, using the exact same framebuffer card). That was way
back with NetBSD-1.3 or before.
It would seem that somebody somewhere broke something in the new code.
(I just can't believe that XFree86's Xsun code could be that much older
and thus not have some fix that made it work in the old code.)
It's the same kind of breakage that may also be causing the screen saver
to kick in even while event have occured within microseconds of the
screeen blanking -- that never happened before, not even with the very
ancient Xserver I used to run on SunOS-4 on the same hardware. Here too
it would seem as though some more recent change, in the xfree code that
was most certainly branced from the working code, must be responsible.
I have no idea where to look or I'd have looked for more recent changes
in the xfree code that might be responsible for the breakage.
My frustration comes from having "upgraded" to something that's far more
broken than all of what came before it.
Greg A. Woods
H:+1 416 218-0098 W:+1 416 489-5852 x122 VE3TCP RoboHack <email@example.com>
Planix, Inc. <firstname.lastname@example.org> Secrets of the Weird <email@example.com>
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
-----END PGP SIGNATURE-----