Hi, I expect that you have akonadi-backend-sqlite installed.
Get logs why the migrator is failing: QT_LOGGING_RULES="*.*=true" akonadi-db-migrator --newengine sqlite A last recommend, maybe appmor profile is not uptodate, so put it in complain mode: aa-complain usr.bin.akonadiserver mariadbd_akonadi (to enforce it afterwards use aa-enforce) Regards, hefee -- On Samstag, 21. Dezember 2024 19:00:45 MEZ Martin Steigerwald wrote: > Hi Frank, hi. > > Frank Mehnert - 21.12.24, 18:02:36 MEZ: > > I tried the migration from MySQL to Sqlite3 and failed: > > > > I upgraded everything to current unstable. > > Did you restart the session or the computer afterwards? > > > I started `akonadi-db-migrator --newengine sqlite`. > > The assistant started and executed all steps, then tried to finish and > > aborted with a core dump. MySQL is still running. > > […] > > > Any hints? > > Unfortunately no as I did not use the migrator. A core dump is unexpected > to say the least. > > Except for asking upstream about it on kdepim-users or reporting a bug on > with upstream¹ *if* none about this is reported already. As KDEPIM should > 24.12 on your system, I think it would be okay to report directly to > upstream. Of course for that it is good you have debug packages set up so > the core dump would be useful. > > In case you find anything, please let us now. > > [1] https://bugs.kde.org > > Best,
signature.asc
Description: This is a digitally signed message part.