Bug 1226386 - Akonadi doesn't start after upgrade from Leap 15.5 to Leap 15.6
Summary: Akonadi doesn't start after upgrade from Leap 15.5 to Leap 15.6
Status: NEW
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: KDE Applications (show other bugs)
Version: Leap 15.6
Hardware: x86-64 openSUSE Leap 15.5
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-15 12:09 UTC by Thomas Formella
Modified: 2024-06-20 13:05 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Formella 2024-06-15 12:09:03 UTC 
Akonadi doesn't start after an upgrade from Leap 15.5 to Leap 15.6 and therefore all programs relying on Akonadi (i.e. Kontact, KMail) won't start either.
After an "akonadictl start", the Akonadi server exits with "exit code: 1" and "Unknown error".
Possibly it has to do with an upgraded database engine? 
Anyway, deleting 
~/.local/share/akonadi/db_data/ib_logfile0, then creating an empty file with "touch ~/.local/share/akonadi/db_data/ib_logfile0" and then "akonadictl start" solves the problem on my system.
Comment 1 Fabian Vogt 2024-06-16 11:34:38 UTC 
> Possibly it has to do with an upgraded database engine? 

Full logs would be useful.

Can you still reproduce the issue? If not, I'm afraid we'll have to close this as WORKSFORME, as there's no way to confirm the cause.
Comment 2 Thomas Formella 2024-06-20 13:05:25 UTC 
(In reply to Fabian Vogt from comment #1)
> > Possibly it has to do with an upgraded database engine? 
> 
> Full logs would be useful.
> 
> Can you still reproduce the issue? If not, I'm afraid we'll have to close
> this as WORKSFORME, as there's no way to confirm the cause.

Sorry, I had to get my Kmail working again as fast as possible, therfore no more logs available.

As fas as I remember, it was the same output as mentioned in this bugreport:
https://bugs.kde.org/show_bug.cgi?id=454948

This bug seems to be around for several years and across several distributions btw.