(In reply to Peter from comment #0)
> ***
> If you're not sure this is actually a bug, instead post about it at
> https://discuss.kde.org
> 
> If you're reporting a crash, attach a backtrace with debug symbols; see
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports
> 
> Please remove this comment after reading and before submitting - thanks!
> ***
> 
> SUMMARY
> Since today's (17 August 2025) update, Kmail, Korganizer and Kontact won't
> start, giving the message ""Personal information management service is
> starting" and then "A required backup service is not operational".  
> 
> In a terminal, 'akonadictl stop' gives "Akonadi is not running" immediately
> followed by 'akonadictl start' gives "Akonadi is already running". 
> 'akonadictl status' reports 
> "Akonadi Control: stopped
> Akonadi Server: running
> Akonadi Server Search Support: available (Remote Search)"
> 
> STEPS TO REPRODUCE
> 1. Select Kmail, Korganizer or Kontact
> 2. Run akonadictl as described above.
> 
> 
> OBSERVED RESULT
> Kmail, Korganizer and Kontact won't start, giving the message ""Personal
> information management service is starting" and then "A required backup
> service is not operational".  
> 
> EXPECTED RESULT
> Applications should start normally.  
> 
> SOFTWARE/OS VERSIONS
> 'kinfo' reports
> ERROR:             VkInstanceCreateInfo::pApplicationInfo::apiVersion has
> value of 0 which is not permitted. If apiVersion is not 0, then it must be
> greater than or equal to the value of VK_API_VERSION_1_0
> [VUID-VkApplicationInfo-apiVersion]
> Operating System: KDE neon User Edition
> KDE Plasma Version: 6.4.4
> KDE Frameworks Version: 6.17.0
> Qt Version: 6.9.1
> Kernel Version: 6.14.0-27-generic (64-bit)
> Graphics Platform: Wayland
> Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
> Memory: 8 GiB of RAM (7.5 GiB usable)
> Graphics Processor: Intel® Iris® Xe Graphics
> 
> 
> 
> ADDITIONAL INFORMATION

BTW, if I click on "Details", to get further information, nothing happens.

I found what sounds like the same problem for ArchLinux ( https://lists.archlinux.org/archives/list/arch-general@lists.archlinux.org/thread/F4IPTWJZVYWAU5YTVKVIOG5NGJMONV5K/ ).  

The recommendation is to remove knotes and akonadi-notes .  For KDE Neon, I don't see akonadi-notes, so I removed kpim6-akonadi-notes instead.  Doesn't seem to work, though.

I found what sounds like the same problem for ArchLinux ( https://lists.archlinux.org/archives/list/arch-general@lists.archlinux.org/thread/F4IPTWJZVYWAU5YTVKVIOG5NGJMONV5K/ ).  

The recommendation is to remove knotes and akonadi-notes .  For KDE Neon, I don't see akonadi-notes, so I removed kpim6-akonadi-notes instead.  Doesn't seem to work, though.  

Any help much appreciated!

Were you able to solve this in some way?

(In reply to Steffen W. from comment #4)
> Were you able to solve this in some way?

Hi Steffen,

The problem persisted after a couple of reboots.  I then deleted knotes and kpim6-akonadi-notes.  At first nothing changed,  even after stopping and starting akonadi, and killing and restarting a few processes.  Seems to now work after a reboot, though.  Whether it was deleting knotes and kpim6-akonadi-notes that made the difference, I don't know.  

Have you been having the same problem?  

P

Yes and I managed to fix it as well. Not sure how though, no reboots were involved.

https://bugs.kde.org/show_bug.cgi?id=508515

After digging into my journalctl a bit it seems like Akonadi has a weird logic where it doesn't fully restart until it was stopped a couple of times. Once that happened and the two packages were no longer on my system it worked though. This really needs to be fixed, at the very least a proper error message needs to be displayed, the current error message's Details button needs to work and if programs get abandoned there needs to be some kind of announcement that is visible to endusers.

https://bugs.kde.org/show_bug.cgi?id=508594 seems to be related, potentially even the same issue with slightly different behavior (gets stuck in migration)

See also https://discuss.kde.org/t/akonadi-migration-agent-stops/38814

> The problem persisted after a couple of reboots.

Same for me, on a PC and a Laptop running KDE neon.

>  I then deleted knotes and kpim6-akonadi-notes.

Yep, this and a reboot just did the trick for both of my systems too...

*** Bug 508594 has been marked as a duplicate of this bug. ***

*** Bug 509069 has been marked as a duplicate of this bug. ***

Why was this marked as resolved and fixed? This bug report contains at the very least three issues that need to be fixed.
 - the non working button
 - Akonadi not working just because of one outdated module
 - unclear error message by applications that use Akonadi as to why they aren't working

*** Bug 508515 has been marked as a duplicate of this bug. ***

because I consider this a distro packaging error.
but I won't fight if you want to reopen. not sure what we can do about it from the source code -- maybe someone has an idea

Ah, fair enough. You have more knowledge in this regard than me, I was just a bit irritated as there was no reason given why the bug was marked solved. 

With that being said, is the non-working Details button also due to a packaging error?

Hi Peter, Allan,
I noticed that I could change the product form akonadi to 'kde neon'.  Maybe that's the right thing to do to trigger Harald and Jonathan as
well as keeping track of the bug.    Allan, is that okay?  (and thx to Allan for redirecting my bug report to this bug)

At least todays upgrade kde neon pkg upgrade did not fix the problem for me (akonadi running but no PIM app can connect.

[I] ~►dpkg -l akonadi\* kmail korganizer                                                                                                   14.424s 09:46
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                   Version                                      Architecture Description
+++-======================-============================================-============-====================================
ii  akonadi-backend-mysql  4:25.08.0-0zneon+24.04+noble+release+build50 amd64        MySQL storage backend for Akonadi
un  akonadi-backend-sqlite <none>                                       <none>       (no description available)
un  akonadi-contacts-data  <none>                                       <none>       (no description available)
un  akonadi-import-wizard  <none>                                       <none>       (no description available)
un  akonadi-mime-data      <none>                                       <none>       (no description available)
ii  akonadi-server         4:25.08.0-0zneon+24.04+noble+release+build50 all          Dummy transitional
ii  kmail                  4:25.08.0-0zneon+24.04+noble+release+build38 amd64        full featured graphical email client
ii  korganizer             4:25.08.0-0zneon+24.04+noble+release+build37 amd64        calendar and personal organizer

FYI KDE Neon User:   KDE PIM apps could connect to akonadi here again after the suggested  (my luck I don't use knotes)

  apt purge knotes kpim6-akonadi-notes

Afterwards

  akonadictl start
  akonadictl stop

worked as expected and starting kmail/korganizer started akonadi themself again in the background and connected to it.

(In reply to Achim Bohnet from comment #15)
> Hi Peter, Allan,
> I noticed that I could change the product form akonadi to 'kde neon'.  Maybe
> that's the right thing to do to trigger Harald and Jonathan as
> well as keeping track of the bug.    Allan, is that okay?  (and thx to Allan
> for redirecting my bug report to this bug)

correct

Git commit 9cc24359c9944295d9baa94792b104942d4eb121 by Carlos De Maine.
Committed on 04/09/2025 at 13:47.
Pushed by carlosdem into branch 'Neon/release'.
Conflicts: kpim6-akonadi-notes, knotes

M  +1    -0    debian/control

https://invent.kde.org/neon/kde/akonadi/-/commit/9cc24359c9944295d9baa94792b104942d4eb121