Since upgrading kde neon to jammy some three weeks ago akonadi does not work for me any more after waking from suspend. The issue is persistent after every wakeup. I have to restart the akonadi server and then manually enable all network related resources one by one. It won't recover itself otherwise.

I have the impression that akonadi is trying to restart before networkmananger has done its job.
Their startup logs are mangled and I see one entry like that for each akonadi resource:
akonadi_imap_resource[29138]: "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/5”"

I did not find anything related on the internet.
I don't even know how akonadi is controlled and restarted after a suspend.

Does anyone have an idea where and how I could start debugging this?

Looks like a PR has been created to fix this issue:
https://invent.kde.org/neon/extras/gran ... requests/1

I just installed the latest updates today: things work again.
Great! Thanks!

And, just a few days later, things are broken again.

It seems that things work fine right after a fresh boot, but that things fail after a suspend.

Working again just fine, as it looks. For about one week now.

Unbelievable.
I hesitated 2 full weeks to confirm that things work again.
Then I finally thought OK, that appears to be stable enough and did confirm.

Two hours later KDE Neon published an update and things were broken again.

I am experiencing the exact same issue on neon, makes Kmail almost unusable on a laptop.

I was already wondering if it's specific to me since I didn't see a bug report on it, but apparently I'm not the only one.

Same issue here. Whatever you do no NOT upgrade to 5.27.5 I just did, to try and fix this issue but Kontact is broken in this new version. It won't even launch.

viewtopic.php?f=215&t=177690

Beware!

Hi!

You should probably head over to https://discuss.kde.org/c/help/6, in particular this thread:

https://discuss.kde.org/t/on-kde-neon-k ... ction/1425

Cheers!