Summary: | When receiving a meeting update (attached .ics) kmail always propose the old informations and not the new ones | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Alexandre Bonneau <alexandre.bonneau> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | montel |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
invitation in the message window
same invitation, but read from the preview pane ..and the rest of the invitation |
Description
Alexandre Bonneau
2012-01-03 13:26:48 UTC
It works fine here Created attachment 68193 [details]
invitation in the message window
Created attachment 68194 [details]
same invitation, but read from the preview pane
Created attachment 68195 [details]
..and the rest of the invitation
What can I say, this bug is always reproducible on my configuration. I did notice 2 things : - when double clicking the email, there is no comparison shown into the email window ; the comparison is only shown in the email content pane (as it can be seen in the 3 screeshots) - I you receive an invitation to an event, save it to your calendar, everything is ok. But if you go change the name of the event in korganizer, then go back to the email invitation you can see the same strange behavior : the name into the email invitation is stroked when the new name you used is shown in red. kmail 4.8 ? version 4:4.7.4+git111222-0ubuntu0.1 I can't reproduce here. It works fine. Regards Ok then, is there any other things I can provide for investigating this nasty bug ? 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. 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. |