Bug 458550 - Useless 'View stable version on local bundle' button when I open a flatpak bundle without a version number set
Summary: Useless 'View stable version on local bundle' button when I open a flatpak bu...
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: master
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-31 13:44 UTC by Patrick Silva
Modified: 2022-09-16 15:30 UTC (History)
2 users (show)

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

Attachments
screen recording (2.15 MB, video/webm)
2022-08-31 13:44 UTC, Patrick Silva 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2022-08-31 13:44:16 UTC 
Created attachment 151735 [details]
screen recording

SUMMARY
When I open a flatpak bundle with Discover, a button labeled 'View stable version on local bundle' is available.
If I click on it, Discover returns to the same page. Please watch the attached screen recording.

EXPECTED RESULT
I'm not sure what is the purpose of 'View stable version on local bundle' button. Make it work or remove it.

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.25.80
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.5
Graphics Platform: Wayland
Comment 1 Nate Graham 2022-08-31 20:01:25 UTC 
Not intended for this use case, no.

Where can I get a Flatpak bundle file to test this? I can only find .flatpakref files on flathub.org.
Comment 3 Nate Graham 2022-08-31 20:04:55 UTC 
Cannot reproduce with https://github.com/flameshot-org/flameshot/releases/download/v12.1.0/org.flameshot.Flameshot-12.1.0.x86_64.flatpak.

Looks like this happens because the local bundle in question lacks a version number. We should detect this use case.

And the author of the bundle should fix that.
Comment 4 Aleix Pol 2022-09-02 17:48:55 UTC 
Can you try if you still get this weird behaviour? This should be addressed as of aa9e92bc5d269b33e64e660ed7d7cd18eb12a3a2, which I worked on the same day of this bug report.
Comment 5 Nate Graham 2022-09-02 18:49:10 UTC 
.
Comment 6 Patrick Silva 2022-09-16 15:30:55 UTC 
Cannot reproduce on Plasma 5.26 beta.