Bug 499246

Summary: Brush pressure sensitivity not persisting after switch apps
Product: [Applications] krita Reporter: Trevor <shalomav>
Component: Brush enginesAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: penguinflyer2222
Priority: NOR    
Version First Reported In: 5.2.1   
Target Milestone: ---   
Platform: macOS (DMG)   
OS: macOS   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Trevor 2025-01-28 16:34:27 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. launch Krita preferably using 2 monitors. Running Krita on a single monitor and other desktop apps on the other monitor
2. Setup the default painting workspace and select a brush that has pressure sensitivity enabled. While painting the the paint is applied depending on the pressure, gentle at first and then slowly build up paint.
3. Click some app on the other monitor and type something using the keyboard into the other app

OBSERVED RESULT

Navigate back to the Krita and start painting. The brush's pressure sensitive is lost and it starts painting with 100% pressure, meaning it draws a thick line with paint. After few seconds it resets back to the prior settings. A workaround is to click some other tool, back to Brush and continue working in Krita.

EXPECTED RESULT
Brush should retain its current settings (pressure sensitivity)

SOFTWARE/OS VERSIONS
Windows: 
macOS: macOS Big Sur Version 11.7.10 MacBook mid 2014. Intel chipset
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
I'm also using a Wacom Cintiq as the primary display.
Comment 1 Freya Lupen 2025-01-28 18:33:24 UTC

*** This bug has been marked as a duplicate of bug 430927 ***