Has anyone else seen this?

I installed a fresh Neon 18.04 a week ago, although I'm pretty sure it was like this right at the start, just to make it clear, I've added a couple of PPAs (Vivaldi & Nvidia) and installed Vivaldi(stable), Steam, Deja dup, Gimp, Konversation and GUFW.

There is a bug report:

https://bugs.kde.org/show_bug.cgi?id=399647

Which implies Discover from 5.14.8 is good?

I'm kind of feeling this out as I'm new to the forum and not sure if I should add to the bug report and I'm curious why I couldn't find any reports of this in this forum yet.

[Edit]
I've tried pkcon and it shows the following:

Code: Select all

robert@Neon:/etc/apt/sources.list.d$ pkcon refresh --verbose --plain
11:14:51        PackageKit          Verbose debugging enabled (on console 1)
11:14:51        PackageKit          filter=(null), filters=0
11:14:51        PackageKit          adding state 0x56069f1560d0
11:14:51        PackageKit          role now refresh-cache
Transaction:    Refreshing cache
11:14:51        PackageKit          notify::connected
Status:         Waiting in queue
Status:         Waiting for authentication
Status:         Waiting in queue
Status:         Starting
Status:         Loading cache
Percentage:     0
Percentage:     100
Percentage:     0
Percentage:     50
Percentage:     100
Status:         Refreshing software list
Status:         Downloading packages
Percentage:     0
Status:         Running
Status:         Loading cache
Percentage:     100
Status:         Finished

Do you want to allow installing unsigned software? [N/y]

The unsigned software will not be installed.
11:15:03        PackageKit          declined request 1
11:15:03        PackageKit          remove state 0x56069f1560d0

I don't know how to read this - is this the problem - my system can't install the correct packagekit?), or is this a new packagekit that isn't signed yet (whatever this means in this case)?

And there's a Reddit post too with quite a few responses:

https://www.reddit.com/r/kde/comments/9 ... ed_things/

Problem has been solved on mine after this mornings updates on Neon Dev Stable 18.04. These are the files after the update:

discover/bionic,now 2.1.2-8 amd64 [installed]
discover-data/bionic,bionic,now 2.2013.01.11 all [installed,automatic]
libdiscover2/bionic,now 2.1.2-8 amd64 [installed,automatic]
plasma-discover/bionic,now 5.14.0+p18.04+git20181016.0050-0 amd64 [installed,automatic]
plasma-discover-common/bionic,bionic,bionic,now 5.14.0+p18.04+git20181016.0050-0 all [installed,automatic]
plasma-discover-flatpak-backend/bionic,now 5.14.0+p18.04+git20181016.0050-0 amd64 [installed,automatic]
plasma-discover-private/bionic,now 5.14.0+p18.04+git20181016.0050-0 amd64 [installed,automatic]
plasma-discover-snap-backend/bionic,now 5.14.0+p18.04+git20181016.0050-0 amd64 [installed,automatic]
plasma-discover-updater/bionic,now 5.14.0+p18.04+git20181016.0050-0 amd64 [installed,automatic]

This is the relevant bug report (there was another but marked as duplicate)

https://bugs.kde.org/show_bug.cgi?id=399647#c7