Created attachment 161973 [details] What the Discover Homepage looks like SUMMARY I've just installed a fresh KDE Neon instance onto my laptop with the hopes of migrating from Kubuntu, but with newer KDE software. Unfortunately, I've run into two bugs, one of which I'm mentioning here (the other is just that the KDE Neon staart symbol turns into the KDE multicolored logo when trying to set it to my app launcher symbol, but that's besides the point). When I open Discover, the Home page tells me that I'm not connected, and the "Editor's choice" thing is weirdly not at the top of the window, possibly because of some default reserved space I don't know about. Everything else about Discover is seemingly working fine, it's *just* the Home page that isn't working. Per the recommendation of a different user with a similar bug but on Arch (and from a while ago), I tried reinstalling appstream, but that just broke Discover altogether with no way to fix it. So, I tried reinstalling again, and the original issue persisted. This is the laptop I intend to use for school, so I'm hoping this issue isn't all that important. Though worst-case scenario, I'll just switch back to Kubuntu LTS. I still get KDE, so I'm happy. STEPS TO REPRODUCE 1. Download the current available Neon iso from official page and install to computer 2. Open Discover OBSERVED RESULT Home reports connectivity errors, everything else is fine. EXPECTED RESULT Discover works as intended (home page loads apps) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27.8 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION
If you switch to another page (e.g. "Installed") and then back to "Home", does it start showing content?
And have you by any chance disabled NetworkManager and started to manage network connections via another method?
(In reply to Nate Graham from comment #1) > If you switch to another page (e.g. "Installed") and then back to "Home", > does it start showing content? Unfortunately I tried this, and no dice. (In reply to Nate Graham from comment #2) > And have you by any chance disabled NetworkManager and started to manage > network connections via another method? Unless this occurs on install, no. Basically the first thing I did after booting for the first time was open Discover (as I was curious to see the 5.27 changes made to the new Home page) and that's what I saw. Also, because this is the machine I use for school, I had to end up switching to Kubuntu, so I don't think I can give more information on the bug and its behavior anymore. I apologize for the inconvenience. Should I close this bug thread?
Thanks for the info.
*** Bug 480719 has been marked as a duplicate of this bug. ***
*** Bug 483603 has been marked as a duplicate of this bug. ***
In progress with https://invent.kde.org/plasma/discover/-/merge_requests/840.
Git commit 0c0bfd43f1a173397e69dad631c4018d9c28eb5a by Harald Sitter. Committed on 24/06/2024 at 14:28. Pushed by sitter into branch 'master'. packagekit: consider a not running daemon a dysfunction this in particular prevents us from incorrectly presenting network connectivy (from the AbstractResourcesBackend) as dysfunction when the more topical lack of packagekitd was detected. M +20 -0 libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp M +1 -0 libdiscover/backends/PackageKitBackend/PackageKitBackend.h https://invent.kde.org/plasma/discover/-/commit/0c0bfd43f1a173397e69dad631c4018d9c28eb5a