Bug 322039

Summary:	Unable to display/reply/or forward message.
Product:	[Applications] kmail2	Reporter:	K G <govik>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	grave	CC:	giuseppe.vinci
Priority:	NOR
Version:	4.11 beta2
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Screenshot

Description K G 2013-07-06 13:15:46 UTC

After selecting message in message list it's not displayed.  You can't also reply or forward message.

Reproducible: Always

Steps to Reproduce:
1.Choose any folder
2.Chose any message
3.
Actual Results:  
Appears mesaage "Retrieving Folder Contents"

Expected Results:  
Message displayed

After choosing reply or forward dialog "Please wait while message is transferred" appears.

Aplication itself seams to be very responsive. Sometimes message content is displayed after few minutes, but sometimes not even after half hour.

You can display message in akonadi console without problems.

Comment 1 K G 2013-07-06 13:21:32 UTC

Created attachment 80991 [details]
Screenshot

Comment 2 K G 2013-08-01 18:19:38 UTC

Bug is still present  in 4.11 rc2

Comment 3 Giuseppe Vinci 2013-08-11 16:44:58 UTC

I have exact the same problem on KDE10.5.1

Here two related error lines, you get restarting akonadi
1.
akonadi_pop3_resource_1(7302)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
ItemRetrieverException : Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

2. 
Provided 1 values - "[NAME OF MAIL DIRECTORY]"^^<http://www.w3.org/2001/XMLSchema#string>. Existing - "PC%20+%20B%C3%BCro"^^<http://www.w3.org/2001/XMLSchema#string>"
akonadi_nepomuk_feeder(4135) ItemQueue::batchJobResult: Error while storing graph: "http://www.semanticdesktop.org/ontologies/2007/08/15/nao#identifier has a max cardinality of 1

Comment 4 Denis Kurz 2016-09-24 18:02:53 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 5 Denis Kurz 2017-01-07 22:10:13 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.