Bug 397211 - Discover doesn't properly show flatpak appdata (missing images, description flatpak name)
Summary: Discover doesn't properly show flatpak appdata (missing images, description f...
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: Flatpak Backend (show other bugs)
Version: 5.13.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-08-06 13:11 UTC by autinfrancois2
Modified: 2018-10-29 02:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
No pictures displayed, no description on krita flatpak (236.77 KB, image/png)
2018-08-06 13:11 UTC, autinfrancois2
Details
Discover showing data correctly (272.96 KB, image/png)
2018-08-15 12:58 UTC, Omar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description autinfrancois2 2018-08-06 13:11:05 UTC
Created attachment 114326 [details]
No pictures displayed, no description on krita flatpak

When viewing flatpaks through discover, no images previews are being displayed and some keep their flatpak names (e.g. org.gnome.Lollypop.desktop).

Steps to reproduce:
- Open discover
- Click on a flatpak

Additional information: At startup, Discovers asks to check whether Appstream is properly set up.
Comment 1 Nate Graham 2018-08-09 20:25:57 UTC
"org.gnome.Lollypop.desktop" is actually a Flathub bug.

What happens if you remove the flathub repo and re-add it?
Comment 2 autinfrancois2 2018-08-10 13:50:37 UTC
I've got the same issues after re-adding the repo! However I've gotten a huge amount of flatpak updates afterwards. Strange indeed.
Comment 3 Nate Graham 2018-08-10 13:52:43 UTC
Strange indeed.
Comment 4 autinfrancois2 2018-08-10 14:00:11 UTC
Well the updates fail, actually. But the terminal output changed.

Maybe this will help.

francoisautin@metal:~% plasma-discover                  
QQmlComponent: Created graphical object was not placed in the graphics scene.

** (process:25456): WARNING **: 15:58:12.198: Found icon of unknown type, skipping it: unknown
Could not open the AppStream metadata pool "Metadata files have errors: /usr/share/app-info/xmls/google-chrome.xml"
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation."
Discarding invalid backend "servicemenu.knsrc"
Discarding invalid backend "ksysguard.knsrc"
Couldn't get latest commit for com.discordapp.Discord
Couldn't get latest commit for org.gimp.GIMP
Couldn't get latest commit for org.kde.krita
Couldn't get latest commit for org.qbittorrent.qBittorrent
Couldn't get latest commit for org.videolan.VLC
Couldn't get latest commit for org.freedesktop.Platform.Compat32
Couldn't get latest commit for org.freedesktop.Platform.Icontheme.Adwaita
Couldn't get latest commit for org.freedesktop.Platform.ffmpeg
Couldn't get latest commit for org.freedesktop.Platform
Couldn't get latest commit for org.gnome.Platform.Locale
Couldn't get latest commit for org.gnome.Platform
Couldn't get latest commit for org.gtk.Gtk3theme.Breeze-Dark
Couldn't get latest commit for org.gtk.Gtk3theme.Breeze
Couldn't get latest commit for org.kde.KStyle.Adwaita
Couldn't get latest commit for org.kde.KStyle.Adwaita
Couldn't get latest commit for org.kde.Platform.Locale
Couldn't get latest commit for org.kde.Platform
Couldn't get latest commit for org.kde.krita.Locale
Couldn't get latest commit for org.videolan.VLC.Locale

Flatpak updates from flathub work on my other PC, so I'd say it is likely that this isn't a flathub bug.
Comment 5 Omar 2018-08-15 12:58:00 UTC
Created attachment 114445 [details]
Discover showing data correctly
Comment 6 Omar 2018-08-15 13:01:05 UTC
Could it be something related to Flatpak/Discover specifically on Fedora, because everything works fine for me on KDE Neon, Discover v5.13.4

https://bugs.kde.org/attachment.cgi?id=114445
Comment 7 Aleix Pol 2018-09-03 10:39:24 UTC
Sounds like OP had connectivity problems. The issue on "Couldn't get latest commit for X" could be the culprit.

Do you still have the problem?
Comment 8 Andrew Crouthamel 2018-09-28 03:16:19 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Andrew Crouthamel 2018-10-29 02:21:03 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!