Whenever I touch my tablet with the pen, it doesn't matter if it's to open a new file or draw something, it automatically crashes (using a Peritab-302) Reproducible: Always Steps to Reproduce: 1. Opening Krita 2. Trying to open a new file with the pen Actual Results: It crashes Expected Results: Open a new canvas, file to draw on The program works great with my mouse, I can open a canvas with it, but Krita crashes anyway when I try to use the pen
Which version of Krita are you using? 2.9.11 or the 3.0 beta?
2.9.11
Could you check with the 3.0 beta? Your brand of tablet is very obscure and we don't have hardware to test with, but it sounds like the same problem Trust and Genius tablets give.
I checked it, it works fine at first but crashes 2min later
Okay, thanks for checking. Could you try to get a tablet log for us (https://docs.krita.org/KritaFAQ#Tablets) and check if http://files.kde.org/krita/3/windows/devbuilds/krita-3.0-Beta-master-d330a4a-x64-dbg.zip produces a backtrace?
Created attachment 98969 [details] Tablet DebugView file here's the .LOG file
Okay, so you didn't get a backtrace when testing the -dbg build?
(In reply to Boudewijn Rempt from comment #7) > Okay, so you didn't get a backtrace when testing the -dbg build? Hello. I think I have the same sort of problem. I use a Trust TB7300 (so old it's not even sold anymore but old faithful still works! But I understand you probably might not be able to do testing yourself <3) It didn't work on 2.7-2.9 releases but the Version: 3.1 Alpha (git be 28b 1b) it works! YAY! I tried the most recent 'bleeding' release announced on FB 18/05/16. Again it works fine until I touch the pen to the tablet whereupon Krita immediately crashes. My partner found out how to do a bug report and I will attach it to this message just as soon as I work out how to. Thanks for making such a wonderful art programme which has meant I can pursue my hobby btw! It really is wonderful!
Created attachment 99139 [details] Krita debug file when attempting to use Trust Tablet TB7300 Krita debug file when attempting to use Trust Tablet TB7300 on latest 3.0 release. Thanks! <3 :D
Comment on attachment 99139 [details] Krita debug file when attempting to use Trust Tablet TB7300 Looks like the driver is reporting nonsense: 00000054 22.66714478 [6312] krita.tabletlog: lc.lcInExtX = 65535 00000055 22.66719818 [6312] krita.tabletlog: lc.lcInExtY = 65535 And puts the good data here, instead: 00000060 22.66758728 [6312] krita.tabletlog: lc.lcSysOrgX = 0 00000061 22.66767120 [6312] krita.tabletlog: lc.lcSysOrgY = 0 00000062 22.66775894 [6312] krita.tabletlog: lc.lcSysExtX = 3200 00000063 22.66781998 [6312] krita.tabletlog: lc.lcSysExtY = 1080
Hi Sarah, What is your exact monitor configuration and resolution?
(In reply to Boudewijn Rempt from comment #11) > Hi Sarah, > > What is your exact monitor configuration and resolution? Hi I have two monitors. My main monitor has a resolution of 1920 x 1080, this is the monitor the tablet is configured to respond to (specifically I have been told that the tablet is mapped to monitor 1 only - which is not the TV). My other monitor is an older widescreen TC, the resolution is 1280 x 720. So I am dual screening I think. Thanks for the speedy reply!
(In reply to Sarah from comment #12) > (In reply to Boudewijn Rempt from comment #11) > > Hi Sarah, > > > > What is your exact monitor configuration and resolution? > > Hi > > I have two monitors. My main monitor has a resolution of 1920 x 1080, this > is the monitor the tablet is configured to respond to (specifically I have > been told that the tablet is mapped to monitor 1 only - which is not the > TV). My other monitor is an older widescreen TC, the resolution is 1280 x > 720. So I am dual screening I think. > > Thanks for the speedy reply! Sorry widescreen TV not TC. Silly me!
Hi Adriano and Sara, What are the exact types of these tablets and what are the exact driver revisions you are using?
(In reply to Boudewijn Rempt from comment #14) > Hi Adriano and Sara, > > What are the exact types of these tablets and what are the exact driver > revisions you are using? HI again! I'm using a Trust WIDE SCREEN DESIGN TABLET TB-7300 with a Windows 10 (64 bit driver). The company doesn't produce the tablet any more but they created the windows 10 driver after finding out that I still using the tablet (isn't that lovely!?) http://www.trust.com/en/product/15358-wide-screen-design-tablet-tb-7300 Thanks again for all your help and looking into this, it means a lot. :D
We got a second-hand Trust TB 5300... And that doesn't allow us to reproduce the crash yet!
(In reply to Boudewijn Rempt from comment #16) > We got a second-hand Trust TB 5300... And that doesn't allow us to reproduce > the crash yet! Mine still does it but in a different way now! I downloaded the latest 3.0 (git f0cbffc) release and it comes up with a box about screen resolution. I didn't think I could describe it well so I took a screenshot and did another Debug report, Maybe I just have an awkward tablet which doesn't play well with others! Although I have been told my graphic card could also be being a bother, I have attached a screenshot of the details of the card and the monitors so I can be more specific.
Created attachment 99283 [details] Monitor and graphics driver details
Created attachment 99284 [details] Screen resolution box when I try to use the tablet
Created attachment 99285 [details] Debug crash report when using newest release Krita with Trust Tablet TB7300
*** Bug 363873 has been marked as a duplicate of this bug. ***
*** Bug 363684 has been marked as a duplicate of this bug. ***
*** Bug 363754 has been marked as a duplicate of this bug. ***
*** Bug 362868 has been marked as a duplicate of this bug. ***
CRASHES: Adesso Cybertablet M14 Peritab-302 Trust Tablet TB7300 VisTablet Realm Pro Aiptek 14000u (latest driver: v5.03, 2013-10-21) NOT: Trust Tablet TB5300
Git commit 942cb4b614246ad08485eaa2264154de2d07ce17 by Dmitry Kazakov. Committed on 03/06/2016 at 12:46. Pushed by dkazakov into branch 'master'. Add a workaround for weird tablets Instead of the returning the size of the needed buffer these "nice" tablet drivers start writing its name straight into the buffer pointed by a null pointer. See a comment in the code for more details Related: bug 359298, bug 362868, bug 363684, bug 363873, bug 351059, bug 354979 M +35 -2 libs/ui/input/wintab/kis_tablet_support_win.cpp http://commits.kde.org/krita/942cb4b614246ad08485eaa2264154de2d07ce17
Git commit 22c3c0d5d49ef164e4def4d545faee7f37797a5f by Dmitry Kazakov. Committed on 03/06/2016 at 12:48. Pushed by dkazakov into branch 'krita/3.0'. Add a workaround for weird tablets Instead of the returning the size of the needed buffer these "nice" tablet drivers start writing its name straight into the buffer pointed by a null pointer. See a comment in the code for more details Related: bug 359298, bug 362868, bug 363684, bug 363873, bug 351059, bug 354979 M +35 -2 libs/ui/input/wintab/kis_tablet_support_win.cpp http://commits.kde.org/krita/22c3c0d5d49ef164e4def4d545faee7f37797a5f
(In reply to Dmitry Kazakov from comment #27) > Git commit 22c3c0d5d49ef164e4def4d545faee7f37797a5f by Dmitry Kazakov. > Committed on 03/06/2016 at 12:48. > Pushed by dkazakov into branch 'krita/3.0'. > > Add a workaround for weird tablets > > Instead of the returning the size of the needed buffer these > "nice" tablet drivers start writing its name straight into > the buffer pointed by a null pointer. > > See a comment in the code for more details > Related: bug 359298, bug 362868, bug 363684, bug 363873, bug 351059, bug > 354979 > > M +35 -2 libs/ui/input/wintab/kis_tablet_support_win.cpp > > http://commits.kde.org/krita/22c3c0d5d49ef164e4def4d545faee7f37797a5f Hello I'm sorry to keep bothering you but I'm afraid the work around in the latest download 3.0 still has the same error. I read the bug fixing report and it was very interesting! I even understood some of it. :D Which is super rare for me with PC things. If there's nothing that can be done I appreciate all the time and effort you have made, we donated what we could afford which I hope offset the awkwardness a but for you.
Created attachment 99373 [details] Krita offset
Created attachment 99374 [details] Debug report for latest Krita release showing the issue causing crash
Created attachment 99375 [details] The 3.0 Alpha which works with Tablet I thought this might help if it shows the difference between the Krita which understands the awkward tablet and the one which causes Krita to crash