Bug 396935 - Krita refuses to open a file
Summary: Krita refuses to open a file
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: CPU Canvas (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-28 19:06 UTC by mona.guiot
Modified: 2018-07-28 20:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mona.guiot 2018-07-28 19:06:48 UTC
Hello ! I was working on a drawing then saved it . However , once I tried to open it again , Krita didn't let me ( and still doesn't ). Does anyone know how to solve this problem ? I would be thankful for anyone's help :(
Comment 1 Halla Rempt 2018-07-28 19:08:43 UTC
Can you please attach the file or a link to the file so we can see what's up?
Comment 2 mona.guiot 2018-07-28 19:17:13 UTC
(In reply to Boudewijn Rempt from comment #1)
> Can you please attach the file or a link to the file so we can see what's up?

Sure , here you go : 
https://drive.google.com/open?id=1C1fCvUQwYUFBsN5_sPoeQB21RoaJQwmt
Comment 3 Halla Rempt 2018-07-28 20:03:22 UTC
Okay, the file was corrupted. I've run a zip repair tool on the file. Layer 20 and 21 are lost, the rest works. You can get the repaired file here: https://www.dropbox.com/s/f7gqhaxo73fde15/7DS.kra?dl=0

Please do check your system for problems: your disk might be going bad, your system's memory might be going bad or you might have a problem with malware. 

In any case, this is the best I can do for you, so I'm closing the bug.
Comment 4 mona.guiot 2018-07-28 20:12:00 UTC
(In reply to Boudewijn Rempt from comment #3)
> Okay, the file was corrupted. I've run a zip repair tool on the file. Layer
> 20 and 21 are lost, the rest works. You can get the repaired file here:
> https://www.dropbox.com/s/f7gqhaxo73fde15/7DS.kra?dl=0
> 
> Please do check your system for problems: your disk might be going bad, your
> system's memory might be going bad or you might have a problem with malware. 
> 
> In any case, this is the best I can do for you, so I'm closing the bug.

Thanks a lot for your help !