Bug 1380609

Summary: Kmail: crash when trying to view SOGO event notifications
Product: [Fedora] Fedora Reporter: Stephan Mueller <smueller>
Component: kf5-kmailtransportAssignee: Daniel Vrátil <me>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: kde-sig, me, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:16:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Stephan Mueller 2016-09-30 06:09:30 UTC
Description of problem:

When receiving event notifications from SOGO, kmail crashes instantly when trying to open the message. It is not even possible to remove the email (even when selecting a bunch of emails such that the offending event email is not opened). Further, even akonadiconsole crashes when accessing the email.

Also, the event email is not found in .local/share/local-mail which means that even a manual removal is impossible.

Thus, I am stuck with these event emails in my inbox.

Note, other event notifications from other systems work.


Version-Release number of selected component (if applicable):

kmail-libs-16.08.1-1.fc24.x86_64
kf5-kmailtransport-16.08.1-1.fc24.x86_64
kmail-16.08.1-1.fc24.x86_64


How reproducible:

Receive a SOGO event email and click on it.


Steps to Reproduce:
1.
2.
3.

Actual results:

crash


Expected results:

no crash


Additional info:

Comment 1 Stephan Mueller 2016-09-30 06:10:53 UTC
Side note: everything worked before the last update of kmail.

Comment 2 Rex Dieter 2016-09-30 14:35:03 UTC
If possible, I encourage you to report this upstream to bugs.kde.org

Comment 3 Rex Dieter 2016-09-30 14:36:26 UTC
and, include a backtrace of the crash too

Comment 4 Stephan Mueller 2016-09-30 15:00:35 UTC
The issue looks very similar to what is described in https://bugs.kde.org/show_bug.cgi?id=369042.

Is it possible to pull the fix into F24?

Comment 5 Rex Dieter 2016-09-30 15:08:52 UTC
If there is a fix available, yes (but I don't see one yet)

Comment 6 Fedora End Of Life 2017-07-25 23:18:05 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2017-08-08 19:16:28 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.