Bug 272435

Summary: KOrganizer silently deletes participants with no e-mail
Product: [Applications] korganizer Reporter: Christopher Yeleighton <giecrilj>
Component: invitationsAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: major CC: mail
Priority: NOR    
Version: 4.4.10   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Bug Depends on:    
Bug Blocks: 442331    

Description Christopher Yeleighton 2011-05-04 12:20:04 UTC
Version:           4.4.10
OS:                Linux

KOrganizer silently deletes participants with no e-mail

Reproducible: Always

Steps to Reproduce:
  1. Tell KOrganizer to create a new task 
"KOrganizer silently deletes participants with no e-mail".
  2. Tell the task to add the participant "Richard Apodaca".
  3. Tell the task to save and close.
  4. Tell KOrganizer to edit the task.

Actual Results:  
  4. No participants.

Expected Results:  
  4. Participant: Richard Apodaca.

OS: Linux (x86_64) release 2.6.37.6-0.5-desktop
Compiler: gcc
Comment 1 Elias Probst 2011-09-21 08:40:18 UTC
I can confirm this issue.

When adding someone without an e-mail address, I see the warning
"does not look like a valid email address. Are you sure you want to invite this participant?"
first.

This error message should probably display the entered name in front of "does not look like...", otherwise it is not clear to which entry this message refers.
Comment 2 Elias Probst 2011-09-21 08:42:39 UTC
(In reply to comment #1)
> I can confirm this issue.

Forgot to add some information about my system:
KDE SC 4.7.1
KDEPIM 4.7.1
Akonadi-Server 1.6.0

Resource: CalDAV connecting to a Citadel Groupware Server
Comment 3 Denis Kurz 2016-09-24 18:42:14 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 4 Denis Kurz 2017-01-07 22:37:05 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.