[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #15 from Boudewijn Rempt --- I guess there isn't much more we can do with this report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 --- Comment #14 from Sabine Wieluch --- > (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. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 --- Comment #13 from Alvin Wong --- (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. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 Boudewijn Rempt changed: What|Removed |Added Platform|unspecified |MS Windows --- Comment #12 from Boudewijn Rempt --- 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. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 --- Comment #11 from Boudewijn Rempt --- So, should we just cap those values? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 --- Comment #10 from Alvin Wong--- D'oh, that's not it. The tablet log shows pressure values higher than 1, of course it would crash. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 --- Comment #9 from Alvin Wong--- 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? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 --- Comment #8 from Sabine Wieluch--- Created attachment 110853 --> https://bugs.kde.org/attachment.cgi?id=110853=edit 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 :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 Alvin Wongchanged: What|Removed |Added CC||alvinhoc...@gmail.com --- Comment #7 from Alvin Wong --- 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 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 --- Comment #6 from Sabine Wieluch--- Created attachment 110356 --> https://bugs.kde.org/attachment.cgi?id=110356=edit tablet log from crash Hey, sorry for the delay. I have the tablet log :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 --- Comment #5 from Boudewijn Rempt--- 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. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 --- Comment #4 from Sabine Wieluch--- (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 :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 Boudewijn Remptchanged: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #3 from Boudewijn Rempt --- 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. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 --- Comment #2 from Sabine Wieluch--- Created attachment 110260 --> https://bugs.kde.org/attachment.cgi?id=110260=edit crashlog Wacom Driver crash log -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389688] Crash on first pen use (2 Wacom devices installed; Win10)
https://bugs.kde.org/show_bug.cgi?id=389688 Boudewijn Remptchanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Could you try to make a crash log? See https://docs.krita.org/Dr._Mingw_debugger -- You are receiving this mail because: You are watching all bug changes.