https://bugs.kde.org/show_bug.cgi?id=363265
David REVOY <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #3 from David REVOY <[email protected]> --- > David, do you remember on which version of Krita you saw this bug? @Friedrich ; I'm building daily Krita, so I think git~master of 2016-05-19 was the date I could trigger the bug. > I am not sure the quickfix done to close this bug made really would change > anything, but it add complexitity to the startup, so would like to know if > this fix really was needed :) @Friedrich : The bug is still reproductible; I just forgot to ran another test. Since 'mergedimage.png' inside the *.kra exist, all my script prefer to extract this rather than running a full command-line re-render and export. Here is how you can study this bug: How to reproduce: =============== 1. Select a *.kra file on your disk, eg. myartwork.kra 2. Copy it to .myartwork.kra-autosave.kra to create a fake autosaved copy 3. then run: krita myartwork.kra --export output.png Result: ====== You'll have the pop-up, and even the command-line exporter will segfault. -- You are receiving this mail because: You are watching all bug changes.
