Bug 409019

Krita version 4.1.7 does have this problem on Windows 10 but version 4.2.1 (the latest version) does not. Can you upgrade to 4.2.1 and try that again?

Note: When I paste in your short paragraph from Steps To Reproduce, The font is changed to whatever my browser is using so the change to Ariel has to be done after this.

I’ll do that thank you so much!

Sent from my iPhone

> On Jun 21, 2019, at 10:41 PM, Ahab Greybeard <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=409019
> 
> Ahab Greybeard <ahab.greybeard@hotmail.co.uk> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|REPORTED                    |NEEDSINFO
>         Resolution|---                         |WAITINGFORINFO
>                 CC|                            |ahab.greybeard@hotmail.co.u
>                   |                            |k
> 
> --- Comment #1 from Ahab Greybeard <ahab.greybeard@hotmail.co.uk> ---
> Krita version 4.1.7 does have this problem on Windows 10 but version 4.2.1 (the
> latest version) does not. Can you upgrade to 4.2.1 and try that again?
> 
> Note: When I paste in your short paragraph from Steps To Reproduce, The font is
> changed to whatever my browser is using so the change to Ariel has to be done
> after this.
> 
> -- 
> 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.

Waiting for the bug report author to confirm all is well with 4.2.1.

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Created attachment 121406 [details]
attachment-28319-0.html

I've never heard of your bug status procedure and have not received an
email on it since your initial response.  Can you post a link where I might
be able to respond with the results? Your HowTo link looks more like
protocol for someone receiving a bug inquiry?

Mahalo,
Dave

On Sun, Jul 7, 2019 at 6:33 PM Bug Janitor Service <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=409019
>
> --- Comment #5 from Bug Janitor Service <bug-janitor@kde.org> ---
> Dear Bug Submitter,
>
> This bug has been in NEEDSINFO status with no change for at least
> 15 days. Please provide the requested information as soon as
> possible and set the bug status as REPORTED. Due to regular bug
> tracker maintenance, if the bug is still in NEEDSINFO status with
> no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
> due to lack of needed information.
>
> For more information about our bug triaging procedures please read the
> wiki located here:
> https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
>
> If you have already provided the requested information, please
> mark the bug as REPORTED so that the KDE team knows that the bug is
> ready to be confirmed.
>
> Thank you for helping us make KDE software even better for everyone!
>
> --
> You are receiving this mail because:
> You reported the bug.

Created attachment 121407 [details]
attachment-28405-0.html

Yes, 4.2.1 solved this.  Thank you so much,
Dave

On Sun, Jun 23, 2019 at 3:17 AM Ahab Greybeard <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=409019
>
> Ahab Greybeard <ahab.greybeard@hotmail.co.uk> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|REPORTED                    |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
>
> --- Comment #4 from Ahab Greybeard <ahab.greybeard@hotmail.co.uk> ---
> Waiting for the bug report author to confirm all is well with 4.2.1.
>
> --
> 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.

Thanks for getting back to us (Bug Janitor Service is a bot, btw). Since you report the issue was fixed in 4.2.1, I'm closing the bug (I'm not a bot :-))

Great. Thanks so much. Sorry I’d missed those prior emails. 
Dave

Sent from my iPhone

> On Jul 8, 2019, at 9:51 PM, Boudewijn Rempt <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=409019
> 
> Boudewijn Rempt <boud@valdyas.org> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                 CC|                            |boud@valdyas.org
>         Resolution|---                         |FIXED
>             Status|REPORTED                    |RESOLVED
> 
> --- Comment #9 from Boudewijn Rempt <boud@valdyas.org> ---
> Thanks for getting back to us (Bug Janitor Service is a bot, btw). Since you
> report the issue was fixed in 4.2.1, I'm closing the bug (I'm not a bot :-))
> 
> -- 
> You are receiving this mail because:
> You reported the bug.