Hm, I cannot reproduce that here on my 2015 macbook pro with Mojave and a clean 
config. 

* Did you enable any Python plugins that weren't enabled, and if so, which?
* If that is the case, does running krita as a test user or with a clean config (https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration) fix the issue?

No changes since last Keira update. 
iMac 2019 with Mac OS 10.15.5

Thanks and regards

Von meinem iPhone gesendet
Fernando Baptista Photograph!e
bapfoto.de
Jahnstr. 19
64385 Reichelsheim
Fon: 06164-5163343
Fax: 06164-5163346
Mobil: 0172-6986477
USt.-ID Nr.: DE152407160
Skype: bapfoto
https://www.bapfoto.de
Mail: fernando@bapfoto.de


> Am 15.07.2020 um 18:50 schrieb Boudewijn Rempt <bugzilla_noreply@kde.org>:
> 
> https://bugs.kde.org/show_bug.cgi?id=424241
> 
> Boudewijn Rempt <boud@valdyas.org> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>         Resolution|---                         |WAITINGFORINFO
>             Status|REPORTED                    |NEEDSINFO
>                 CC|                            |boud@valdyas.org
> 
> --- Comment #1 from Boudewijn Rempt <boud@valdyas.org> ---
> Hm, I cannot reproduce that here on my 2015 macbook pro with Mojave and a clean 
> config. 
> 
> * Did you enable any Python plugins that weren't enabled, and if so, which?
> * If that is the case, does running krita as a test user or with a clean config
> (https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration) fix the
> issue?
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

"no changes since the latest update" doesn't tell me whether you enabled python plugins that were disabled by default.

Please check, like I asked, with a clean configuration.

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.

Yeah, updating the application doesn't mean you start with a clean confuguration, so please try resetting it :)
I'm marking this bug report as NeedsInfo again.

Created attachment 130184 [details]
attachment-3007-0.html

Seems problem disappeared after todays new update to Mac OS 1015.6.

Thanks and regards,
Fernando

> Am 16.07.2020 um 13:51 schrieb Tymond <bugzilla_noreply@kde.org>:
> 
> https://bugs.kde.org/show_bug.cgi?id=424241
> 
> Tymond <tamtamy.tymona@gmail.com> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>         Resolution|---                         |WAITINGFORINFO
>                 CC|                            |tamtamy.tymona@gmail.com
>             Status|REPORTED                    |NEEDSINFO
> 
> --- Comment #5 from Tymond <tamtamy.tymona@gmail.com> ---
> Yeah, updating the application doesn't mean you start with a clean
> confuguration, so please try resetting it :)
> I'm marking this bug report as NeedsInfo again.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

Fernando Baptista Photographie
bapfoto.de



Jahnstr. 19 • 64385 Reichelsheim
Tel.: +49-6164-5163343
Mobil: +49-172-6986477
Mail: fernando@bapfoto.de
Web: www.bapfoto.de

Created attachment 130185 [details]
PastedGraphic-11.png

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.

Since it disappeared after system update, we can assume it wasn't a problem in Krita code.