Bug 401300 - Discover can't install missing flatpak backend in Fedora
Summary: Discover can't install missing flatpak backend in Fedora
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 5.14.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-22 06:13 UTC by Mustafa Muhammad
Modified: 2024-05-07 10:07 UTC (History)
4 users (show)

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


Attachments
plasma-discover log from kubuntu 21.04 (13.48 KB, text/x-log)
2021-02-18 09:50 UTC, Unknown
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mustafa Muhammad 2018-11-22 06:13:44 UTC
SUMMARY
Using discover on Fedora, in the settings, I had "Missing Backends" part, I pressed the button in front of "Flatpak Backend", it wasn't installed, and the whole "Missing Backends" part disappeared.
Even after I close Discover and start it again, it gets hidden immediately after I press Settings.

STEPS TO REPRODUCE
1. Open Discover on a newly installed Fedora KDE with updates and test updates applied (Maybe not required, but in my case, these are the details)
2. In Discover Settings, press install in front of "Flatpak Backend"
3. 

OBSERVED RESULT
The "Missing Backends" part disappears

EXPECTED RESULT

The backend should be installed.

Operating System: Fedora 29
KDE Plasma Version: 5.14.3
Qt Version: 5.11.1
KDE Frameworks Version: 5.52.0
Kernel Version: 4.19.2-301.fc29.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4770K CPU @ 3.50GHz
Memory: 15.4 GiB of RAM

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2018-11-26 22:08:57 UTC
Hmm, feels like maybe a distro packaging issue...
Comment 2 Rex Dieter 2018-11-27 12:38:40 UTC
This worked for me last I tested with 5.13.x

Retesting with 5.14.3 now... 

Other than slow startup (seems to spawn ~70+ packagekit transactions initially, according to 'pkmon'), once that's done, going to 
settings -> missing backends , clicking install next to "Discover -l Flatpak backend" finishes rather quickly without incident.
(repeated test twice, manually removing the plasma-discover-flatpak package prior to each test)

So in short, I cannot reproduce what's been reported here.
Comment 3 Rex Dieter 2018-11-27 12:39:25 UTC
(Though I just tested on f28, I'll retry on f29 soon)
Comment 4 Rex Dieter 2018-11-27 14:44:52 UTC
So I *can* reproduce this on my f29 box, interesting, though my findings are slightly different:

removing plasma-discover-flatpak, and (re)running plasma-discover.  

First try, behavior difference(s) from f28:
* startup is fast (good), no sign of the many transactions seen before
* settings displays no information about backends at all (only available repositories)

second try, first do:
$ pkcon refresh force

while that is going, run plasma-discover, initially settings showed the backend info and no repositories shown.  Once the repositories displayed, the backend info disappeared again  :(

doing more tests, but it does appear to be fairly reproducible on fedora 29 alright.

It may be because fedora 29 has a higher number of available repositories to be shown compared to f28 (I have 47 listed on my box, including rpmfusion).
Comment 5 Rex Dieter 2018-11-27 14:46:32 UTC
Testing with:
qt5-qtbase-5.11.1-9.fc29
kf5-kirigami2-5.52.0-1.fc29
PackageKit-1.1.11-1.fc29
plasma-discover-5.14.3-1.fc29
Comment 6 Rex Dieter 2018-11-27 14:53:53 UTC
May be relevant, getting this error too (that disappears almost too quick to notice):

"Please make sure that Appstream is properly setup on your system"

console showing:
Could not open the AppStream metadata pool ""

$ appstreamcli search plasma-discover
works and shows results, so it's not completely non-functional

$ sudo appstreamcli refresh-cache
seems to have fixed the startup warning (for now), so maybe not relevant after all.  original issue remains after that.
Comment 7 Justin Zobel 2020-11-21 05:40:51 UTC
I don't have a Fedora machine setup, can you please test with Fedora 33.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 8 Bug Janitor Service 2020-12-06 04:34:05 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
mark the bug 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 Mustafa Muhammad 2020-12-06 07:18:17 UTC
Sorry for the delay, on new installation of Fedora 33, Discover has no "Missing Backends" part, even though the snap backend (plasma-discover-snap) is not installed.
Nowadays Fedora ship flatpak backend by default, so not sure if this (hiding the "Missing Backends") is the intended behaviour.

Regards
Mustafa
Comment 10 Unknown 2021-02-18 09:49:41 UTC
Same problem but on kubuntu, missing backends just hidden.
Comment 11 Unknown 2021-02-18 09:50:02 UTC
Created attachment 135825 [details]
plasma-discover log from kubuntu 21.04
Comment 12 Unknown 2021-03-17 10:23:12 UTC
Same in Fedora KDE 33
Comment 13 Unknown 2022-01-27 11:35:32 UTC
Still a problem with fedora kde 35.
Comment 14 Unknown 2022-05-22 17:32:28 UTC
Same on fedora kde 36, log https://pastebin.com/NFxEVcpR
Comment 15 Harald Sitter 2024-05-07 09:41:43 UTC
Seems to work well on latest fedora kde (after I removed the backend because it is installed by default ;))