Description of problem: In Mageia 5 an email received with a meeting invitation is displayed in a manner to allow you to accept/refuse/differ etc the meeting and consequently to send the reponse to the author and to enter the meeting details in korganizer. In Mageia 6 this has disappeared and the received email just provides the cal.ics attachement with no means of response. Note that Kontact in Kubuntu 18.04 (Kontact version 5.7 displays the email properly. Not Kontact in Mageia 7 beta 2 has the same problem as Mageia 6. Finally the problems occurs on my three 64bit computers How reproducible: always Steps to Reproduce: 1.Prepare a meeting invitation from another computer and send 2. Send invitation email to the computer with faulty kontact 3.
Hmmmm! maybe another missing runtime dependency but which???
CC: (none) => geiger.david68210
CC: (none) => marja11Assignee: bugsquad => kde
(In reply to David GEIGER from comment #1) > Hmmmm! maybe another missing runtime dependency but which???
CC: (none) => sohelFlags: (none) => in_errata7?
(In reply to Sohel Fares from comment #2) > (In reply to David GEIGER from comment #1) > > Hmmmm! maybe another missing runtime dependency but which??? Excuse me. Comment #2 appeared by mistake when I tried to put myself on CC.
Note: In Mageia 6 and Mageia 7 producing an meeting invitation with Korganiser yields an email for meeting participants with adequate invitation elements seen when received in Mageia 5 and Kubuntu 18.04 Kontact(s) but not when received in the Mageia 6 and 7 Kontact.
Isn't an upstream bug report open about this issue? at https://bugs.kde.org/
I did no find any similar bug in bugs.kde.org with "korganizer" , kontact, or "meeting invitations" keywords in the time period (2017-2018) related to the release of Mageia 6 and 7. Remember Mageia 5 Kontact works well! It was introduced in the development of Mageia 6 and not in the Kubuntu 18.
Hi, thanks for reporting this bug. We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there. As a result we are setting this bug to CLOSED:OLD
Status: NEW => RESOLVEDResolution: (none) => OLDCC: (none) => ouaurelienKeywords: (none) => UPSTREAM