Bug 257605 - received invitation mail doesn't show invitation info and action buttons
Summary: received invitation mail doesn't show invitation info and action buttons
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: invitations (show other bugs)
Version: enterprise
Platform: Unlisted Binaries Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-22 15:20 UTC by Ludwig Reiter
Modified: 2017-01-07 22:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ludwig Reiter 2010-11-22 15:20:49 UTC 
Version:           enterprise (using Devel) 
OS:                Linux

version e5.20101112.1197730-kk4 (enterprise5)

Receive an invitation. But the invitation box display is not shown and it is not possible to accept it.

Reproducible: Always

Steps to Reproduce:
1. A sends an invitation to B.
2. B waits until the mail is in the inbox.
3. B looks at the invitation.

Actual Results:  
Not a normal invitation display is shown.

Expected Results:  
A boxed invitation with action buttons, which work.
Comment 1 Christian (Fuchs) 2011-04-18 15:10:05 UTC 
Confirmed in "regular" kmail 2.0.95  (kdepim 4.6 beta 5) 

Invitations are displayed as an .ics attachement, but there is no possibility to accept, decline or any other actions. 

This is a major drawback since kmail1, currently it is not possible to reply to any invitations received ...
Comment 2 Denis Kurz 2016-09-24 18:43:31 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 3 Denis Kurz 2017-01-07 22:29:37 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.