Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 196534

Summary: x11-drivers/xf86-input-hyperpen-1.1.0 broken with x11-base/xorg-server-1.4-r2
Product: Gentoo Linux Reporter: Stefan de Konink <stefan>
Component: Current packagesAssignee: Gentoo X packagers <x11>
Status: RESOLVED FIXED    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
URL: http://cgit.freedesktop.org/xorg/driver/xf86-input-hyperpen/
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 276822    

Description Stefan de Konink 2007-10-20 14:38:25 UTC
I decided to use my 'pen' again as input device. First I noticed that /dev/tts/0 did not exist anymore, so I reverted back to /dev/ttyS0. But when my 'pen' got close to the surface of the tablet. Linux/X completely crashes. I did not investigate if I could still log in remotely, but locally there is no way to make the machine to restart/switch back to a working console.

I presume this is an ABI incompatibility, and in the upstream git to changes are found yet. http://cgit.freedesktop.org/xorg/driver/xf86-input-hyperpen/

Reproducible: Always

Steps to Reproduce:
1. use hyperpen as driver
2. apply pen to the surface
3. crash

Actual Results:  
Crashing Xorg

Expected Results:  
Mouse movement.

cat /dev/ttyS0 works.
Comment 1 Stefan de Konink 2007-12-10 23:46:40 UTC
From a conversation on IRC, it seems the ABI has changed, therefore the driver calls a non-existent X function. This is solved now, could someone package it? Or apply the patch if the user uses 1.4?
Comment 2 Rémi Cardona (RETIRED) gentoo-dev 2009-07-08 12:42:14 UTC
Not a build failure per se, but I'm adding the blocker so we take a look at it. The ABI mismatch should have been caught by xorg-server.

Thanks
Comment 3 Rémi Cardona (RETIRED) gentoo-dev 2009-08-17 20:58:56 UTC
I've added xf86-input-hyperpen-1.3.0 to portage. If you can still reproduce the issue with this version, please don't hesitate to reopen this bug.

Thanks