Bug 411016 - krita stops drawing and gives me a message when i save
Summary: krita stops drawing and gives me a message when i save
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: General (other bugs)
Version First Reported In: 4.2.5
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-17 16:36 UTC by joost
Modified: 2019-08-19 08:00 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
image of the message krita gives me (24.38 KB, image/png)
2019-08-17 16:36 UTC, joost
Details

Note You need to log in before you can comment on or make changes to this bug.
Description joost 2019-08-17 16:36:16 UTC
Created attachment 122202 [details]
image of the message krita gives me

SUMMARY
Krita stops drawing after switching between the drawing function of my tablet pen and eareser function. and if I try to save my drawing then I am hit with the message "wait untill the completion of the editing of the image" 

STEPS TO REPRODUCE
1. keep switching between the draw function and earaser function
2. 
3. 

OBSERVED RESULT
krita stops drawing and if I try to save I get a odd message

EXPECTED RESULT
krita keeps on drawing and I am able to save without a message.

SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 wolthera 2019-08-17 16:51:56 UTC
Hi, this should be fixed in the last Krita: Next (And Krita: Stable), can you check?
Comment 2 joost 2019-08-17 17:39:55 UTC
(In reply to wolthera from comment #1)
> Hi, this should be fixed in the last Krita: Next (And Krita: Stable), can
> you check?

Do you mean wich version I am using? It is version 4.2.5 . If that isn't what you meant what should I check. You are a bit vague
Comment 3 wolthera 2019-08-17 18:00:26 UTC
There's 'krita:next' and 'krita:stable' entries on the download section of Krita.org, these are our nightly builds for the master and bugfix branches respectively, so the code is newer than 4.2.5.

Could you check if the fix that went in a few days ago and thus is in one of these two builds works to solve your bug? Because otherwise you have a different bug and we need to figure out why it is different :)
Comment 4 joost 2019-08-17 18:32:03 UTC
(In reply to wolthera from comment #3)
> There's 'krita:next' and 'krita:stable' entries on the download section of
> Krita.org, these are our nightly builds for the master and bugfix branches
> respectively, so the code is newer than 4.2.5.
> 
> Could you check if the fix that went in a few days ago and thus is in one of
> these two builds works to solve your bug? Because otherwise you have a
> different bug and we need to figure out why it is different :)

I didn't download krita from krita.org I bought it from steam
Comment 5 Tiar 2019-08-17 18:42:44 UTC
Hi! Krita you bought on Steam is the same Krita that you can download from the website (just with the addition that on Steam, your Krita updates yourself; if you download from the website, you need to update it yourself). Please go to the website https://krita.org/en/download/krita-desktop/ and then scroll down a bit, there is a section called "Nightly Builds". There are two options: Krita Next and Krita Plus. Please click on the Krita Plus Windows version. 

Then you'll be redirected to this website: https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/ - please download the file that looks like this:

krita-nightly-x64-v4.2.5-[number]-[some random letters and numbers].zip - just make sure it's .zip, not -dbg.zip.

Then unpack it (it's a .zip archive after all) and click on the 'krita' file inside. It will open Krita. Please use it for a little while and see if the issue persists there or not. It's a new version, newer than what you have on Steam, so it contains some code that should fix your issue - but we need you to check it.

If the issue doesn't show up in this version, then that means that when we make a new official version of Krita (on Steam, too), it will be fixed there, too :)
Comment 6 Tiar 2019-08-17 19:34:51 UTC
Just for the record, this person on reddit: https://www.reddit.com/r/krita/comments/cp9num/waiting_for_image_operation_to_complete/ex7raue/?context=3
says that they had this issue and in Krita Plus package from today (August 17th, 2019, either g1a1ba08147 or the previous one) they didn't have those issues, so it looks to be fixed for them (not that they tested for a long time or anything... it's like three hours between my comment and theirs ;) )
Comment 7 joost 2019-08-17 19:42:04 UTC
(In reply to Tymond from comment #6)
> Just for the record, this person on reddit:
> https://www.reddit.com/r/krita/comments/cp9num/
> waiting_for_image_operation_to_complete/ex7raue/?context=3
> says that they had this issue and in Krita Plus package from today (August
> 17th, 2019, either g1a1ba08147 or the previous one) they didn't have those
> issues, so it looks to be fixed for them (not that they tested for a long
> time or anything... it's like three hours between my comment and theirs ;) )

thanks for the tip and help. I was planning on drawing all day tomorrow so if the isseu still persits I will contact you.
Comment 8 Bug Janitor Service 2019-08-18 04:33:16 UTC
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.
Comment 9 Tiar 2019-08-18 10:54:13 UTC
Bug janitor made a mistake this time ;) We're still waiting for confirmation.
Comment 10 joost 2019-08-18 15:05:14 UTC
This is the result after about 7 hours of straight drawing using Krita. The newer version did indeed solve my problem. I was able to draw until i litterly dropped. so at least it is solved at my part. I like to thank the people who helped me with the bug. you guys are awesome
Comment 11 Halla Rempt 2019-08-19 08:00:37 UTC
Thanks for getting back to us :-)