Git Product home page Git Product logo

Comments (5)

jigpu avatar jigpu commented on July 17, 2024

Hi! Unfortunately we can't be too much help with your particular issue. Our kernel driver is only used with Wacom tablets (or tablet PCs using Wacom sensors), not tablets from other brands like Waltop.

Looking at your log, it appears that the "hid-generic" kernel driver and the "libinput" Xorg driver are being used to power your tablet. If the pointer doesn't respond to tablet input, the issue will be a bug in one of those two drivers. I would suggest capturing a recording of the kernel events sent by your device to better understand what is going on. Install the "evemu-tools" package and then run sudo evemu-record > /tmp/waltop.log. You'll be prompted to select a device: type in the number for your Waltop tablet and press Enter. Next, move the stylus around on the tablet for a few seconds. Finally, press CTRL+C to stop the recording.

Next, file a bug at https://bugs.freedesktop.org against the "xorg" product and select the "Input/libinput" component on the bug form. Provide all the information you have, along with this new log file. The libinput maintainer should be able to let you know if the kernel events look sane or not. From there, the root cause of your issue can be fixed :)


As for the libwacom packages you've been installing... Libwacom is only a database of tablet properties which is used by programs like the Cinnamon Control Center to provide you with appropriate options for the particular tablet you have plugged in. Updating or removing it won't have any effect on the device actually working and moving the pointer. The libwacom database does contain data for non-Wacom devices, but it doesn't look like it has any info about your particular Waltop tablet. Once you get the issue with your tablet worked out, you're more than welcome to file an issue at https://github.com/linuxwacom/libwacom/issues requesting that your tablet be added to the database.

from input-wacom.

cptX avatar cptX commented on July 17, 2024

Hi jigpu,
I'm really disappointed to see you closing this issue so soon.

My tablet is Waltop based on walcom chip, and it is still working using a wacom driver in linux 17.3 . So correct me if I'm wrong, you are making a driver for wacom tablets, and I have a walcom based tablet, which in 17.3 is working. So why shouldn't your driver in LM18.2 (Ubuntu 16.04) be related to my issue?

My only question actually sums up to why is your driver working in LM17.3 (Kernel 4.4) and not LM18.2 (kernel 4.13).

To understand better, who was responsible for producing the files
libwacom2_0.11+dfsg-0ubuntu1_amd64.deb
libwacom-common_0.11+dfsg-0ubuntu1_all.deb
for ubuntu 14.04 which successfully worked for my tablet in LM17.3 (Kernel 4.4)?

Are these files using your driver or not?

from input-wacom.

jigpu avatar jigpu commented on July 17, 2024

As I explained, your tablet does not use our driver. No Waltop tablet uses our driver. Your tablet uses the hid-generic driver that is developed on the LKML and the libinput driver that is developed at freedesktop.org. We do develop the libwacom library but that is not used by either of those two drivers, and has never included a definition of your tablet.

Sorry, but there really isn't anything we can do but point you to the correct developers.

from input-wacom.

cptX avatar cptX commented on July 17, 2024

OK solution found as you can see here:
https://forums.linuxmint.com/viewtopic.php?f=49&t=268898&p=1468224#p1468224

The /usr/share/X11/xorg.conf.d/50-wacom.conf is the only correct file that should exist in that folder and includes a section for Waltop drivers, so I insist that the Waltop Tablets are walcom powered tablets...

from input-wacom.

jigpu avatar jigpu commented on July 17, 2024

Good to hear. Reading your linked thread, I think I now understand now the source of the confusion. Both the xf86-input-wacom and libinput drivers can be used to decode data from many different tablet manufacturers (but this bug tracker is for the "input-wacom" driver which can only decode Wacom tablet data). Your logs indicated that your system was using libinput, and I thought that was intentional. Any issue with libinput would need to be filed with their bug tracker. It seems, however, that this is instead a configuration issue, with the Mint 18.2 changing the default from "use xf86-input-wacom" to "use libinput".

from input-wacom.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.