Bug 492607 - akonadi crashes with core dump
Summary: akonadi crashes with core dump
Status: RESOLVED DUPLICATE of bug 492547
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 6.2.0
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-03 16:52 UTC by Axel Braun
Modified: 2024-09-12 09:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
log of the dump (108.32 KB, text/plain)
2024-09-03 16:52 UTC, Axel Braun
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Braun 2024-09-03 16:52:02 UTC
Created attachment 173281 [details]
log of the dump

Since 24.08 update akonadi crashes frequently with a core-dump. 
Postgresql 16 backend
Pls find journal log attached

Operating System: openSUSE Tumbleweed 20240829
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.5-1-default (64-bit)
Graphics Platform: X11
Comment 1 Axel Braun 2024-09-05 16:41:14 UTC
These crashes lead to the following situation:
docb@X1E:~> akonadictl stop
Akonadi is not running.

docb@X1E:~> akonadictl start
Akonadi is already running.

docb@X1E:~> akonadictl status
Akonadi Control: stopped
Akonadi Server: running
Akonadi Server Search Support: available (Remote Search)
Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent, akonadi_birthdays_resource, akonadi_contacts_resource, akonadi_davgroupware_resource, akonadi_etesync_resource, akonadi_ews_resource, akonadi_ewsmta_resource, akonadi_followupreminder_agent, akonadi_google_resource, akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource, akonadi_indexing_agent, akonadi_knut_resource, akonadi_kolab_resource, akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mailfilter_agent, akonadi_mailmerge_agent, akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent, akonadi_notes_resource, akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_sendlater_agent, akonadi_unifiedmailbox_agent, akonadi_vcard_resource, akonadi_vcarddir_resource

docb@X1E:~> akonadictl instances
(default)
Comment 2 Axel Braun 2024-09-12 05:14:34 UTC
I deleted a newly received mail today and the crash appeared again.

From the log:
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "22P02"
org.kde.pim.akonadiserver:   DB error:  "FEHLER:  ungültige Eingabesyntax für Typ integer: »PLD«\nZEILE 1: EXECUTE qpsqlpstmt_86d6c (2, 'PLD', 669903, 669904, 669842, ...\n                                      ^\n(22P02)"
org.kde.pim.akonadiserver:   Error text: "FEHLER:  ungültige Eingabesyntax für Typ integer: »PLD«\nZEILE 1: EXECUTE qpsqlpstmt_86d6c (2, 'PLD', 669903, 669904, 669842, ...\n                                      ^\n(22P02) QPSQL: Es konnte keine Abfrage erzeugt werden"
org.kde.pim.akonadiserver:   Values: QList(QVariant(qlonglong, 2), QVariant(QString, "PLD"), QVariant(qlonglong, 669903), QVariant(qlonglong, 669904), QVariant(qlonglong, 669842), QVariant(qlonglong, 669812), QVariant(qlonglong, 669811), QVariant(qlonglong, 669810), QVariant(qlonglong, 669808), QVariant(qlonglong, 669805), QVariant(qlonglong, 669804), QVariant(qlonglong, 649290))
org.kde.pim.akonadiserver:   Query: "SELECT PimItemTable.id, PartTable.partTypeId, PartTable.data, PartTable.storage, PartTable.version, PartTable.datasize FROM PimItemTable INNER JOIN PartTable ON ( PimItemTable.id = PartTable.pimItemId ) INNER JOIN PartTypeTable ON ( PartTable.partTypeId = PartTypeTable.id ) WHERE ( ( PartTable.partTypeId = :0 OR PartTypeTable.ns = :1 ) AND PimItemTable.id IN ( :2, :3 ) ) ORDER BY PimItemTable.id DESC"
org.kde.pim.akonadiserver: Handler exception when handling command FetchItems on connection akonadi_indexing_agent (0x55fb6b9b5c70) : Unable to list item parts
org.kde.pim.akonadi_indexer_agent: Failed to fetch items:  "Unable to list item parts"
org.kde.pim.akonadi_indexer_agent: Indexing failed:  ""
org.kde.pim.akonadiserver: Handler exception when handling command FetchItems on connection Archive Mail Kernel ETM (0x55fb6b95fba0) : Item query returned empty result set
"Item query returned empty result set"
org.kde.pim.akonadiserver: Handler exception when handling command FetchItems on connection KMail Kernel ETM (0x55fb6b95e380) : Item query returned empty result set
org.kde.pim.akonadiserver: Handler exception when handling command FetchItems on connection MailFilter Kernel ETM (0x55fb6b9607b0) : Item query returned empty result set
"Item query returned empty result set"
....
KCrash: Application 'akonadiserver' crashing... crashRecursionCounter = 2
org.kde.pim.akonadicore: "QLocalSocket: Die Verbindung wurde von der Gegenseite geschlossen" "/run/user/1001/akonadi/akonadiservorg.kde.pim.akonadicore: "QLocalSocket: Die Verbindung wurde von der Gegenseite geschlossen" "/run/user/1001/akonadi/akonadiservorg.kde.pim.akonadicore: "QLocalSocket: Die Verbindung wurde von der Gegenseite geschlossen" "/run/user/1001/akonadi/akonadiserver-ntf.socket"
er-ntf.socket"
er-ntf.socket"
....
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' crashed! 0 restarts left.
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
QList(QFileInfo(/usr/lib/postgresql/bin), QFileInfo(/usr/lib/postgresql/lib64))
org.kde.pim.akonadiserver: PostgreSQL for Akonadi is already running, trying to connect to it.
org.kde.pim.akonadiserver: Running DB initializer
org.kde.pim.akonadiserver: DB initializer done

Hope that helps!
Comment 3 Christophe Marin 2024-09-12 09:29:09 UTC
The backtrace is not very useful, are the akonadi-debuginfo akonadi-debugsource packages installed?
Comment 4 Daniel Vrátil 2024-09-12 09:42:35 UTC
The backtrace is incomplete, but the last frame before KCrash is _ZNSt8__detail15_List_node_base9_M_unhookEv, which points at the same std::list corruption that we had in the QueryCache code. The corrupted QueryCache would also explain the SQL query errors where we are trying to execute queries with obviously mismatched parameters, so I think this is almost definitely a duplicate of bug 492547.

*** This bug has been marked as a duplicate of bug 492547 ***