After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 348279 - can't edit recurring all day events
can't edit recurring all day events
Status: RESOLVED DUPLICATE of bug 341691
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other other
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-07-21 19:13 UTC by fowlkes
Modified: 2006-07-21 22:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description fowlkes 2006-07-21 19:13:21 UTC 
Distribution: Fedora Core release 5 (Bordeaux)
Package: Evolution
Severity: Normal
Version: GNOME2.14.2 2.6.x
Gnome-Distributor: Red Hat, Inc
Synopsis: can't edit recurring all day events
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.6.x
Description:
Description of Problem:
User cannot edit recurring, all day events after they have been commited
to the calendar


Steps to reproduce the problem:

1. Create a new all day, recurring event.  
2. Select the event and try to edit it and hit save
3. Witness error message "Object ID already exists"

Actual Results:

error message, forced to discard changes

Expected Results:

editing allowed like any other event in the calendar like any other

How often does this happen?

every time.

Additional Information:




------- Bug created by bug-buddy at 2006-07-21 19:13 -------
Comment 1 Karsten Bräckelmann 2006-07-21 21:55:16 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 341691 ***
Comment 2 fowlkes 2006-07-21 22:14:21 UTC 
hmmmm.  i cannot reproduce bug #341691.  i only get the
bug described here if an event is both "reccuring" and 
"all day".

if i only have "recurring" (as in 341691) it works fine.