Hey all,
I recently uninstalled an reinstalled the packages xorg-driver-input-wacom and wacomtablet, but when I went to reinstall these packages my tablet was no longer showing up under xsetwacom --list devices which stops me from using it. I checked around the Internet and it appears that the tablet is supposed to show up as a USB device (and when I enter lsusb it does come up), but it isn't showing up under /dev/input. I know there exists a dependency on libwacom but I have not uninstalled/reinstalled that package because it will uninstall a large amount of packages on my system if I remove this dependency.

That said, if I uninstall libwacom, which will remove all the packages which have dependencies, then reinstall everything it just uninstalled with libwacom, will this help jog my system back into recognizing this Wacom tablet?

I looked at how to link events in /dev/input but it all seemed a little too complicated for me. I could try to learn, but I thought I might break else along the way.

Also, would it be better for me to just compile my own verison of libwacom or is that equally complicated? (I've never compiled anything from source myself, let alone set up my system to utilize said packages)

Any advice would be helpful!

Have you tried to reconect the device after reinstalling all thoose packages? It seems like udev takes care of events when you plug the tablet, and a rule should populate the devices under /dev/input/by-id it basically links to a mouse

    clasclin Yes, unfortunately, when I reconnect xsetwacom list devices still returns nothing. Even if it is now recognized in /dev/input/by-id I would be completely amiss as to the next step of editing which config files in order to get it to be recognized by xsetwacom.

      Bhibb Frist check if the driver is currently loaded lsmod | grep -i wacom, other thing you can do is search for errors in the xorg log file grep 'wacom' /var/log/Xorg.0.log. The man page for xsetwacom says it's an utility to query and modify the driver so no config file there, however a persistent config could be created under /etc/X11/xorg.conf.d/70-wacom.conf, you should have a copy in /usr/share/X11/xorg.conf.d/70-wacom.conf. Also you could boot into a live cd and test the output of thoose commands

        clasclin Thanks for your help with this!

        lsmod | grep -i wacom
        wacom 84865 0
        hid 104377 3 hid_generic,usbhid,wacom

        and,

        grep 'wacom' /var/log/Xorg.0.log
        [ 427.835] (II) LoadModule: "wacom"
        [ 427.835] (II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so
        [ 427.836] (II) Module wacom: vendor="X.Org Foundation"
        [ 427.836] (II) Build version: xf86-input-wacom-xf86-input-wacom-0.38.0
        [ 427.836] (II) wacom: Driver for Wacom graphics tablets: PenPartner, Graphire,
        [ 427.838] (II) Using input driver 'wacom' for 'Wacom Co.,Ltd. Intuos BT S Pen'
        [ 427.898] (II) UnloadModule: "wacom"

        My 70-wacom.conf files look stock to me. They don't mention my "intuos" tablet in the list, but I've had this tablet work on this machine before. Any advice from the above output would be very helpful, thank you!

        clasclin I did as you suggested and logged into a live USB session to check the output. It varies from my machine, but I'm not sure what it means! Also, my tablet is working completely fine in this live USB session.

        lsmod | grep -i wacom
        wacom 118784 0
        usbhid 53248 1 wacom
        hid 135168 4 hid_steam,wacom,usbhid,hid_generic

        and,

        grep 'wacom' /var/log/Xorg.0.log
        [ 20.838] (II) LoadModule: "wacom"
        [ 20.838] (II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so
        [ 20.864] (II) Module wacom: vendor="X.Org Foundation"
        [ 20.864] (II) Build version: xf86-input-wacom-xf86-input-wacom-0.38.0
        [ 20.864] (II) wacom: Driver for Wacom graphics tablets: PenPartner, Graphire,
        [ 20.864] (II) Using input driver 'wacom' for 'Wacom Intuos BT S Pen'
        [ 20.985] (II) Using input driver 'wacom' for 'Wacom Intuos BT S Pad'
        [ 21.073] (II) Using input driver 'wacom' for 'Wacom Intuos BT S Pen eraser'
        [ 21.087] (II) Using input driver 'wacom' for 'Wacom Intuos BT S Pen cursor'

          Bhibb It looks like it's trying to load the wacom module and the next line just unload the module, so not using anything at all. The output should look like your live usb, the using input driver part...
          You can try to unload/load the module manually and test if it works. Remove with modprobe -r wacom, and load with modprobe wacom as root. The xorg probably tell you what's going on you could use less /var/log/Xorg.0.log and watch for errors (EE) and warning (WW) related to wacom

          But here is the last resource of what you can try. The package manager eopkg has the hability to rollback, if you type eopkg history it will show you all the operations related to installed and removed packages in the system (see man eopkg for details). So, in a live usb environment you could try to replicate the scenario in a safe way without messing up you actual system.

          For example in a live environment

          1. Install something small like an irc client
            eopkg install irssi
          2. Check the history
            eopkg history
          3. Tell the system to rollback, it will ask you with yes/no confirmation
            eopkg history --takeback n # n is the number of the operation

          If you're gonna try in your actual system keep in mind that it could potentially break it, so be prepare for the worst and backup your important files before and just rollback to the point where you don't remove important files like xorg-driver-input-wacom or libwacom

            clasclin Thanks for your recommendations! I've used the process you've described here before to success, but this time it wasn't cutting it. I took this opportunity to test out my backups by doing a fresh install of Solus Budgie over my drive. I'm happy to report that now my Wacom tablet works, and so does my Deja-dup snapshots!

            Thanks again for your time, but it seems like I must have messed something up poking around somewhere I didn't belong.