After applying the fix for Discover in 5.12 I'm getting an error on launch, but it looks that it works properly.

Code: Select all

dario in ~ λ 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."
Discarding invalid backend "ksysguard.knsrc"
Discarding invalid backend "servicemenu.knsrc"
setting currentApplicationBackend PackageKitBackend(0x2dad1a0)
org.kde.knewstuff.core: Could not find category "KAddressbook Theme"
invalid kns backend! "/etc/xdg/kaddressbook_themes.knsrc" because: "All categories are missing"
Discarding invalid backend "kaddressbook_themes.knsrc"
qrc:/qml/DiscoverDrawer.qml:145: TypeError: Cannot read property 'name' of null
kns error "/etc/xdg/kaddressbook_themes.knsrc" "Invalid Kaddressbook_themes backend, contact your distributor."
qml: message: kaddressbook_themes.knsrc: Invalid Kaddressbook_themes backend, contact your distributor.
org.kde.knewstuff.core: Could not find category "Xfce Icon Theme"
invalid kns backend! "/etc/xdg/cgcicon.knsrc" because: "All categories are missing"
Discarding invalid backend "cgcicon.knsrc"
qrc:/qml/DiscoverDrawer.qml:145: TypeError: Cannot read property 'name' of null
qrc:/qml/DiscoverDrawer.qml:145: TypeError: Cannot read property 'name' of null
kns error "/etc/xdg/cgcicon.knsrc" "Invalid Cgcicon backend, contact your distributor."
qml: message: cgcicon.knsrc: Invalid Cgcicon backend, contact your distributor.
QObject::~QObject: Timers cannot be stopped from another thread


Reinstall the entire system. I had a problem with the disappearing menubar in all windows. After a short time, new problems began to appear, I had broken / no icons in most windows, etc. Problems also began to appear after the upgrade to KDE 5.12. It seems that the upgrade to 5.12 spoiled a lot of things.

After clean installing the system again, everything works as it should.

Update 09.02.2018

I do not want to be rude, but updates should fix problems and not create next ones. After clean installation of the system, everything worked as it should. After some time, the system downloaded more updates and problems again.

I just praised that after clean installation of the system everything works without a hitch.

What has become a care about the stability of this system? Why does it look like nobody checked updates before releasing?

Had to sign up to pitch in on this one. My KDE has been acting a little strange the past few days and I can't seem to find a cause or fix.

I get the same cgcicon error when opening the updater, but auto-hide on my taskbar has started acting up quite a bit as well where it will restore and stay up whenever I change windows, and will disappear and reappear every couple of seconds when mousing over it.

I'm on a fairly vanilla Kubuntu 17.10 install. I can provide more details if it would be of any help.

Reinstall is not a solution, it's just workaround to avoid finding the real solution.

I don't have any problems with stability after an upgrade, this (Neon LTS) is the most stable Linux system I used in past 2 years (and I did upgrade from 5.8 to 5.12, not clean 5.12 install obv). The only issue I see is annoying toast message on starting of the Discover (and that is hardly a reason to do reinstall). Also, this is my production machine, it's under load 9 - 13 hours a day. So big thanks to people behind Neon project as it's a Breeze to work on this kind of system.

I am on Neon User Edition, no problems at all.

notdario wrote:Reinstall is not a solution, it's just workaround to avoid finding the real solution.

It depends on the situation. In my case KDE neon is my default sysytem. And after upgrading to 5.12, the system was becoming more unstable. The second issue of problems that were present in me was still unsolved.

I was delighted with this system. But after the 5.12 update, it makes me wonder if the next updates will not blow my system to the rest.

Hi!
I'm on Neon LTS and lately I've been having the same kind of issues.
When I open Discovery I get:
"...Invalid cgicon backend..."

and If I ask to check for updates I get a longer:
"...W: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://archive.neon.kde.org/user/lts xenial InRelease' doesn't support architecture 'i386'..."

and also a:
"...E: http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons is not (yet) available (Could not open file /var/lib/apt/lists/partial/security.ubuntu.com_ubuntu_dists_xenial-security_main_dep11_icons-64x64.tar.gz - open (13: Permission denied) [IP: 91.189.88.152 80])..."

If I run "pkcon refresh" from the konsole I get the same.

Apart from that, Discover seems to update the system normally. So I am a bit confused.

I work professionally with video editing and 3d animation, so my system is running at full load most of the time and I have to say that is the fastest, rock solid distro I have tried. I wouldn't like to reinstall it from scratch because my system is running like a charm. Any ideas?

KDE Neon LTS 5.12
Plasma version 5.12.1
KDE Frameworks version: 5.43.0
Qt version: 5.9.3

Thanks, Lalegion.

I don't want to be a complainer, because I love all the work and love that has been put into KDE by the people that work hard to maintain such a beautiful collection of software..
That being said.. As I upgraded from a stable KDE Neon 5.8 LTS to KDE Neon 8.12 LTS and have the same problem..

Discovery opens with a toast stating "cgcicon.knsrc: invalid cgcicon backend, contact your distributor."
After which, at the end of installing updates, Discovery tells me that it is checking for new updates.. but that screen never comes to a conclusion.. it just sits there with a blank stare in its eyes..

But for me personally, the most important thing that I've found is the plasmashell process that is eating memory until there is none left.. I've gotten used to pressing Meta + Z, which is my version of Ctrl + Z, but for plasma.. Meta + Z runs a script that kills the plasmashell process and restarts it again.
I was in need of using such a script somewhere between KDE Neon 5.8.2 LTS (is where I discovered KDE) and 5.8.5 because the shell would regularly crash or hang sometimes.. but as updates came in, KDE Neon became more and more stable.. I actually had a very stable system for quite some time..
With KDE Neon 8.12 LTS, plasmashell is being naughty in a new way..

This experience has redefined my --erroneous-- assumption of what LTS suppose to mean.. I reminded myself that LTS stands for long term support, that this has to do with things like duration of support and the focus on bug fixes instead of features, and this is not the same as being rigorously tested before release.

I love KDE, and love advocating for it. But based merely on my personal experience, I feel that 5.12 LTS was maybe released a bit too soon. Not because of Discovery, but because of the plasmashell being unstable again. (see viewtopic.php?f=289&t=151102 for more details)

But enough about that.. instead of me complaining, lets see if I can add something to the conversation and maybe offer some solutions or ideas..

I didn't find anything on the subject before, but today I found this: https://www.mail-archive.com/kde-bugs-d ... 13000.html
Which inspired me to temporarily move file /etc/xdg/cgcicon.knsrc to a different location..

I also moved /etc/xdg/kdenlive_projectprofiles.knsrc because it contains a ProvidersUrl variable set to https://kdenlive.org/data/mltprofilesources.xml which returns a 404.. and therefore this .knsrc is also reporting trouble..

Discovery stopped giving me errors.. BUT.. this is not an actual solution because all I did was simply removing components.. it didn't actually fix anything..

As cgcicon.knsrc is part of the "GTK2 and GTK3 Configurator for KDE", I figure I'm now unable to get new GTK Icon themes using of a GUI.. But I can live with that for the moment, as I see people already starting to notice the problem and a fix is prolly already underway..
I suspect these are just some growing pains going from 5.8 to 5.12..

I don't even use Discover, but apt instead; so I am not sure that this will help since I don't have this error. Have you tried reinstalling kaddressbook since that is what the dialogue complains about?

Code: Select all

sudo apt update
sudo apt install --reinstall kaddressbook

The log of the initial poster does mention 'kaddressbook', but as I understand it, the initial poster is talking about the error message in the screen shot ("cgcicon.knsrc").
Although he opens his post with the log, is seems to be there to supply extra information about the screen shot.