Control: tags -1 +moreinfo Control: reassign -1 kdepim-runtime 4:16.04.2-2+b2 Control: forcemerge -1 900957
Thanks for reporting the issue and sorry for not responding for so long time.
The bug is actually in the maildir_resource that is shipped within kdepim-
runtime package, that why reassign the bug.
It would be super great if you could test your setup with kmail on Debian
Buster, that is currently in testing. Because kdepim fixed serveral issues for
maildir resource.
hefee
On Mittwoch, 27. Februar 2019 05:33:12 CET Jens Radloff wrote:
> I recorded another occurrence of this behaviour with the debugger in the
> Akonadi Console. This time, below the output field on the "All" tab, the
> following additional error messages gets displayed:
>
> --- Quote Beginning ---
>
> AgentBase(akonadi_maildir_resource_0): Verbindung zum Akonadi-Dienst kann
> nicht hergestellt werden. => Can be translated as "Cannot establish
> connection to Akonadi service"
> NotificationManager::notify ( { Type: "Items" Operation: "Modify" Items: { {
> ID: "32532" RemoteID: "1551182744.R329.punk" Remote Revision: "" Mime Type:
> "message/rfc822" } } Session: "akonadi_maildir_resource_0" Resource:
> "akonadi_maildir_resource_0" Destination Resource: "" Parent Collection:
> "9" Parent Destination Collection: "-1" Parts: "QSet(PLD:HEAD, PLD:RFC822,
> PLD:ENVELOPE)" Added Flags: "QSet()" Removed Flags: "QSet()" Added Tags:
> "QSet()" Removed Tags: "QSet()" } )
> NotificationManager::notify ( { Type: "Items" Operation: "Modify" Items: { {
> ID: "32536" RemoteID: "1551196645.R430.punk:2,S" Remote Revision: "" Mime
> Type: "message/rfc822" } } Session: "akonadi_maildir_resource_0" Resource:
> "akonadi_maildir_resource_0" Destination Resource: "" Parent Collection:
> "7" Parent Destination Collection: "-1" Parts: "QSet(PLD:HEAD, PLD:RFC822,
> PLD:ENVELOPE)" Added Flags: "QSet()" Removed Flags: "QSet()" Added Tags:
> "QSet()" Removed Tags: "QSet()" }
>
> -- Quote End ----
>
> Then I restarted Akonadi with "akonadictl restart" in a command shell window
> and did not close this window, but provoked the behavior again. The console
> window returned the following debugging information about the time when the
> behaviour occurred again:
>
> --- Quote Beginning ---
>
> akonadicore_log: Invalid command, the world is going to end!
> QIODevice::read (QLocalSocket): device not open
> akonadi_maildir_resource: /build/akonadi-EKz4jf/akonadi-16.04.3/src/private/
> protocol.cpp:1590: Akonadi::Protocol::HelloResponse::HelloResponse(const
> Akonadi::Protocol::Command&): Zusicherung »d_func()->commandType ==
> Command::Invalid || d_func()->commandType == (Command::Hello |
> Command::_ResponseBit)« nicht erfüllt.
> void Akonadi::Server::NotificationSource::serviceUnregistered(const
> QString&) Notification source "akonadi_maildir_resource_0_4955_mdI52n" now
> serving: () ProcessControl: Application /usr/bin/akonadi_maildir_resource
> stopped unexpectedly ( "Der Prozess ist abgestürzt" ) => Can be translated
> as "The process has crashed"
> Application '/usr/bin/akonadi_maildir_resource' crashed too often. Giving
> up! Shutting down "/subscriber/akonadi_maildir_resource_0_4955_mdI52n" ...
> Lost connection to resource
> "org.freedesktop.Akonadi.Resource.akonadi_maildir_resource_0" , discarding
> cached interface
> Shutting down "akonadi_maildir_resource_0" ...
> Shutting down "0x55b505adb7b0" ...
>
> --- Quote End ---
>
> This bug issue is a duplicate of
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900957
signature.asc
Description: This is a digitally signed message part.
