Hi,
There seem to be quite a number of known bad interactions with the
xorg 1.4 input layer at present. It changed considerably from 1.3
and we're being bitten from two angles, the linuxwacom support for
that is still relatively immature, and there are bugs in the xorg
input layer itself which I'm led to believe will only be fixed in
1.5+ versions.
There is a new linuxwacom release which contains some fixes for
reported problems, but gauging from the upstream reports, it's
still crashing X (in some cases in keyboard handler related ways)
for a number of people.
So the short and unfortunate answer, is that this seems doomed to
suck for Lenny :( People who really need their tablet(s) for
professional use are best advised to stick to xorg 1.3 (in stable),
though if you have a newer tablet, introduced since then, you will
also need a backport of the newer linuxwacom drivers to support it.
The current nasty bugs should be limited to just the xorg 1.4 code
branches, so such a backport should work ok (and this did work
nicely and reliably prior to xorg 1.4).
I'm aiming to get some packages into experimental soon for testing
with xorg 1.5, but I don't anticipate this will instantly fix all
of the problems either (and may well introduce some new ones).
People who have the time, skill, and inclination to hack on this
are more than welcome to make their problems and patches known on
the linuxwacom-{discuss,devel} list(s). The more people we get
contributing there, the better our chances of having this solid
again by the time Squeeze freezes, and there are friendly and
helpful folk who can point out the known workarounds.
Sorry, there was just more work in this transition than there
were people to do it, so it's about as badly 'out of phase' for
release with Lenny this time as things should ever get ...
Ron
On Fri, Oct 03, 2008 at 11:02:10PM +0100, Chris Lamb wrote:
> David Buckley wrote:
>
> > I use a number of binds on these buttons to make them bindable in my
> > window manager
> [...]
> > pressing the pad buttons which have keys assigned kills the whole X
> > server.
> [...]
> > The final message in the log is:
> >
> > Fatal server error:
> > Impossible keyboard event
>
> Please obtain a backtrace for this crash. You can find some useful
> information here:
>
> http://wiki.debian.org/XStrikeForce/XserverDebugging
>
> (There doesn't appear to be a x-x-input-wacom-dbg, however)
>
>
> Regards,
>
> --
> ,''`.
> : :' : Chris Lamb
> `. `'` [EMAIL PROTECTED]
> `-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
