Created attachment 161695 [details] screenshot STEPS TO REPRODUCE 1. open Discover 2. search for any of these apps from flathub: Slack Quetoo Vocal SMPlayer Planner Paper Olive 3. click on the app you have searched for OBSERVED RESULT the description page opens but the screenshots are not loaded. Discover shows an inline message saying "Could not access the screenshots". Please see the attached screenshot. EXPECTED RESULT all screenshots are loaded SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Graphics Platform: Wayland
Right now with Plasma 6, I can reproduce this 100% when the app's source is Flathub beta, but 0% when the source is the normal Flathub stable repo (bug 475842). Are you able to reproduce that too?
I can reproduce with apps from both sources.
Interesting, I guess it's a different bug, then.
Tested again all apps mentioned in comment 0; can only reproduce with Paper from flathub. https://flathub.org/apps/io.posidon.Paper Operating System: Arch Linux KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.9.0 Graphics Platform: Wayland
Just thinking from looking back at the screenshot on the original report, does Paper have any alternative sources on your device (e.g. is the sources drop-down available), or is it Flathub only? Asking as I can't reproduce on Fedora KDE 42, and I have only Flathub given as a source for Paper.
Created attachment 180604 [details] screenshot of Paper As we can see in the screenshot attached to this comment, flathub is the only source for Paper.
I can reproduce - it's the size! I noticed you had Discover maximized at a pretty high resolution, and when I did the same I also got the same empty screenshot - and also get that when clicking to view a larger version of the image, regardless of the Discover window size. My guess would be that the Flatpak backend is looking for a higher-resolution version of the screenshot from the repository (Flathub, in this case), and shows an error instead of falling back to the smaller image? That could explain why certain applications work now but didn't then, if they had higher-resolution screenshots uploaded since you originally tried them. It's probably not the cause, but the code referenced and touched in this commit might be where a fallback could be placed? https://invent.kde.org/plasma/discover/-/commit/d594c01f5669dbda48039098b12b98d313d051ac