| Summary: | Krita crashes when I use my VisTablet Realm Pro pen/stylus. | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | frijid4 |
| Component: | Tablets (tablet issues are only very rarely bugs in Krita!) | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | VERIFIED WAITINGFORINFO | ||
| Severity: | crash | CC: | halla |
| Priority: | NOR | ||
| Version First Reported In: | 2.9.11 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | http://commits.kde.org/krita/22c3c0d5d49ef164e4def4d545faee7f37797a5f | Version Fixed In: | |
| Sentry Crash Report: | |||
|
Description
frijid4
2016-05-30 02:43:53 UTC
Thanks for your report. It's the same issue, probably, as with the other cheap tablets with broken drivers like Trust, Genius, Peritab... They all seem to use the same drivers, the same hardware internally, and we still haven't got a piece of hardware to use to test and fix the bug. The output shows the same probably uninitialized values returned by the driver when asking for the context. *** This bug has been marked as a duplicate of bug 362948 *** 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 363873, bug 351059, bug 354979, bug 362948 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 363873, bug 351059, bug 354979, bug 362948 M +35 -2 libs/ui/input/wintab/kis_tablet_support_win.cpp http://commits.kde.org/krita/22c3c0d5d49ef164e4def4d545faee7f37797a5f (In reply to Boudewijn Rempt from comment #1) > Thanks for your report. It's the same issue, probably, as with the other > cheap tablets with broken drivers like Trust, Genius, Peritab... They all > seem to use the same drivers, the same hardware internally, and we still > haven't got a piece of hardware to use to test and fix the bug. > > The output shows the same probably uninitialized values returned by the > driver when asking for the context. So will there be a patch eventually, or are there just too many cheap tablets to compensate for? I'm greatly interested in using Krita, thank you. |