Summary: | Crash of akonadiserver upon startup | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Erik Quaeghebeur <bugs.kde.org> |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Erik Quaeghebeur
2019-01-10 07:48:06 UTC
I did an update of Qt from 5.11.1 to 5.11.3 yesterday, and it seems this may have something to do with it. Namely, I observed the following on the konsole where I tried to start akonadi after it crashed: org.kde.pim.akonadicontrol: ProcessControl: Application "akonadiserver" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application 'akonadiserver' crashed! 1 restarts left. Cannot mix incompatible Qt library (version 0x50b01) with this library (version 0x50b03) KCrash: Application 'akonadiserver' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 so, akonadi wasn't rebuilt after updating Qt? (In reply to Christophe Giboudeaux from comment #2) > so, akonadi wasn't rebuilt after updating Qt? No, I guess the package maintainers didn't think minor library version updates required a rebuild. (I also find it a bit strange that a minor update is this incompatible.) In any case, I rebuilt akonadi and things are working again. I'll report this downstream. Minor Qt updates _can_ update internal API or data layout, and any code that accesses the internal API needs to be recompiled against the new Qt. That's why Qt's plugin system throws the version mismatch error, even if it cannot know if there really is an incompatible change. Better safe (sane error message) than sorry (just crash and nobody knows why). For "normal" Qt code, you do not need to recompile. |