Bug 202834

Summary: Drag email to calendar icon - shows in event list - not on calendar until kontact closed/restarted
Product: [Applications] kontact Reporter: Harry <harryl>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: harryl
Priority: NOR    
Version: 4.3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Harry 2009-08-06 19:11:02 UTC 
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Ubuntu Packages

Dragging an email from kmail component to the calendar icon to create linked event.

Event is created with no problems, but does not show on calendar until kontact is closed and restarted.

Event does show in the event list function anytime.

Creating an event in calendar window by new or right click create works as intended. Shows in calendar as created.

This drag function has always performed very well in previous versions up to this newest 4.3.0. 

I use the mail drag to calendar extensively to record correspondence so to be a permanent entry with little chance of being purged.

The to-do module can be purged very easily. This is why I use events.

Otherwise, Kontact has been working very good in 4.3.0.

NOTE: Akonadi is ON. I am using PIM as stand-alone.
Comment 1 Harry 2009-08-11 18:27:47 UTC 
Also, a repeating event that I changed the repeating values also did not appear on the calendar until program was closed and re-started.

This glitch also happens when standalone use in Korganizer.

Using refresh from the menu also does not make the event reappear, either in Kontact, or Korganizer.
Comment 2 Denis Kurz 2016-09-24 19:27:09 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 kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:16:27 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.