Bug 401334

Can you try running "plasma-discover --list-backends" and tell us what's the output?

(In reply to Aleix Pol from comment #1)
> Can you try running "plasma-discover --list-backends" and tell us what's the
> output?

plasma-discover --listbackends
Available backends:
 * fwupd-backend
 * packagekit-backend
 * flatpak-backend
 * kns-backend
 * snap-backend

Weird, that shouldn't happen when you have those app backends installed.

Can't reproduce on Neon dev unstable myself.

output from console:
plasma-discover 
Using Wayland-EGL
Using the 'xdg-shell-v6' shell integration
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/TextField.qml:57:21: Unable to assign [undefined] to QQmlComponent*
adding empty sources model QStandardItemModel(0x55ee8dbdd7a0)
no packages for "org.kde.plasma.systemloadviewer"
no packages for "org.kde.plasma.showActivityManager"
no packages for "org.kde.plasma.grouping"
no packages for "org.kde.plasma.diskquota"
no packages for "org.kde.kscreen"
no packages for "org.kde.plasma.kimpanel"
no packages for "audoban.applet.separator"
no packages for "org.kde.plasma.timer"
no packages for "im.riot.webapp"
no packages for "org.kde.plasma.appmenu"
no packages for "org.kde.plasma.quicklaunch"
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation."
qml: error No application back-ends found, please report to your distribution.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:113: TypeError: Cannot read property 'globalToolBarItem' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:114: TypeError: Cannot read property 'globalToolBarItem' of null
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"

Also experiencing this on Neon Dev Unstable. Here's the output of running `plasma-discover`:

~ plasma-discover
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation."
adding empty sources model QStandardItemModel(0x55c781ba1360)
no packages for "org.kde.plasma.systemloadviewer"
no packages for "timeshift.desktop"
no packages for "org.kde.plasma.showActivityManager"
no packages for "org.kde.plasma.grouping"
no packages for "org.kde.plasma.diskquota"
no packages for "org.kde.kscreen"
no packages for "org.gnupg.scdaemon"
no packages for "org.kde.plasma.kimpanel"
no packages for "audoban.applet.separator"
no packages for "org.kde.plasma.timer"
no packages for "im.riot.webapp"
no packages for "org.kde.plasma.appmenu"
no packages for "org.kde.plasma.quicklaunch"
qml: error No application back-ends found, please report to your distribution.
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"

Alexander, you've been reporting other bugs where you clearly have a backend. What happened here?

I'm reporting bugs of the Discover - it's initially displays 'No application back-ends found...' screen)

Created attachment 116899 [details]
Discover when launched with --backends packagekit-backend

Created attachment 116900 [details]
Discover when launched without --backends packagekit-backend

This appears to be a problem with discover not loading available backends by default. `plasma-discover --listbackends` shows that I do have backends available, and launching with `plasma-discover --backends packkagekit-backend` shows the desired featured screen on launch. 

I've attached screenshots of these behaviors.

Chase Lau, which distro are you on? Can you run discover from a terminal and show us the output you get?

Aleix,

I'm running KDE Neon Dev Unstable. I posted the output of `plasma-discover` in comment 5

Here's the output from `plasma-discover --backends packagekit-backend`

~ plasma-discover --backends packagekit-backend
adding empty sources model QStandardItemModel(0x55f15472d230)
no packages for "org.kde.plasma.systemloadviewer"
no packages for "timeshift.desktop"
no packages for "org.kde.plasma.showActivityManager"
no packages for "org.kde.plasma.grouping"
no packages for "org.kde.plasma.diskquota"
no packages for "org.kde.kscreen"
no packages for "org.gnupg.scdaemon"
no packages for "org.kde.plasma.kimpanel"
no packages for "audoban.applet.separator"
no packages for "org.kde.plasma.timer"
no packages for "im.riot.webapp"
no packages for "org.kde.plasma.appmenu"
no packages for "org.kde.plasma.quicklaunch"
Could not resolve property : #a

Looks like a packaging issue.

jr@merkin:~>ldd /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so
        linux-vdso.so.1 (0x00007ffcccbd6000)
        libDiscoverCommon.so => not found
        libpackagekitqt5.so.1 => /usr/lib/x86_64-linux-gnu/libpackagekitqt5.so.1 (0x00007f531a301000)
        libKF5KIOCore.so.5 => /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 (0x00007f5319f7c000)
...

compiling master manually shows this problem.

Running a Git bisect to track it down it says

There are only 'skip'ped commits left to test.
The first bad commit could be any of:
b946520f6b3872d428781da0cc9bfc068d7501c1
c2c5c833c0c73ac9009f00412dfb75c25d8e433a
4c003d441a175a8536b0fdc7a5a403851e43ac54
5aa9988402b30ef7c2aae66cbf23982ea2a024bd
4d1d585e2392e098505ffa7734a25d32bd2e1ead
e81d0d1bca83a61fd4c296939e9378311398eec2
99c93102b1184c35c3e7c2274379456de4a49f23
We cannot bisect more!

Discover does load the backends if I revert commit
b946520f6b3872d428781da0cc9bfc068d7501c1

That doesn't make much sense, as it means that this from PackageKitBackend returns false:
        bool hasApplications() const override { return true; }

Can you still see this? This is very weird...

author	Dan Leinir Turthra Jensen <admin@leinir.dk>	2019-01-15 09:18:29 +0000
committer	Dan Leinir Turthra Jensen <admin@leinir.dk>	2019-01-15 09:18:29 +0000
commit	798514c1166823846e64cb8e5ca7608db8051ae3 (patch)
tree	786741f0f923de3c84a335336fdddfd881419c54
parent	b59109351a1e69b045340be3051bdc9161fce059 (diff)
Fix premature firing of allInitialized signal
In case this is in fact the first backend to be added, and also
happens to be pre-filled, we still need for the rest of the
backends to be added before trying to send out the initialized
signal. To ensure this happens, this patch schedules it for the
start of the next run of the event loop, and ensures that it
only happens if there are no more backends to initialise.

Specifically, this happens if e.g. the fwupd backend is the
first to be initialised, and results in (amongst other things)
that the application loads up and insists that there are no
application backends.

Differential Revision: https://phabricator.kde.org/D18246
BUG: 401334
Diffstat
-rw-r--r--	libdiscover/resources/ResourcesModel.cpp	14