Hi, in my setup of Aurora it is impossible to start the software manager Discover. When I click a button to start it I see the cursor bouncing for a couple of seconds but the main Discover window does not open.
When I try to open it in a terminal, typing plasma-discover, I see absolutely nothing, no text at all.
On the KDE forum I have seen more issues like this on different distro’s. Does anyone here have the same problem as I have?
What could be a cause for this?
I have a similar issue of Aurora not booting to SDDM. My post (Aurora Stable (41) unable to reach SDDM) here suggested that the issues were upstream on Kinoite but now that you’ve mentioned this, I wonder if it is KDE 6.2 having bugs.
On the KDE forum I also read that in other distro’s they have the same issue. Among them is neon, the KDE distro. But Nate Graham (KDE) wrote it is not a KDE fault but a bad packaging of the program in the distro. He knew that without investigating it first, he just wrote it. No idea where he got this info from.
That doesn’t make sense if it affects people using KDE neon. By Graham’s logic, it would mean that KDE is improperly packaging Plasma 6 for KDE neon. 
I was just thinking about the problem I have with Discover, the KDE software tool. It seems not many people here have this problem or else the forum would be filled by threads about it. So maybe something else is wrong in my setup. Now I can re-install Aurora but what if it doesn’t change one bit?
It is part of the base install of Aurora, it’s not a flatpak, nor is it layered. Is there a way it can be re-installed to see if it will work?
How else do I get it working?
Thanks.
I guess most people don’t just use discover and just install flatpaks through flatpak install from terminal.
Yes, I know I can do that, I can even install flatpaks straight from the Flathub website but that is besides the point. Discover is a part of KDE, it is installed by Aurora as part of the system and now because something is wrong with it, or with something else interfering with Discover, I should just forget about it?
When tomorrow another program stops working should I also forget about that too?
I was hoping for some help from somebody who knows the system, so it will all work again, but until now that didn’t happen. Unfortunately.
Thank you for your point to install it using the terminal, I have been looking into it already, but still hoping Discover will run soon again.
You don’t believe it: it is kinda running. I do get the main window, I can choose and select software, look at the details of this software, that all works.
But, after starting a second icon is placed on the taskbar showing that the program is running. This happens both when I start it using the normal taskbar icon and also when I start it from terminal using plasma-discover as command.
Starting it in the terminal gives me this:
plasma-discover
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false
qrc:/qt/qml/org/kde/discover/qml/BrowsingPage.qml:17:1: QML BrowsingPage: Created graphical object was not placed in the graphics scene.
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for com.github.tchx84.Flatseal
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for io.github.flattool.Warehouse
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for io.missioncenter.MissionCenter
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.fedoraproject.MediaWriter
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.fkoehler.KTailctl
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.gnome.DejaDup
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.gnome.World.PikaBackup
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.filelight
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.gwenview
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.kcalc
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.kclock
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.kontact
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.kweather
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.okular
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.mozilla.Thunderbird
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.mozilla.firefox
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for io.github.flattool.Warehouse.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for io.missioncenter.MissionCenter.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.fkoehler.KTailctl.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.freedesktop.Platform.GL.default
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.freedesktop.Platform.GL.default
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.freedesktop.Platform.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.freedesktop.Platform
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.gnome.DejaDup.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.gnome.World.PikaBackup.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.gtk.Gtk3theme.adw-gtk3-dark
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.gtk.Gtk3theme.adw-gtk3
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.KStyle.Adwaita
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.Platform.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.Platform
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.filelight.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.gwenview.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.kcalc.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.kclock.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.kontact.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.kweather.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.kde.okular.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.mozilla.Thunderbird.Locale
org.kde.plasma.libdiscover.backend.flatpak: Couldn't get latest commit for org.mozilla.firefox.Locale
I’m guessing most of these messages are caused by the first two. So now is the question what is wrong in my setup? Do I really have to re-install Aurora?
Who can help me with this?
I have just re-installed Aurora because Discover once again refused to start. Yesterday it kinda worked, meaning it did start and I could use it, but in my taskbar a new icon was placed during the time the program ran, instead of marking the pinned icon I placed there.
To be honest, in the first install I also could use Discover for a while until 3-4 days ago it stopped working.
I installed Aurora while keeping my complete /home disk so it all went very fast, maybe 10 minutes for the base software and another 10 minutes for the flatpaks. I sure hope it will now keep working.
Thanks.
1 Like