Created attachment 123449 [details] plasma-discover --mode update worked but it printed many errors. SUMMARY I have updated Plasma from 5.16.5 to 5.17.1. Since then I cannot start Discover anymore. The icon appears jumping, then stops jumping and the window does not display the discover app but only a screenshot of the background. Additional information: I could open Discover in the terminal with "--mode update", however there are some errors printed. Please see attached log. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1
There are only those lines in the terminal log: > qrc:/qml/Feedback.qml:2:1: module "org.kde.userfeedback" is not installed > qrc:/qml/DiscoverDrawer.qml:74:17: QML AbstractApplicationHeader: > Detected anchors on an item that is managed by a layout. > This is undefined behavior; use Layout.alignment instead. > qrc:/qml/DiscoverDrawer.qml:74:17: QML AbstractApplicationHeader: > Detected anchors on an item that is managed by a layout. > This is undefined behavior; use Layout.alignment instead. But maybe they give you a hint.
Created attachment 123896 [details] Video of the issue. Plama-Discover still does not work in 5.17.3 for me and neither the the git custom build. All other apps work fine though.
(In reply to Postix from comment #1) > There are only those lines in the terminal log: > > > qrc:/qml/Feedback.qml:2:1: module "org.kde.userfeedback" is not installed That's the problem. What's going on here is that you're actually using the 5.18/git master version of Discover which pulls in the user feedback UI, but you don't have the KUserFeedback module that provides it installed. It was added as a dependency in 5.18. In other words, this is a local configuration issue, and not something users are exposed to. Since you've got git builds of stuff, try building the kuserfeedback framework and launching Discover again.
> That's the problem. What's going on here is that you're actually using the 5.18/git master version of Discover which pulls in the user feedback UI, but you don't have the KUserFeedback module that provides it installed. It was added as a dependency in 5.18. Unfortunately it seems not to be related. Those messages were indeed from the git build, but are not found in the package build 5.17.3 of Manjaro.
Created attachment 123897 [details] plasma-discover terminal output I should have been more patient. Discover (5.17.3) indeed starts after waiting for ~20 seconds with the terminal output attached. Any idea why it takes so long?
Taking a look at the terminal output respectively the warning displayed: > Fwupd Error 20 Fehler beim Aufruf von StartServiceByName für org.freedesktop.fwupd: > Failed to activate service 'org.freedesktop.fwupd': > timed out (service_start_timeout=25000ms) > qml: message: Fehler beim Aufruf von StartServiceByName für org.freedesktop.fwupd: > Failed to activate service 'org.freedesktop.fwupd': > timed out (service_start_timeout=25000ms) plus stopping the time and doing the math: Discover takes pretty much exactly 25 seconds to start due to this service start timeout. :-/
Yikes. So fwupd is timing out after failing to initialize properly, or something.
(In reply to Nate Graham from comment #7) > Yikes. So fwupd is timing out after failing to initialize properly, or > something. Right, it's kind of this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941661 though it's actually not fixed or broken again in 1.3.3-1. :) Anyway, Discover should start with or w/o fwupd as it would start as when it is not installed at all. It may reinitialize the fwupd module later if it should finally start within the timeout. The current situation is not ideal.
Edit to my above post*: It's not exactly this bug, but almost: > Nov 13 18:02:51 pc systemd[10036]: > fwupd.service: Failed to execute command: No such file or directory > Nov 13 18:02:51 pc systemd[10036]: > fwupd.service: Failed at step EXEC spawning /usr/lib/fwupd/fwupd: > No such file or directory > Nov 13 18:02:51 pc systemd[1]: > fwupd.service: Main process exited, code=exited, status=203/EXEC * When will the time come that you can finally edit your posts and use markdown in Bugzilla? ;)
Cannot reproduce it anymore.