Bug#900895: kmail: KMail malfunctioning: Red email folders, no emails can be viewed; "Unable to fetch item from backend (collection-1): Unable to contact resource"

2019-05-23 Thread Jens Radloff
Hi,

The behaviour described in this bug issue has just appeared again.

Regards,

Jens



Bug#900895: kmail: KMail malfunctioning: Red email folders, no emails can be viewed; "Unable to fetch item from backend (collection-1): Unable to contact resource"

2019-03-03 Thread Jens Radloff
Hi hefee,

I strongly assume that it makes no sense if I _currently_ would test my PIM 
environment in the current Debian testing release because the behavior 
described in this bug issue did not occur anymore since the last time I 
updated this bug issue on Wed, 27 Feb 2019. 

This is now the 5th day after Wed, 27 Feb 2019 that the behavior did not occur 
again. Before that, between Sunday, 24th 2019 and Wed, 27 Feb 2019, the 
behavior occurred very often. let's say about 30 times.

Since Wed, 27 Feb 2019 I installed at least one system update via apt-get, 
could it be that this update resolved the behavior? I cannot remember which 
package this update updated.

Or could it be that a misconfiguration of one of the remote mail servers which 
I am utilizing, or a erroneous software environment the respective mail server 
is running in, temporary could caused the behavior?

I will report new occurrences of the behavior in this bug issue, but I do not 
know when these occurrences will happen again.

Regards,

Jens


Am Sonntag, 3. März 2019, 22:41:51 CET schrieb Sandro Knauß:
> 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



Bug#900895: kmail: KMail malfunctioning: Red email folders, no emails can be viewed; "Unable to fetch item from backend (collection-1): Unable to contact resource"

2019-03-03 Thread Sandro Knauß
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.


Bug#900895: kmail: KMail malfunctioning: Red email folders, no emails can be viewed; "Unable to fetch item from backend (collection-1): Unable to contact resource"

2019-02-26 Thread Jens Radloff
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



Bug#900895: kmail: KMail malfunctioning: Red email folders, no emails can be viewed; "Unable to fetch item from backend (collection-1): Unable to contact resource"

2019-02-26 Thread Jens Radloff
Since the last 48 hours the behavior described in this bug issue occurred 14 
times, and it strongly seems that it will continue to occur.

I searched the Internet for the error message "Unable to fetch item from 
backend (collection-1): Unable to contact resource", and found this bug report:

https://forums.opensuse.org/showthread.php/533024-KMail-Not-Syncing-Gmail-Accounts-After-Recent-Updates

But this external bug report did not help me to resolve the issue. I installed 
the packages libgsasl7 and libgsasl7-dev, but without access, the behavior 
still occurs.

Note that I am using the PIM and within the PIM kmail to access among other 
things my Yahoo mail account, but no Gmail account. I am retrieving my mails 
from my mail accounts using POP3, but not IMAP. Currently the behavior occurs 
if I click the "Check for new mails" button in kmail and then wait until the 
status bar tells me that this check has been completed by "100%", but the 
behaviour does not occur every time I check my mails using this button. It 
occurs once in a while.

The behavior just occurred again, and here is the output of the debugger in the 
Akonadi Console (last lines):

--- Quote Beginning ---

akonadi_pop3_resource_2 (0x55975d44f2c0) 24 { Command: "FetchCollections" 
Collections: "UID " Depth: "2" Resource: "akonadi_pop3_resource_2" Mimetypes: 
"()" Ancestors Depth: "2" Ancestors Attributes: "QSet()" Enabled: "false" Sync: 
"false" Display: "false" Index: "false" Status: "false" }
akonadi_pop3_resource_2 (0x55975d44f2c0) 24 { Response: "FetchCollections" 
Error Code: "0" Error Msg: "" ID: "-1" Name: "" Parent ID: "-1" Remote ID: "" 
Remote Revision: "" Resource: "" Mimetypes: "()" Statistics: { Count: "-1" 
Unseen: "-1" Size: "-1" } Search Query: "" Search Collections: "QVector()" 
Cache Policy: { Inherit: "true" Interval: "-1" Cache Timeout: "-1" Sync on 
Demand: "false" Local Parts: "()" } Ancestors: { } Attributes: "QMap()" 
Display: "Undefined" Sync: "Undefined" Index: "Undefined" Enabled: "true" 
Virtual: "false" Referenced: "false" }
akonadi_pop3_resource_2 (0x55975d44f2c0) 25 { Command: "FetchCollections" 
Collections: "UID " Depth: "2" Resource: "akonadi_pop3_resource_2" Mimetypes: 
"()" Ancestors Depth: "0" Ancestors Attributes: "QSet()" Enabled: "false" Sync: 
"true" Display: "false" Index: "false" Status: "false" }
akonadi_pop3_resource_2 (0x55975d44f2c0) 25 { Response: "FetchCollections" 
Error Code: "0" Error Msg: "" ID: "-1" Name: "" Parent ID: "-1" Remote ID: "" 
Remote Revision: "" Resource: "" Mimetypes: "()" Statistics: { Count: "-1" 
Unseen: "-1" Size: "-1" } Search Query: "" Search Collections: "QVector()" 
Cache Policy: { Inherit: "true" Interval: "-1" Cache Timeout: "-1" Sync on 
Demand: "false" Local Parts: "()" } Ancestors: { } Attributes: "QMap()" 
Display: "Undefined" Sync: "Undefined" Index: "Undefined" Enabled: "true" 
Virtual: "false" Referenced: "false" }
akonadi_pop3_resource_1 (0x55975d403ee0) 24 { Command: "FetchCollections" 
Collections: "UID " Depth: "2" Resource: "akonadi_pop3_resource_1" Mimetypes: 
"()" Ancestors Depth: "2" Ancestors Attributes: "QSet()" Enabled: "false" Sync: 
"false" Display: "false" Index: "false" Status: "false" }
akonadi_pop3_resource_1 (0x55975d403ee0) 24 { Response: "FetchCollections" 
Error Code: "0" Error Msg: "" ID: "-1" Name: "" Parent ID: "-1" Remote ID: "" 
Remote Revision: "" Resource: "" Mimetypes: "()" Statistics: { Count: "-1" 
Unseen: "-1" Size: "-1" } Search Query: "" Search Collections: "QVector()" 
Cache Policy: { Inherit: "true" Interval: "-1" Cache Timeout: "-1" Sync on 
Demand: "false" Local Parts: "()" } Ancestors: { } Attributes: "QMap()" 
Display: "Undefined" Sync: "Undefined" Index: "Undefined" Enabled: "true" 
Virtual: "false" Referenced: "false" }
akonadi_pop3_resource_1 (0x55975d403ee0) 25 { Command: "FetchCollections" 
Collections: "UID " Depth: "2" Resource: "akonadi_pop3_resource_1" Mimetypes: 
"()" Ancestors Depth: "0" Ancestors Attributes: "QSet()" Enabled: "false" Sync: 
"true" Display: "false" Index: "false" Status: "false" }
akonadi_pop3_resource_1 (0x55975d403ee0) 25 { Response: "FetchCollections" 
Error Code: "0" Error Msg: "" ID: "-1" Name: "" Parent ID: "-1" Remote ID: "" 
Remote Revision: "" Resource: "" Mimetypes: "()" Statistics: { Count: "-1" 
Unseen: "-1" Size: "-1" } Search Query: "" Search Collections: "QVector()" 
Cache Policy: { Inherit: "true" Interval: "-1" Cache Timeout: "-1" Sync on 
Demand: "false" Local Parts: "()" } Ancestors: { } Attributes: "QMap()" 
Display: "Undefined" Sync: "Undefined" Index: "Undefined" Enabled: "true" 
Virtual: "false" Referenced: "false" }
akonadi_pop3_resource_0 (0x55975d4559d0) 24 { Command: "FetchCollections" 
Collections: "UID " Depth: "2" Resource: "akonadi_pop3_resource_0" Mimetypes: 
"()" Ancestors Depth: "2" Ancestors Attributes: "QSet()" Enabled: "false" Sync: 
"false" Display: "false" Index: "false" Status: "false" }
akonadi_pop3_resource_0 (0x55975d4559d0) 24 { Response: 

Bug#900895: kmail: KMail malfunctioning: Red email folders, no emails can be viewed; "Unable to fetch item from backend (collection-1): Unable to contact resource"

2018-07-26 Thread Jens Radloff
Hi,

The behavior which I described here (Bug#900895) has not appeared again since 
several weeks.

Regards,

Jens



Bug#900895: kmail: KMail malfunctioning: Red email folders, no emails can be viewed; "Unable to fetch item from backend (collection-1): Unable to contact resource"

2018-06-06 Thread Jens Radloff
Package: kmail
Version: 4:16.04.3-4~deb9u1
Severity: important

Hi,

The following behaviour currently occurs in my Debian 9 (Stretch)
installation since some days, several times a day. 

All current Debian repository updates are installed in my system. The
file /etc/debian_version says "9.4" as the currently installed Debian
version on my computer. KDE 5 (Plasma) is the only installed Desktop
Manager in my system.

This is the content of my sources.list file:

- - - Quote Beginning - - -

deb http://ftp2.de.debian.org/debian/ stretch main contrib non-free
deb-src http://ftp2.de.debian.org/debian/ stretch main contrib non-free

deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib
non-free

- - - Quote End - - -

This is a description of the behaviour:

1. Kdepim is running for a while. Within Kdepim, I am either writing a
new email, and/or I am clicking around in the email folders, and/or I am
viewing emails which I had received in the Preview Window of the KMail
section of kdepim.

2. Suddenly the colour of the names of all email folders in the KMail
section turns red, and the status indicator line shows the following
error message:

"Unable to fetch item from backend (collection-1): Unable to contact
resource"

3. I am not able to view the contents of any email in the Preview Window
of KMail anymore, no email is displayed there.

4. When double-clicking any email in any email folder, its content is
not displayed, the email does not get opened. Instead, an external
window is displayed with the following text: "Bitte Übertragung der
Nachricht abwarten" (this can be translated into English like "Please
wait for the message being transferred"). No message get transferred,
independent from how long I wait.

5. While this behaviour occurs, event reminders from the calendar
application (KOrganizer), which is part of Kdepim, get displayed.

To resolve this behaviour I successfully can apply the command
"akonadictl restart", or I reboot my machine. I did not check whether
this bevaviour gets resolved if I log off from KDE and log in again.

This behaviour is similar, but not identical with bug #726831.

Best regards,

Jens


-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kmail depends on:
ii  akonadi-server   4:16.04.3-4
ii  kdepim-runtime   4:16.04.2-2+b2
ii  kdepimlibs-data  4:16.04.2-2
ii  kf5-kdepimlibs-kio-plugins   4:16.04.2-2
ii  kio  5.28.0-2
ii  libc62.24-11+deb9u3
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libkf5akonadiagentbase5  4:16.04.3-4
ii  libkf5akonadicalendar5   16.04.2-2
ii  libkf5akonadicontact54:16.04.2-2
ii  libkf5akonadicore5   4:16.04.3-4
ii  libkf5akonadimime5   4:16.04.2-2
ii  libkf5akonadisearch-plugins  16.04.3-1+b2
ii  libkf5akonadisearchdebug516.04.3-1+b2
ii  libkf5akonadiwidgets54:16.04.3-4
ii  libkf5alarmcalendar5 16.04.2-2
ii  libkf5archive5   5.28.0-2
ii  libkf5bookmarks5 5.28.0-1
ii  libkf5calendarcore5  4:16.04.2-1
ii  libkf5calendarsupport5   4:16.04.2-2
ii  libkf5calendarutils5 16.04.3-1
ii  libkf5codecs55.28.0-1+b2
ii  libkf5completion55.28.0-1
ii  libkf5configcore55.28.0-2
ii  libkf5configgui5 5.28.0-2
ii  libkf5configwidgets5 5.28.0-2
ii  libkf5contacts5  16.04.2-1
ii  libkf5coreaddons55.28.0-2
ii  libkf5crash5 5.28.0-1
ii  libkf5dbusaddons55.28.0-1
ii  libkf5followupreminder5  4:16.04.2-2
ii  libkf5gpgmepp-pthread5   16.04.3-2+b2
ii  libkf5gravatar5  4:16.04.2-2
ii  libkf5guiaddons5 5.28.0-1
ii  libkf5i18n5  5.28.0-2
ii  libkf5iconthemes55.28.0-2
ii  libkf5identitymanagement516.04.2-1
ii  libkf5incidenceeditor-bin16.04.2-2+b2
ii  libkf5incidenceeditor5   16.04.2-2+b2
ii  libkf5itemmodels55.28.0-2
ii  libkf5itemviews5 5.28.0-1
ii  libkf5jobwidgets55.28.0-2
ii  libkf5kcmutils5  5.28.0-2
ii  libkf5kdelibs4support5   5.28.0-1
ii  libkf5kiocore5   5.28.0-2
ii  libkf5kiofilewidgets55.28.0-2
ii  libkf5kiowidgets55.28.0-2
ii  libkf5kmanagesieve5  4:16.04.3-2+b2
ii  libkf5kontactinterface5  16.04.2-1
ii  libkf5ksieveui5  4:16.04.3-2+b2
ii  libkf5libkdepim-plugins  4:16.04.2-3
ii  libkf5libkdepim5 4:16.04.2-3
ii  libkf5libkleo5