x server crash (wacom on hp tc1100)

[mu3en]

fresh jaunty rc kubuntu install (+ updates) + nvidia 96 from jockey + wacom-tools + cellwriter (no other packages installed):

when cellwriter is launched from the k menu, x server restarts to the kdm login screen. (reproduced more than 5 times, same procedure). same x server crash to kdm login at various times using tablet buttons or stylus.

after further testing, problem seems related to x, configuration of xorg.conf yielded varying results, final issue seems to be:

1. if the commented lines in attached xorg.conf are both uncommented, behavior as described above. stylus button is right click and rotation via xsetwacom works.
2. if "isdv4" line only is uncommented, everything works fine but stylus button does nothing and xsetwacom (for rotation) does not find a device.
3. if "/dev/ttyS0" line only is uncommented xserver blanks upon x restart and all input is locked (have to hard reset).
4. if "/dev/ttyS0" line only is uncommented, and "/dev/input/wacom" substituted, stylus is completely unresponsive.

further testing reveals:

1. problem does not seem only related to the nvidia driver, nv driver behaves the same when cellwriter is launched (or randomly during stylus input), except instead of dropping back to kdm, the computer simply freezes and becomes completely unresponsive.
2. updating the linux wacom driver module to the latest stable version has no effect on behaviour.

seems there must be a clue in the consistency of the crash upon loading cellwriter, perhaps cellwriter is calling some input related function that prompts the xserver crash/lockup.

[mu3en (mu3en)]

not sure that this nvidia package definition is correct, as i updated
in the bug description, using the nv driver does not change the
problem. Seems more X or wacom related maybe...

thanks

On 22 Apr 2009, at 2327, Brian Murray wrote:

> ** Package changed: ubuntu => nvidia-graphics-drivers-96 (Ubuntu)
>
> --
> x server crash (nvidia + wacom on hp tc1100)
> https://bugs.launchpad.net/bugs/364996
> You received this bug notification because you are a direct subscriber
> of the bug.

[mu3en (mu3en)]

nv driver is same, problem seems more X or wacom related maybe