| Summary: | Received email with a meeting invitation does not explicit the invitation properly as in the Kontact version in Mageia5 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Sohel Fares <sohel> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | geiger.david68210, marja11, ouaurelien, sohel |
| Version: | 6 | Keywords: | UPSTREAM |
| Target Milestone: | --- | Flags: | sohel:
in_errata7?
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kontact 17.12.2 (Help shows 5.7.2) | CVE: | |
| Status comment: | |||
|
Description
Sohel Fares
2019-03-12 05:17:13 CET
Hmmmm! maybe another missing runtime dependency but which??? CC:
(none) =>
geiger.david68210
Marja Van Waes
2019-03-12 12:27:37 CET
CC:
(none) =>
marja11 (In reply to David GEIGER from comment #1) > Hmmmm! maybe another missing runtime dependency but which??? CC:
(none) =>
sohel (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 =>
RESOLVED |