« Return to Thread: Graphire4 Pad Button freeze with 0.10.11.
Re: Graphire4 Pad Button freeze with 0.10.11.
by Chris Bagwell
::
Rate this Message:
Hi Favux,
For first bug report, it does sound same issue as I looked into a
while back. The kernel driver is mistakenly telling userland that the
PAD device has gone out of proximity when you use pen. From that
point, buttons don't work.
Something has changed in xf86-input-wacom that we must l trust kernel
information more then we used to. My personal preference is to fix
the kernel to give us good info instead of reverting back to old
xf86-input-wacom behavior.
Maybe when Ping gets back next month we can have some progress. Or
hopefully we can find a user that doesn't mind hacking kernel drivers.
I can give tons of guidance on patch to implement (its like 3 lines
for simple solution) but ultimately I can't push forward much more
since I don't have the device.
For second bug report (X server crash), I've no idea. It sounds like
its own issue.
Chris
On Fri, May 27, 2011 at 3:45 PM, Favux ... <favux.is@...> wrote:
> Hi list,
>
> We're seeing some problems with the Graphire4 pad buttons in Ubuntu
> Natty (2.6.38 and xf86-input-wacom-0.10.11). Peter said he needed
> some more information. I have a little now.
>
> See this Launchpad bug report:
> https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/782756
> and this possibly related one:
> https://bugs.edge.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/769477
>
> What happens is the Graphire's buttons work until the stylus is used
> then they stop working. The only way to fix the button freeze is to
> hot plug the tablet.
>
> Chris worked on the Graphire pad button logic a few months ago. I
> seem to recall Chris and Ping talking about maybe implementing some
> kernel changes for the Graphire pad logic also, but I don't think
> anything happened.
>
> I've attached Conner's debug Xorg.0.log and his annotated version
> where he describes his actions. As far as I can see he gets a
> 6:usbParseKeyEvent when the buttons are working and the pad is
> recognized and a button event sent. But once he uses the stylus the
> 6:usbParseKeyEvent no longer happens. However I do see it pop up,
> apparently after he has unplugged his tablet, in the tablet removed
> stuff.
>
> Any help appreciated.
>
> Favux
>
> PS: This is my third attempt to post. Because of size limitations
> the Xorg.0.log can't be attached and the annotated Xorg.0.log had to
> be compressed.
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Linuxwacom-discuss mailing list
> Linuxwacom-discuss@...
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>
>
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
For first bug report, it does sound same issue as I looked into a
while back. The kernel driver is mistakenly telling userland that the
PAD device has gone out of proximity when you use pen. From that
point, buttons don't work.
Something has changed in xf86-input-wacom that we must l trust kernel
information more then we used to. My personal preference is to fix
the kernel to give us good info instead of reverting back to old
xf86-input-wacom behavior.
Maybe when Ping gets back next month we can have some progress. Or
hopefully we can find a user that doesn't mind hacking kernel drivers.
I can give tons of guidance on patch to implement (its like 3 lines
for simple solution) but ultimately I can't push forward much more
since I don't have the device.
For second bug report (X server crash), I've no idea. It sounds like
its own issue.
Chris
On Fri, May 27, 2011 at 3:45 PM, Favux ... <favux.is@...> wrote:
> Hi list,
>
> We're seeing some problems with the Graphire4 pad buttons in Ubuntu
> Natty (2.6.38 and xf86-input-wacom-0.10.11). Peter said he needed
> some more information. I have a little now.
>
> See this Launchpad bug report:
> https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/782756
> and this possibly related one:
> https://bugs.edge.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/769477
>
> What happens is the Graphire's buttons work until the stylus is used
> then they stop working. The only way to fix the button freeze is to
> hot plug the tablet.
>
> Chris worked on the Graphire pad button logic a few months ago. I
> seem to recall Chris and Ping talking about maybe implementing some
> kernel changes for the Graphire pad logic also, but I don't think
> anything happened.
>
> I've attached Conner's debug Xorg.0.log and his annotated version
> where he describes his actions. As far as I can see he gets a
> 6:usbParseKeyEvent when the buttons are working and the pad is
> recognized and a button event sent. But once he uses the stylus the
> 6:usbParseKeyEvent no longer happens. However I do see it pop up,
> apparently after he has unplugged his tablet, in the tablet removed
> stuff.
>
> Any help appreciated.
>
> Favux
>
> PS: This is my third attempt to post. Because of size limitations
> the Xorg.0.log can't be attached and the annotated Xorg.0.log had to
> be compressed.
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Linuxwacom-discuss mailing list
> Linuxwacom-discuss@...
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>
>
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
« Return to Thread: Graphire4 Pad Button freeze with 0.10.11.
| Free embeddable forum powered by Nabble | Forum Help |
