Difference between revisions of "Wacom Tablet And Pen"

imported>Fhdk
imported>Fhdk
Line 13: Line 13:
===Known Issues===
===Known Issues===


* Slow drag in File Manager and very slow interaction of Tools and Brushes in Krita. The resolution is to modify the <code> 10-evdev.conf </code> in <code> /usr/share/X11/xorg.conf.d/10-evdev.con </code>
* Slow drag in File Manager and very slow interaction of Tools and Brushes in Krita. \
The resolution is to modify the <code>10-evdev.conf</code> in <code>/usr/share/X11/xorg.conf.d/10-evdev.conf</code>


There might be necessary to make a symlink of it like this:
There might be necessary to make a symlink of it like this:
Line 65: Line 66:
In Gnome, if someone wants to use the GDM theme of a custom gnome-shell theme to have a consistent look trough login/log-out/lock-screen, the settings for mapping the buttons will render a blank overlay with no options. Resolutions:
In Gnome, if someone wants to use the GDM theme of a custom gnome-shell theme to have a consistent look trough login/log-out/lock-screen, the settings for mapping the buttons will render a blank overlay with no options. Resolutions:


* Use the default <code> gnome-shell </code>, <code> adwaita </code> and <code> gdm </code>
* Use the default <code>gnome-shell</code>, <code>adwaita</code> and <code>gdm</code>
* Use the modified <code> manjaro-gnome-maia-theme </code>
* Use the modified <code>manjaro-gnome-maia-theme</code>


====The device is not recognized====
====The device is not recognized====
* The device is not recognized, the xinput doesn’t list it, etc, that is most likely due to a not supported device, no specific ID in the <code> /usr/share/libwacom/ </code> for it. A possible resolution is to install the <code> input-wacom-dkms </code> making sure that the headers for the kernel are installed too, then manually adding the modules to load. If will not provide a functionality if the modules are not loaded, and still relies in the <code> xf86-input-wacom </code>, <code> libwacom </code> and the Graphical interface for Tablet settings. Of course the <code> xsetwacom </code> commands work too, but the purpose is to have a GUI for settings and avoid any confusing/miss-passed settings from terminal.
* The device is not recognized, the xinput doesn’t list it, etc, that is most likely due to a not supported device, no specific ID in the <code>/usr/share/libwacom/</code> for it. A possible resolution is to install the <code>input-wacom-dkms</code> making sure that the headers for the kernel are installed too, then manually adding the modules to load. If will not provide a functionality if the modules are not loaded, and still relies in the <code>xf86-input-wacom</code>, <code>libwacom</code> and the Graphical interface for Tablet settings. Of course the <code>xsetwacom</code> commands work too, but the purpose is to have a GUI for settings and avoid any confusing/miss-passed settings from terminal.


====KDE Plasma 5====
====KDE Plasma 5====
Line 83: Line 84:
# DO NOT check Tap to execute action
# DO NOT check Tap to execute action


Click Apply button, disconnect and reconnect the tablet and it should work. From this point all the settings can be changed and have also the Express Buttons personalized, and calibrate the pen to the screen area. The settings are stored in <code> ~/.config/tabletprofilesrc </code>
Click Apply button, disconnect and reconnect the tablet and it should work. From this point all the settings can be changed and have also the Express Buttons personalized, and calibrate the pen to the screen area. The settings are stored in <code>~/.config/tabletprofilesrc</code>


====Mixed configurations====
====Mixed configurations====
Mixed configurations due to use of <code> xsetwacom </code> commands and other tools. Resolution is to undo all  and start with the GUI Settings.
Mixed configurations due to use of <code>xsetwacom</code> commands and other tools. Resolution is to undo all  and start with the GUI Settings.
Anonymous user