Bug 292298 - Internal error if linked email is on deleted IMAP server
Summary: Internal error if linked email is on deleted IMAP server
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.7
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-23 21:59 UTC by Robin Green
Modified: 2017-01-07 22:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robin Green 2012-01-23 21:59:35 UTC
Version:           4.7 (using KDE 4.7.4) 
OS:                Linux

I created a linked task from an email on IMAP, and then decided I wanted to use POP instead of IMAP. So I deleted my IMAP receiving server and added a POP server instead. After this, Kontact could not load the email associated to the task, but instead of saying "email cannot be found" it said "internal error".

Reproducible: Didn't try

Steps to Reproduce:
1. Create task from email in Kontact - choose to create the association with the task as a "link"
2. Delete IMAP account
3. Add POP account
4. Open previously-created task
5. Double-click on Akonadi link attachment in task

Actual Results:  
Error dialog: "Internal Error
Please send a full bug report at http://bugs.kde.org
Unknown error. (Item query returned empty result set)"

Expected Results:  
A more helpful error message like "Email could not be found", or even finding the original email.

OS: Linux (x86_64) release 3.1.9-1.fc16.x86_64
Compiler: gcc
Comment 1 Denis Kurz 2016-09-24 18:52:24 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 korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:04:51 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.