| Summary: | Crashes when copy pasting null image | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | myin <illuslion1998> |
| Component: | General | Assignee: | amyspark <amy> |
| Status: | RESOLVED LATER | ||
| Severity: | normal | CC: | amy |
| Priority: | NOR | ||
| Version First Reported In: | 5.1.5 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
myin
2023-02-17 16:02:40 UTC
I'll check this out. This is a case of the infamous "clipboard is cleared midway into pasting". In your case, it is caused by selecting "paste from clipboard" in the source selection dialog, but then something in between clears the clipboard. So when the image is fetched from the clipboard, a null QImage is returned, and that doesn't match the expected state. If you can reproduce it consistently, can you check if you have a password manager active, or something that regularly cleans your clipboard? No, there shouldn't be something like that. But that doesn't explain why it works normally if "Inherit alpha" is disabled. It only crashes when I copy a layer with inherit alpha. Is it not reproducible on your side? I could try it on other machines to check if it's only on my current one. Yes, I have 5.1.5 and current master on Windows and neither crash when copying a layer with Inherit Alpha, even after closing the source document. 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. So what I have tested now is: - In Windows (VM): nothing happens - In another Linux machine: nothing happens I guess the normal behaviour is that nothing should happen when I paste an inherit alpha layer as a new document. Pasting in the same documents works normally. My initial guess that it might be a Linux problem doesn't seem to be the case. It only occurs on my main Linux machine. So this bug doesn't seem to be very important and is also a pretty rare use case, so I will close it for now. Thanks for looking into it though! |