kde crashes; possibly involves kglobalaccel5, intel microcode update

[Peter_Brandon]

Thanks 1fallen!

I realized that I could switch to Gnome desktop today and tried that. But the suspend issue persists. I thought for a moment that meant that KDE wasn't involved, but this time the crash report was for drkonqi, the KDE crash handler (ironically). I guess it's still active even when I have Gnome as my desktop. One thing that's odd about all this is that each crash seems to generate a different report or pair of reports.

The syslog under the gnome crash seems to show the same pattern as for the crashes in KDE: the system tries to go to sleep, it thus seeks to deactivate my network (network manager and modem manager), as it's trying to do that something tells the system to not suspend, it tries to recover, and my existing user session crashes. Tried to reinstall all the network / modem manager software, but this had no effect.

[#&thj^%]

Gnome and Plasma has know issues.
If your going to use multiple desktops>> Create another user so things don't mix between the two.
Gnome user and KDE user, you'll find it a bit more rewarding
One question I've been dying to ask, have you just tried screen-lock instead of suspend.
I'll also use "dm-tool lock"

Locking Screen with LightDM

The LightDM display manager provides dm-tool to allow us to lock the screen from the command line

dm-tool lock

A similar command will also lock the screen and switch to the display manager's login screen.

 dm-tool switch-to-greeter

[Peter_Brandon]

Hi 1fallen: I never use screen lock.

[#&thj^%]

So just suspend? It was kind of a tip for your suspend issues.
Has it improved with Gnome?

[SeijiSensei]

You could consider giving Neon a try in a virtual machine. You can install virtualbox from the repositories, or install the armament required to run "kernel virtual machines" or KVM. Here's the guide I followed: https://phoenixnap.com/kb/ubuntu-install-kvm

I just bit the bullet and installed Neon from the most recent ISO image: https://neon.kde.org/download

[Peter_Brandon]

I found a solution to my problem.

I switched to the lightdm display manager (from sddm), which made it easier to identify the problem because the system wouldn't crash when I suspended, it would simply come out of suspend. I then looked at every available system log and, in the authentication log, I found this: systemd-logind Error during inhibitor-delayed operation (already returned success to client): Unit nvidia-suspend.service is masked. This error occurred right between my system was putting various things to sleep and, for no apparent reason, suddenly waking them back up.

That then led me to this discussion of how to fix nvidia-suspend problems: https://gist.github.com/bmcbm/375f14...4bdbbebbcfd029 . Reading between the lines of that, I discovered that there were several broken symlinks found with: ls /etc/systemd/system/systemd* . I'm using nvidia-470, and I think the broken symlinks are from earlier versions. I disabled these symlinks (renamed them). Viola, my system is able to suspend without incident for the first time in months.

Would be nice if nvidia were to be more careful with their driver installers and Ubuntu didn't bury the relevant error message in the authentication log.