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 342073 - cannot change reccurence of reccuring appointment
cannot change reccurence of reccuring appointment
Status: RESOLVED DUPLICATE of bug 341691
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other other
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-05-17 04:05 UTC by Michael Reinsch
Modified: 2013-09-13 00:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Michael Reinsch 2006-05-17 04:05:19 UTC
Distribution: Mandriva Linux release 2006.1 (Cooker) for i586
Package: Evolution
Severity: Normal
Version: GNOME2.15.2 unspecified
Gnome-Distributor: Mandriva
Synopsis: cannot change reccurence of reccuring appointment
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
Description:
Description of Problem:

Version of Evolution: 2.7.2.1

Steps to reproduce the problem:
1. create an all day appointment in evolution, recurring once a week
until a certain date
2. save
3. open appointment again
4. try to change the end date of the recurrence to an earlier date
5. save
6. select "All instances" (this dialog is actually very stupid, but that
is not within the scope of this report)

Actual Results:
Error message: "Object ID already exists"

Expected Results:
No error message, recurrence of appointment is changed

How often does this happen?
always

Additional Information:
It seems that this problem also affects other properties of an
appointment, rendering recurring appointments pretty much unchangeable...




------- Bug created by bug-buddy at 2006-05-17 04:05 -------

Comment 1 André Klapper 2006-05-17 16:14:20 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 ***