@carl I know I said, "you're probably right"...

#Qt5 #Linux #Kubuntu #Eaon

Oh, and the version of #Ruqola in the Git repo also looks for #KUserFeedback couldn't find it in #PIM #Kontact but perhaps I'm looking in the wrong place (;*

#KDE #Plasma #Eaon #Kubuntu

ASIDE: What is Rocket Chat‽:*

Meanwhile, the CMake files for #systemsettings make no mention of the #KUserFeedback library, I know, I looked and even built it from source myself, to check.

#Kubuntu #Eaon #Plasma #KDE

I find the new #KDE #Plasma 5.18 stuff slightly misleading, with regards to #KUserfeedback . The blurb mentions that systemsettings5 would have a new option for opting in to user feedback, but having installed from the backports PPA on #Eaon #Kubuntu and previously built the latest git version of #Kate the only app that uses KUserFeedback is the aforementioned Kate, and only because I downloaded and built the feedback library myself, it's an optional dependency in the CMake file, for Kate...

Just need to re-educate my eyes to not keep looking over to where #GKrellm used to be to see what the CPU is doing...

#Eaon #Kubuntu

On the bright side, I can read emails from GitHub and GitLab and other sites again in the newer #Evolution, the one that shipped with #Disco had decided that white text on a white background was the way to go, while this #Eaon version manages black text on a white background.

#Kubuntu

Don't think I've noticed one of these so far, so looks like getting rid of xdg-dexktop-proxy-gtk might have fixed that.

#Eaon #Kubuntu

Though there is mention that a newer version of xdg-desktop-proxy might fix a similar issue.

So far so good re: ACPI sensor issues, so I guess GKrellm was doing something that the kernel doesn't like.

#Eaon #Kubuntu

Might be #GKrellm -related, so I've got rid of it for the time being. Now with added zombie process, which is suggestive #Eaon #Kubuntu
Unfortunately also getting issues with reading temperature sensors #ACPI related stuff #Eaon #Kubuntu Which means the laptop may not shutdown properly later. Which I had hoped the newer kernel would have fixed, since I'd been getting the same issue with some of the #Disco kernels. Bugger¡:*