Is anyone able to use their tablet monitor in true dual/multi mode? I have a Yiynova MVP22U along with two Dell U2412M monitors. So far, for the cursor to coincide with the pen, I would have to set it in mirror mode or the other monitors need to be turned off.

From this post, I see many people solved their pressure issue by many means. I also have the similar issue - with wizardpen driver, the pressure works in MyPaint and GIMP but not in Krita. Anyone could help?

My OS: ArchLinux 64-bit
Krita: 2.9.4
[ilovepumpkin@ruige ~]$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 008: ID 8087:07dc Intel Corp.
Bus 002 Device 007: ID 5986:055e Acer, Inc
Bus 002 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 002 Device 003: ID 17ef:6025 Lenovo ThinkPad Travel Mouse
Bus 002 Device 006: ID 28bd:0074
Bus 002 Device 004: ID 1e3d:2093 Chipsbank Microelectronics Co., Ltd CBM209x Flash Drive (OEM)
Bus 002 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ilovepumpkin@ruige ~]$

[ilovepumpkin@ruige ~]$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ UGTABLET TABLET G5 9x6 id=10 [slave pointer (2)]
⎜ ↳ ThinkPad USB Travel Mouse id=11 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=15 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ Lenovo EasyCamera id=12 [slave keyboard (3)]
↳ Ideapad extra buttons id=13 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]
[ilovepumpkin@ruige ~]$

I had also try DIGImend - I gusess my kernal is too new so 'make' can not run.
==========================================================
[ilovepumpkin@ruige digimend-kernel-drivers-5]$ make
make -C /lib/modules/4.0.1-1-ARCH/build SUBDIRS=/home/ilovepumpkin/Downloads/digimend-kernel-drivers-5 modules
make[1]: Entering directory '/usr/lib/modules/4.0.1-1-ARCH/build'
make[1]: *** No rule to make target 'modules'。 停止。
make[1]: Leaving directory '/usr/lib/modules/4.0.1-1-ARCH/build'
Makefile:10: recipe for target 'modules' failed
make: *** [modules] Error 2
[ilovepumpkin@ruige digimend-kernel-drivers-5]$

And I also tried to use wacom driver, but I guess wacom driver does not support my tablet.
===============================
[ilovepumpkin@ruige ~]$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ UGTABLET TABLET G5 9x6 touch id=10 [slave pointer (2)]
⎜ ↳ ThinkPad USB Travel Mouse id=11 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=15 [slave pointer (2)]
⎜ ↳ UGTABLET TABLET G5 9x6 pad id=16 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ Lenovo EasyCamera id=12 [slave keyboard (3)]
↳ Ideapad extra buttons id=13 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]
[ilovepumpkin@ruige ~]$ xsetwacom --list devices
UGTABLET TABLET G5 9x6 touch id: 10 type: TOUCH
UGTABLET TABLET G5 9x6 pad id: 16 type: PAD
[ilovepumpkin@ruige ~]$

shenrui wrote:From this post, I see many people solved their pressure issue by many means. I also have the similar issue - with wizardpen driver, the pressure works in MyPaint and GIMP but not in Krita. Anyone could help?...

Did you try first without any driver? More than a year ago I needed the wizardpen driver for my waltop tablet, but now is simply recognized by the kernel working for any program. You can also try to change the pressure settings on Krita to see if is not working at all or is just not adjusted, I notice the sensitivity changes by program.

The time I notice I did not needed the driver any longer was by mere chance, and the wizardpen was giving me problems too, but I always compiled directly from the site not from the AUR, either case now just works. Arch-64 here too.

Quiralta wrote:

shenrui wrote:From this post, I see many people solved their pressure issue by many means. I also have the similar issue - with wizardpen driver, the pressure works in MyPaint and GIMP but not in Krita. Anyone could help?...

Did you try first without any driver? More than a year ago I needed the wizardpen driver for my waltop tablet, but now is simply recognized by the kernel working for any program. You can also try to change the pressure settings on Krita to see if is not working at all or is just not adjusted, I notice the sensitivity changes by program.

The time I notice I did not needed the driver any longer was by mere chance, and the wizardpen was giving me problems too, but I always compiled directly from the site not from the AUR, either case now just works. Arch-64 here too.

Thanks for your reply. I tried the case without any driver - I can see the cursor move in screen but can not draw anything in any programs like MyPaint, Krita or GIMP.

shenrui wrote:

Quiralta wrote:

shenrui wrote:From this post, I see many people solved their pressure issue by many means. I also have the similar issue - with wizardpen driver, the pressure works in MyPaint and GIMP but not in Krita. Anyone could help?...

Did you try first without any driver? More than a year ago I needed the wizardpen driver for my waltop tablet, but now is simply recognized by the kernel working for any program. You can also try to change the pressure settings on Krita to see if is not working at all or is just not adjusted, I notice the sensitivity changes by program.

The time I notice I did not needed the driver any longer was by mere chance, and the wizardpen was giving me problems too, but I always compiled directly from the site not from the AUR, either case now just works. Arch-64 here too.

Thanks for your reply. I tried the case without any driver - I can see the cursor move in screen but can not draw anything in any programs like MyPaint, Krita or GIMP.

Finally I solved my problem by modifying the source code based on hvfrancesco's method described on the page 13.

Here is my steps:
1) Follow this guide to prepare the environment and download source code - http://www.davidrevoy.com/article193/guide-building-krita-on-linux-for-cats
2) Add the following line in calligra/krita/ui/input/wintab/kis_tablet_support_x11.cpp to check my output
qDebug() << "found input device" << devs->name << "type" << devs->type << XGetAtomName(X11->display, devs->type);
3) Follow hvfrancesco's example to modify the code of calligra/krita/ui/input/wintab/kis_tablet_support_x11.cpp
4) Continue the build and install steps in - http://www.davidrevoy.com/article193/guide-building-krita-on-linux-for-cats

Here is my patch:

Code: Select all

diff -Naur old/calligra/krita/ui/input/wintab/kis_tablet_support_x11.cpp new/calligra/krita/ui/input/wintab/kis_tablet_support_x11.cpp
--- old/calligra/krita/ui/input/wintab/kis_tablet_support_x11.cpp   2015-05-28 22:49:04.860576168 +0800
+++ new/calligra/krita/ui/input/wintab/kis_tablet_support_x11.cpp   2015-05-28 22:49:57.490576950 +0800
@@ -96,6 +96,7 @@
         WacomTouch,
 
         AiptekStylus,
+   WizardPenTablet,
 
         NPredefinedAtoms,
         NAtoms = NPredefinedAtoms
@@ -137,6 +138,9 @@
     // Aiptek drivers (e.g. Hyperpen 12000U) reports non-standard type string
     "Stylus\0"
 
+    // UGTABLET TABLET G5 9x6    
+    "WizardPen Tablet\0"
+
 };
 
 KisX11Data *kis_x11Data = 0;
@@ -292,9 +296,16 @@
 
 #if defined(Q_OS_IRIX)
 #else
+       qDebug() << "found input device" << devs->name << "type" << devs->type << XGetAtomName(KIS_X11->display, devs->type);
 
-
-                if (devs->type == KIS_ATOM(XWacomStylus) || devs->type == KIS_ATOM(XTabletStylus) ||devs->type == KIS_ATOM(XInputTablet)) {
+                if (devs->type == KIS_ATOM(WizardPenTablet) ){
+    
+               qDebug() << "*********************** UGTABLET TABLET G5 9x6";
+          kis_haveEvdevTablets = true;
+                    deviceType = QTabletEvent::Stylus;
+                    gotStylus = true;
+   
+      } else if (devs->type == KIS_ATOM(XWacomStylus) || devs->type == KIS_ATOM(XTabletStylus) ||devs->type == KIS_ATOM(XInputTablet)) {
                     if (devs->type == KIS_ATOM(XInputTablet)) {
                         kis_haveEvdevTablets = true;
                     }


My tablet brand is UGEE so hope the UGEE users can benefit from my post.

And I think Krita team should document these steps somewhere so people can fix their own tablet issue at least for themselves temporarily.

Good finding shenrui! Then it was Krita not recognizing the tablet therefore you have to add it? Was this after installling the wizardpen drive and was it from the AUR or compiled directly from the source. Not that I need the information (different tablet here) but like you mention for future reference for those with similar hardware.

Quiralta wrote:Good finding shenrui! Then it was Krita not recognizing the tablet therefore you have to add it? Was this after installling the wizardpen drive and was it from the AUR or compiled directly from the source. Not that I need the information (different tablet here) but like you mention for future reference for those with similar hardware.

I didn't read all the code so I am not very sure how Krita handles my tablet before I changed the code. At that time I can draw but just there is no pressure so I think Krita recognized my tablet partially.

I tried to disable the wizardpen driver (just removed /etc/X11/xorg.conf.d/70-wizardpen.conf). And I found the debug code printed different strings. As you can see below, "XGetAtomName(X11->display, devs->type)" value is different.

Code: Select all

qDebug() << "found input device" << devs->name << "type" << devs->type << XGetAtomName(X11->display, devs->type);

with wizardpen driver:

Code: Select all

found input device UGTABLET TABLET G5 9x6 type 264 WizardPen Tablet

without wizardpen driver:

Code: Select all

found input device UGTABLET TABLET G5 9x6 type 98 TOUCHPAD

Then I changed my code to use "devs->name" instead.

Code: Select all

     //if (devs->type == KIS_ATOM(WizardPenTablet) ){
        if (QString(devs->name) == "UGTABLET TABLET G5 9x6"){
               qDebug() << "*********************** UGTABLET TABLET G5 9x6";


But once I started drawing with my stylus, Krita crashed. This means wizardpen driver is needed - at least for my tablet.

Regarding where I installed my wizardpen driver from, I am really sorry that I can not recall that. I installed it several months ago. But there is nothing returned from "yaourt -Q wizardpen" so I guess I installed wizardpen from source code.

Any information else you need, just feel free to let me know.

Hi,

[EDIT: Upgrading to Krita 2.9.10 solved the problem]

Apparently, I have the same problem janise described in Jun 2014, and I couldn't find a solution anywhere.

It is about a Huion H610 tablet installed on Ubuntu 14.04.3 LTS. I have already installed the driver from https://github.com/DIGImend/digimend-kernel-drivers and followed the instructions from https://krita.org/about/faq/#huiontablet regarding calibration.

I can draw in GIMP without pressure sensitivity and in MyPaint with pressure sensitivity. On Krita 2.8.1, however, while I can navigate correctly over toolbars and panes, the cursor disappears once it is moved over the drawing area, and nothing gets drawn. The mouse can draw lines, but not the tablet.

Has anybody faced and solved this problem?

Best wishes,
Thomas

It might be worth it to try updating? We're on 2.9.9/2.9.10 now? Things may have gotten fixed in between 2.8.1 and 2.9.9... (check the krita-lime repo instructions on the website)

TheraHedwig wrote:It might be worth it to try updating? We're on 2.9.9/2.9.10 now? Things may have gotten fixed in between 2.8.1 and 2.9.9... (check the krita-lime repo instructions on the website)

Upgrading to version 2.9.10 solved the problem, indeed.
I was using the default version from the Ubuntu repository. I apologise not having thought about this solution before.

Hello!

Just recently I installed Krita. I wanted to use with my tablet Trust TB - 7300 I have had for some years now. I have Win 8.1.

The problem is that pressure sensitivity is not working. I installed the newest driver from the Trust website and funny thing happened: whenever I try to open Krita using the tablet, it does not respond. If I open Krita using touchpad on my notebook, it works correctly until I touch the tablet with the pen - then it again crashes down. I uninstalled the driver and now it works normally but till without the sensitivity.

I tried to install other drivers from other companies which obviously did not work. I gave it a try...

Can somebody help me with this? Just to make it clear I do not have any experience with programming so please talk to me as you would to a small child

If you can donate a trust tablet to the project, we might be able to make it work -- but to be honest, trust is a brand that I don't think is worth spending a lot of time on. They stopped making their tablets, themselves.

Ok, thanks. I guess I will have to do without sensitivity for now. Later I may buy a new tablet. Apart from the sensitivity problem the recent one is still good though.

Enormous thanks to shenrui and his comment on page 15 https://forum.kde.org/viewtopic.php?f=139&t=98347&start=210#p335624 that explains the steps he took to build Krita locally and get his tablet working.

I can confirm that after preparing the build environment on Linux Mint 17, the same update he describes works for the Ugee 19" Pen Display Tablet.

Without the described patch, the tablet is identified as a mouse input device and so doesn't pass through the pressure information.

Thanks again shenrui. Your post was extremely helpful.