Bug 397123

Summary: Plasma Discover 5.13.4; KNSRC3 error; "Config group not found! Check your KNS3 installation."
Product: [Applications] Discover Reporter: ed.r.bakker
Component: discoverAssignee: Aleix Pol <aleixpol>
Status: RESOLVED WORKSFORME    
Severity: critical CC: ed.r.bakker
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: backtrace of plasma-discover snapd backend going haywire...

Description ed.r.bakker 2018-08-03 11:30:36 UTC 
Starting plasma-discover from konsole:

gaytan@iNucNeon:~$ plasma-discover
QQmlComponent: Created graphical object was not placed in the graphics scene.
qml: Warning: ToolbarApplicationHeader is deprecated, remove and use the automatic internal toolbar instead.
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."
falling back applications backend to 0
setting currentApplicationBackend PackageKitBackend(0x2889be0)
could not find "org.kde.krita.desktop" "krita.desktop"
could not find "org.kde.krita.desktop" "krita.desktop"
org.kde.knewstuff.core: Could not find category "Calligra Flow Stencil"
invalid kns backend! "/etc/xdg/calligra_stencils.knsrc" because: "All categories are missing"
Discarding invalid backend "calligra_stencils.knsrc"
falling back applications backend to 0
kns error "/etc/xdg/calligra_stencils.knsrc" "Invalid Calligra_stencils backend, contact your distributor."
could not find "org.kde.krita.desktop" "krita.desktop"

When I uninstall Calligra completely, (I don't need Calligra really..), I do get the same error message when starting Plasma-Discover from terminal, but ... when I then go to 'Applications' section and I 'dare' clicking 1 application (description), then Plasma Discover hangs as a rock!

That's why I reinstalled Calligra suite; when I then start Plasma-Discover from Konsole and go to 'Applications' section and click on a description (random application), nothing hangs and all keeps working...

Why the Krita error? I did not have Krita installed when I first saw the 'Krita error'. Decided to install Krita on my Intel iNuc to see if that would change anything but no... still org.kde.krita.desktop not found error as well, when starting Plasma-Discover from Konsole...

I did see yesterday that earlier Plasma-Discover versions also had filed bugs about the 'Check your KNS3 installation', but don't know if those bugs were similar to this one....
Comment 1 Aleix Pol 2018-08-03 14:28:02 UTC 
> could not find "org.kde.krita.desktop" "krita.desktop"

This line just means that krita isn't available on your distribution. Same for the rest of similar lines. You claim to be using Neon, it seems you maybe have a broken system maybe? you can refresh your appstream metadata with "sudo appstreamcli refresh".


It would be useful to get a backtrace of your frozen system to see where it's stuck.
https://wiki.ubuntu.com/Backtrace
Comment 2 ed.r.bakker 2018-08-03 15:29:10 UTC 
Created attachment 114287 [details]
backtrace of plasma-discover snapd backend going haywire...

Thanks for your info.

By the way, my KDE Neon Plasma seems to function properly and does not seem broken to me...

I have reinstalled the flatpack AND snappack backend both in Plasma-Discover; did the things asked via the gdb program and managed to upload a backtrace here... Let me know if it's of any meaning / value to you please.

Shared the file via Dropbox!
Comment 3 ed.r.bakker 2018-08-05 20:33:52 UTC 
Hey, did you get my backtrace after all?
Hope I was able to provide you with useful information!
Comment 4 Aleix Pol 2018-08-06 14:33:46 UTC 
Can you try running with "G_DEBUG=fatal-criticals" environment variable? This way maybe we'll get to know what's offending glib.

It should crash, that backtrace will be more useful.

Thanks for your patience!
Comment 5 Christoph Feck 2018-08-30 20:41:15 UTC 
If you can provide the information requested in comment #4, please add it.
Comment 6 Christoph Feck 2018-09-13 15:01:40 UTC 
To further investigate this issue, KDE developers need the information requested in comment #4. If you can provide it, or need help with finding that information, please add a comment.
Comment 7 Andrew Crouthamel 2018-09-30 02:44:37 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-11-01 18:47:47 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!