Bug 465013 - PSDs do not load properly and show a blank canvas with several lines.
Summary: PSDs do not load properly and show a blank canvas with several lines.
Status: RESOLVED DUPLICATE of bug 464015
Alias: None
Product: krita
Classification: Applications
Component: File formats (show other bugs)
Version: 5.1.5
Platform: Android Android 13.x
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-29 22:07 UTC by Wontoon
Modified: 2023-01-29 22:44 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wontoon 2023-01-29 22:07:03 UTC
SUMMARY
When opening a PSD file in Krita 5.1.5 on Android 13, the PSD will not load properly. Happens on a Samsung Galaxy Tab S8 Ultra. Also tried it on my phone (Samsung Galaxy Note 10+) with 5.1.3 still installed (!) and on Krita 5.1.5 on deaktop (Flatpak), both of which still open properly.

STEPS TO REPRODUCE
1. Choose a PSD file and attempt to open it in Krita (5.1.5, Android 13).
2. Cry.

OBSERVED RESULT
You will see the file have its proper dimensions but see a white canvas with a few lines. Thumbnail works just fine in the dropdown menu. 

EXPECTED RESULT
The file to load as normal.

SOFTWARE/OS VERSIONS
Krita 5.1.5 for Android (Samsung Galaxy Tab, Android 13)

ADDITIONAL INFORMATION
For now my workaround is to just convert PSDs to KRA on another platform and import it into Android. PSD import did work fine for all versions before 5.1.5; not exactly sure if it's 5.1.5 on the tablet or in general.
Comment 1 amyspark 2023-01-29 22:44:17 UTC
Hi!

It wasn't exactly Android, it affected all devices that have an Arm processor, including the Apple Macbooks.

This is a duplicate of bug 464015 which I've fixed in the 5.1 nightlies and in the upcoming 5.2 release. We've not been able to push a release to the Play Store yet, because of the dependency upgrades we've been doing for 5.2.

*** This bug has been marked as a duplicate of bug 464015 ***