Bug 464278

Summary:	Database error when starting up Akonad console
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Natalie Clarius <natalie_clarius>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	CONFIRMED ---
Severity:	normal	CC:	drn+dev.report.bugs.kde
Priority:	NOR
Version:	5.22.0
Target Milestone:	---
Platform:	Other
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=464275 https://bugs.kde.org/show_bug.cgi?id=464277
Latest Commit:	https://bugs.kde.org/show_bug.cgi?id=464274	Version Fixed In:
Sentry Crash Report:
Attachments:	Error msesage #3 Error message #1 Error message #2

Description Natalie Clarius 2023-01-14 14:19:46 UTC

Created attachment 155284 [details]
Error msesage #3

SUMMARY
***
When opening up Akonadi console, I'm getting the below three error messages. Applications relying on Akonadi crash (see linked related reports). The first two errors seem are both database related, the third one may be something else. Let me know if I should open a separate bug report for that one.
***

STEPS TO REPRODUCE
1. Open Akonadi console

OBSERVED RESULT
1. Error message dialog with the text (see attached screenshot):
> "Failed to connect to database: Can't connect to local server through socket '/run/user/1000/akonadi/mysql.socket' (2) QMYSQL: Unable to connect
2. Error message dialog with the text (see attached screenshot):
> DatabaseCorruptError: Expected block 17 to be level 1, not 0
3. Akonadi console window opens
4. Error message overlay with the text (see attached screenshot):
> The Akonadi personal information management service is not operational.

EXPECTED RESULT
Not sure what that console should show me, but not nothing.

SOFTWARE/OS VERSIONS
akonadiconsole 5.22.1 (22.12.1)
Operating System: Arch Linux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.8
Kernel Version: 6.1.4-arch1-1 (64-bit)
Graphics Platform: X11

Comment 1 Natalie Clarius 2023-01-14 14:20:24 UTC

Created attachment 155285 [details]
Error message #1

Comment 2 Natalie Clarius 2023-01-14 14:20:44 UTC

Created attachment 155286 [details]
Error message #2

Comment 3 Natalie Clarius 2023-01-14 14:22:47 UTC

When running `akonadictl start` on the console, I'm getting the following:

 akonadictl start                                                                                           ❯natalie
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl:    done.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

 org.kde.pim.akonadiserver: Starting up the Akonadi Server...                                               ❯natalie
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial connection!
org.kde.pim.akonadiserver: executable: "/usr/bin/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/natalie/.local/share/akonadi/mysql.conf", "--datadir=/home/natalie/.local/share/akonadi/db_data/", "--socket=/run/user/1000/akonadi/mysql.socket", "--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2023-01-14 15:22:13 0 [Note] /usr/bin/mysqld (server 10.9.4-MariaDB) starting as process 179295 ...\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...

Comment 4 Natalie Clarius 2023-01-14 17:42:08 UTC

Deleting ~/.local/share/akonadi solved it.

I'll keep the old folder around for a bit in case someone wants me to try and test something.

Comment 5 Giorgi Gzirishvili 2023-06-12 15:02:37 UTC

This affects me as well. Renaming ~/.local/share/akonadi solves the issue, but this has all my notes, to-dos and other data in it, so I can't access them. Keep in mind: if you delete it, you'll lose your data. This is not a fix.