SUMMARY When a Wacom application configuration for Krita has been created and selected, Krita is only displaying the default configuration in the button panel on the Intuos 4. The Wacom driver is version 6.3.39-1 dated 4/27/20. This issue was initially seen with 4.3 Beta 1 and now again in Beta 2. Current stable Krita version works fine. STEPS TO REPRODUCE 1. Create a customized application set in the Wacom Tablet Properties app 2. Load Krita 4.3 Beta 1 or 2 3. Observe the default button config. 4. Make sure that the Krita app is selected in the Wacom Tablet app OBSERVED RESULT The button config on the hardware has not changed. EXPECTED RESULT The button config on the hardware should reflect the setting in the Wacom app. SOFTWARE/OS VERSIONS Windows: 10.0.18363 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The pen pressure seems fine. The hardware buttons and the tablet ring all work correctly for the default configuration. However, that is a pretty useless config. as far and Krita and my workflow go.
Krita doesn't do anything whatsoever with the internal workings of the wacom driver. How do you think that this could be a bug in Krita, instead of the Wacom driver?
If you have several portable versions at once on your PC, it might be that Wacom doesn't treat them as one program but as several so it only sees the 4.2.9 Krita as having custom settings and all others as having default ones. So you'd need to create custom settings for every version of Krita you have on your system. THat would be not a bug, neither in Krita nor in Wacom settings: different executable locations are different programs, I guess, as far as Wacom is concerned. If you installed the beta version instead of using the portable one: - have you installed it in the same place as the 4.2.9? - have you checked if first installing the beta, and then 4.2.9 again makes the Wacom settings work?
Created attachment 128993 [details] attachment-16135-0.html Wow. What a difference in these two responses. Tymond, thank you for actually recognizing that a user is trying to help by reporting an anomaly that they are seeing on their system. I purposely did not install the beta and did use the portable version. I guess I can uninstall 4.2.9 and flip them around and see what happens. It's a good suggestion. As for " How do you think that this could be a bug in Krita, instead of the Wacom driver?" Well, not being an engineer, I guess all I can say is...the same version of the driver works in one version of Krita and doesn't in the another". (but thanks for asking) On Tue, Jun 2, 2020 at 7:20 AM Tymond <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=422350 > > Tymond <tamtamy.tymona@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |tamtamy.tymona@gmail.com > > --- Comment #2 from Tymond <tamtamy.tymona@gmail.com> --- > If you have several portable versions at once on your PC, it might be that > Wacom doesn't treat them as one program but as several so it only sees the > 4.2.9 Krita as having custom settings and all others as having default > ones. So > you'd need to create custom settings for every version of Krita you have on > your system. THat would be not a bug, neither in Krita nor in Wacom > settings: > different executable locations are different programs, I guess, as far as > Wacom > is concerned. > > If you installed the beta version instead of using the portable one: > - have you installed it in the same place as the 4.2.9? > - have you checked if first installing the beta, and then 4.2.9 again > makes the > Wacom settings work? > > -- > You are receiving this mail because: > You reported the bug.
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
I followed the suggestion from Tymond and removed my existing install of Krita and restarted the PC. I loaded up the 4.3 Beta 2 portable install and tested the tablet. Everything worked as it should. Thanks to Tymond for a suggestion I would not of thought of myself. I am marking the bug report as RESOLVED and NOT A BUG.
Thanks @Alan for coming back with that information! Btw - in general for tablet issues I always suggest going to krita-artists.org and asking there first because in most cases it's either solvable by different configuration (switching Windows Ink <-> Wintab, disabling Windows flicks, minimizing double-click distance...) or not something Krita has control over, or even if, it's not Krita's code but Qt. And in general krita-artists.org is more user-oriented and user-friendly than this website which is more development-oriented, so it's better to ask for support on KA. (Here it's more like a list of tasks, fixes to do, for developers).
Created attachment 129029 [details] attachment-8917-0.html Thanks for the tip! On Wed, Jun 3, 2020 at 11:09 AM Tymond <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=422350 > > --- Comment #6 from Tymond <tamtamy.tymona@gmail.com> --- > Thanks @Alan for coming back with that information! > > Btw - in general for tablet issues I always suggest going to > krita-artists.org > and asking there first because in most cases it's either solvable by > different > configuration (switching Windows Ink <-> Wintab, disabling Windows flicks, > minimizing double-click distance...) or not something Krita has control > over, > or even if, it's not Krita's code but Qt. And in general krita-artists.org > is > more user-oriented and user-friendly than this website which is more > development-oriented, so it's better to ask for support on KA. (Here it's > more > like a list of tasks, fixes to do, for developers). > > -- > You are receiving this mail because: > You reported the bug.