Bug 389688

Summary:	Crash on first pen use (2 Wacom devices installed; Win10)
Product:	[Applications] krita	Reporter:	Sabine Wieluch <sabine.wieluch>
Component:	Tablets (tablet issues are only very rarely bugs in Krita!)	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	crash	CC:	alvin, halla
Priority:	NOR
Version:	3.3.3
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	crashlog tablet log from crash crashlog with debugpackage

Description Sabine Wieluch 2018-01-31 13:05:52 UTC

I use a Wacom Cintiq Pro13 im combination with my Thinkpad Yoga 260 with built in digitizer. 
After reboot and the Cintiq not attached: I open Krita and on first tap (with the built in digitizer) on the canvas, krita crashes. 

Workaround: Stopping "Wacom Professional Service" in the Windows Service Manager

Comment 1 Halla Rempt 2018-01-31 13:08:38 UTC

Could you try to make a crash log? 

See https://docs.krita.org/Dr._Mingw_debugger

Comment 2 Sabine Wieluch 2018-01-31 13:19:09 UTC

Created attachment 110260 [details]
crashlog

Wacom Driver crash log

Comment 3 Halla Rempt 2018-01-31 14:31:32 UTC

Thanks! I wonder what is going on exactly, but that would need some more debugging. I wonder how I can setup a system like yours with two tablets.

Comment 4 Sabine Wieluch 2018-01-31 15:02:01 UTC

(In reply to Boudewijn Rempt from comment #3)
> Thanks! I wonder what is going on exactly, but that would need some more
> debugging. I wonder how I can setup a system like yours with two tablets.

If there is a way to send you more debugging data from my system, I'm glad to help :)

Comment 5 Halla Rempt 2018-02-01 14:28:20 UTC

Hm, maybe you could also make a tablet log. See https://docs.krita.org/KritaFAQ#What_if_your_tablet_is_not_recognized_by_Krita.3F . Make sure you press ctrl-shift-t before creating the first image, so we can see what tablets Krita sees.

Comment 6 Sabine Wieluch 2018-02-05 17:03:39 UTC

Created attachment 110356 [details]
tablet log from crash

Hey,
sorry for the delay. I have the tablet log :)

Comment 7 Alvin Wong 2018-02-11 16:16:45 UTC

Can you get the debug package (https://docs.krita.org/Dr._Mingw_debugger#Using_the_Debug_Package) and make a new crash log? It would contain more information to help us figure out what's wrong.

Portable 3.3.3 release: https://download.kde.org/stable/krita/3.3.3/krita-3.3.3-x64.zip
Debug package: https://download.kde.org/stable/krita/3.3.3/krita-3.3.3-x64-dbg.zip

Comment 8 Sabine Wieluch 2018-02-20 18:31:27 UTC

Created attachment 110853 [details]
crashlog with debugpackage

Hi, I downloaded the debug package and extracted it to the portable krita folder. I attached the crashlog but it does not seem to show more information? Did I do it correctly? Thanks :)

Comment 9 Alvin Wong 2018-02-20 18:43:27 UTC

Yes, that should gives enough information for us.

Crash is at KisPaintingInformationBuilder::pressureToCurve
 https://github.com/KDE/krita/blob/v3.3.3/libs/ui/tool/kis_painting_information_builder.cpp#L145
which likely means m_pressureSamples isn't populated correctly. Could be a failure in KisCubicCurve::floatTransfer
 https://github.com/KDE/krita/blob/v3.3.3/libs/image/kis_cubic_curve.cpp#L482
due to an invalid tablet pressure curve?

Comment 10 Alvin Wong 2018-02-20 18:49:53 UTC

D'oh, that's not it. The tablet log shows pressure values higher than 1, of course it would crash.

Comment 11 Halla Rempt 2018-07-11 07:56:14 UTC

So, should we just cap those values?

Comment 12 Halla Rempt 2018-07-11 07:56:52 UTC

Btw, we're at 4.1.0 now. I still don't have a setup with two wacom tablets on one windows system, but I'm wondering if it's still reproducible.

Comment 13 Alvin Wong 2018-07-11 10:31:47 UTC

(In reply to Boudewijn Rempt from comment #11)
> So, should we just cap those values?

That would most likely fix the crash, but not the cause (either some mishandling in the WinTab code or a driver bug).

(In reply to Boudewijn Rempt from comment #12)
> Btw, we're at 4.1.0 now. I still don't have a setup with two wacom tablets
> on one windows system, but I'm wondering if it's still reproducible.

The reporter's setup is with a Cintiq and a built-in digitizer. Now that I think about it, the built-in digitizer probably comes with some sort of Wacom Feel driver instead of the Intuos/Cintiq driver. They might had the Intuos/Cintiq driver installed which doesn't handle the built-in digitizer properly (just a guess). If both digitizers are Cintiq/Intuos which uses the same driver, there might not be a problem.

Comment 14 Sabine Wieluch 2018-07-11 11:22:31 UTC

> (In reply to Boudewijn Rempt from comment #12)
> > Btw, we're at 4.1.0 now. I still don't have a setup with two wacom tablets
> > on one windows system, but I'm wondering if it's still reproducible.

Sadly, I can not test this at the moment as I switched from Win10 to kubuntu.

> The reporter's setup is with a Cintiq and a built-in digitizer. Now that I
> think about it, the built-in digitizer probably comes with some sort of
> Wacom Feel driver instead of the Intuos/Cintiq driver. They might had the
> Intuos/Cintiq driver installed which doesn't handle the built-in digitizer
> properly (just a guess). If both digitizers are Cintiq/Intuos which uses the
> same driver, there might not be a problem.

I can confirm this. The driver for the built in digitizer is called WinTab Unitity (from Lenovo Download Page) and looks similar to the bamboo drivers I used some years ago (which were feel it). The Cintiq driver definitly was a different one.

Comment 15 Halla Rempt 2019-04-16 10:24:21 UTC

I guess there isn't much more we can do with this report.