Lucien_Lachance i dont know when this started as i dont use discover very often, but it simply wont start. nothing at all happens when clicking the icon, and starting it from terminal yields no output at all Operating System: Solus 4.7 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.12.12-313.current (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 9800X3D 8-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: ASUS
BuzzPCSOS Lucien_Lachance Try running sudo eopkg install --reinstall discover sudo eopkg up -y flatpak update -y && flatpak remove --unused -y That usually seems to fix it.
AlphaElwedritsch I have no problems with approximately the same system settings. Also plasma with wayland....on newest updates
BuzzPCSOS Lucien_Lachance Worth a try, that is my usual fix for Discover. There was some general fixes for Discover mentioned here. Discover on my Plasma computers ran fine although I did notice that it seemed to take more CPU resources than usual. Running Intel CPU here, I wonder if it might be an AMD thing. Seeing if everything else is working right would be a good sanity check.
Lucien_Lachance BuzzPCSOS i actually already tried the stuff in that post, no change everything else is working as expected
Lucien_Lachance hmm seems plasma-discover was a running process, after killing it i got some output org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true adding empty sources model QStandardItemModel(0x55c29fa4dcd0) but still nothing happening
AlphaElwedritsch My working one: org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false adding empty sources model QStandardItemModel(0x558afd6c1960) Try following: Be sure that all sessions are killed Start with a dedicated backend pkill discover plasma-discover --backends packagekit-backend Or dedicated mode pkill discover plasma-discover --mode Browsing
Lucien_Lachance AlphaElwedritsch hmm ive deleted everything related to discover from the .cache dir, as well as any config file i could find no change thanks for your help though
Lucien_Lachance AlphaElwedritsch hey that worked ! im getting this output though org.kde.plasma.discover: couldn't open file "/home/USERNAME/.cache/discover/featured-5.9.json" "No such file or directory" PackageKitBackend: No distro component found for "us.getsol.solus" AppStreamIntegration: No distro component found for "us.getsol.solus" qrc:/qt/qml/org/kde/discover/qml/SourcesPage.qml:11:1: QML SourcesPage: Created graphical object was not placed in the graphics scene.
MikeK61 AlphaElwedritsch plasma-discover --backends packagekit-backend did the trick. org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false adding empty sources model QStandardItemModel(0x5605fb514880) QObject::startTimer: Timers cannot have negative intervals qrc:/qt/qml/org/kde/discover/qml/BrowsingPage.qml:17:1: QML BrowsingPage: Created graphical object was not placed in the graphics scene. PackageKitBackend: No distro component found for "us.getsol.solus" qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile AppStreamIntegration: No distro component found for "us.getsol.solus" Thank you very much.
pomon And will it start that way: QT_STYLE_OVERRIDE=Fusion plasma-discover or QT_STYLE_OVERRIDE="" plasma-discover
BuzzPCSOS Lucien_Lachance I know this is basic but have you tried turning it off and then back on again? Fixes so many unsolvable computer conundrums.
Lucien_Lachance plasma-discover --backends packagekit-backend i like this, seems to prevent it from checking flatpaks (which i dont use and have no interest in) AND prevents it from checking the kde store, so much faster, and none of that junk i never wanted anyway. better than it ever was
BuzzPCSOS Lucien_Lachance Does it still fail when using the original shortcut? plasma-discover --backends packagekit-backend just starts Discover without Flatpak and Firmware update functions enabled. Maybe an error on one of those two modules that was causing the original crash? This weeks update incorporated a patch to prevent Flatpak failed error messages when booting. Perhaps this update was related to the crash on your system. Flatpak removal caused the error? Just thinking out loud here. Half the joy of fixing is knowing what the fault was when you fix it.
Lucien_Lachance BuzzPCSOS yeah still doesent start withouth the backend bits. dont want the other backends so im fine
Lucien_Lachance now it works without the backends parameter, dont know why, must have been one of the recent updates that fixed something cos i didnt do anything to make it work. ill stick with the parameters though cos i dont want flathub and stuff anyway
MikeK61 I just found another solution on KDE forums start with following params in terminal. plasma-discover --backends packagekit,snap,fwupd,flatpak,kns
