GNOME Bugzilla – Bug 271679
"make this occurrence movable" unusable
Last modified: 2013-09-10 14:04:09 UTC
running evolution-2.1.3.2.0.200501200931-0.snap.ximian.10.1 on suse9.2, i have a recurring event which is once a week. if i right-click on it and say "make this occurrence movable" (yepp, on exactly that day my lessons are at 9h45 and not at 15h00 like all the other days), the appointment gets duplicated in all its occurences! after choosing "delete all occurrences" to get rid off the duplicate, both recurring appointments get removed on all the days except the one occurrence i set movable. and i have to set it up all again... sigh. yeah, i know, recurrences rewrite, please fix this, it's unusable... :-)
Duplicates should not show up anymore
(related/same as bug 270580 by the way) hi rodrigo, still testing around with the reoccurence thing and still seeing this. running evolution-2.1.5.0.200502170410-0.snap.ximian.10.1 on suse9.2 here, gtk2-2.4.9-10. set up a normal appointment, date: today (march 1st; time: 4:00-6:00) and set occurence to "every 1 weeks forever". choose the first occurence of the appointment and choose "make this occurence movable". result: - days are still bolded in mini calendar in the right above corner. - first item moves from 4:00 to 1:00 beginning time in every view! - in day view, work week view and work view, the second occurence and the third are not visible, the 4th one is doubled, 5th one does not exist, 6th and above is doubled again! - in month view, all the items except for the first one get doubled! ok, so i must assume that when i once click on a reoccurence item to make it movable, it automatically gets set to 1:00. everytime i choose "make this occurence movable" again, it gets duplicated. -click again on the first item and choose "make this occurence movable". it gets doubled, both in month and day view. -delete the second one in month view or in day view. nothing happens. now switch the view [or in day view, go to another day and back again to where you came from], there is only one item. switching back to former view: now there is also only one item like expected (seems like view does never get redrawn after deleting an element). it also seems to me that the little mini calendar in the right above corner also does not get redrawn always correctly. another case: i am in month view and set up an appointment, date: today (march 1st; time: 12:00-18:00) and set occurence to "every 3 days until march 31st". i take the 4th item (march 10th) and choose to make that occurence movable. the time gets set to 1:00 again and all the other occurences get removed (!) in my month view (5 weeks from feb 28th to april 3rd), but the little mini calendar does not change and still shows all those days in bold. switching views does not bring all those items back! now mark a different time period by marking days in the mini calendar: - feb 28th to march 27th: only the one movable occurence gets displayed. - feb 28th to march 20th: mar 1st, 4th, 7th and 13th have *two* occurences at 12:00, 10th has the movable occurence at 1:00, 16th and 19th show nothing, and 14th which should show nothing shows 4 occurences! - march 7th to april 03rd: thrid week totally empty, 28th got four occurences. ....and so on. seems to be heavily broken. deleting also seems to be very weird, won't test this tonight anymore. .. should i test this with a current snapshot version again? sigh...
that every movable occurence gets set to 1:00 could be because of my timezone (CET) - so it always seems to get set to 0:00 GMT/UTC.
i've just installed the latest snap (evolution-2.1.6.0.200503010410-0. snap.ximian.10.1), i still see these issues, sometimes in variations (e.g. not everything getting doubled, but only the occurence i made movable is shown in the month view and still gets set to 1:00 beginning time), won't test that now here in detail again. if you want me to test something or need more data, just leave a note. .. :-)
Patch sent to e-p list
The patch didn't go in, but we worked around this in 2.2.0.
bug 273506 and bug 273507 could be duplicates of this one here
some of my "the third week in the month view shows incorrectly blah blah" experiences described here actually have nothing to do with this bug here but with bug 273533 i guess.
Fixed.
*** bug 273506 has been marked as a duplicate of this bug. ***
*** bug 273507 has been marked as a duplicate of this bug. ***
perhaps bug 270580 is a duplicate.
Should be fixed in CVS HEAD
*** Bug 270580 has been marked as a duplicate of this bug. ***
i still see this issues in evolution-2.4.0.0.200509090712-0.snap.novell.11.1 on suse9.3 at least in dayview, therefore reopening, sigh... (five o'clock in the morning and writing a loooong how-to-reproduce instruction sucks, so having a cigarette before continuing ...wait... ): ok, now how to reproduce: CASE I 1) set up a new appointment (half an hour standard) and set recurrence to "every 1 week forever". 2) go to the first date it takes place and try to change its length by dragging its bottom to something below (let's say you want it to be 3 hours long instead of half an hour). choose "only this instance" in the popup window. in day view, the length of the first appointment has not changed at all [BUG1]. 3) use the date date selector in the upper right corner and click on the date with the second appointment of that series. the day is bolded, but there is no appointment at all [BUG2]. this seems to be 100% reproducible here, though i've seen many surprises in my recurrence tests, so i wouldn't swear that it's 100%. switching to mail component and back does not fix it. CASE II 1) set up a new appointment with 3 hours length and set recurrence to "every 1 week forever". 2) go to the first date it takes place and reduce its length by dragging its bottom to something above (let's say you want it to be 1 hour long instead of 3 hours). choose "only this instance" in the popup window. we already know that in day view, the length of the first appointment has not changed at all. 3) use the date date selector in the upper right corner and click on the date with the second appointment of that series. the day is bolded, but there is no appointment at all. there is also no appointment displayed at the third and the fourth date (haven't tested later dates in the future). 4) use the date date selector in the upper right corner and click on the date with the first appointment of that series to go back there. now i have two appointments displayed that day, one with 3 hours length and one with 1 hour length [BUG 3]. this is **NOT** 100% reproducible here!! 5) use the date date selector in the upper right corner and click on the second, third and fourth date. now they are displayed correctly. 6) use the date date selector in the upper right corner and click on the first date again. now i have three appointments displayed that day, one with 3 hours length and two with 1 hour length. 7) use the date date selector in the upper right corner and click on the second, third and fourth date. now i have two appointments displayed each date, both with 1 hour length. repeat 6 and 7, you can see that this happens recursively. 8) i did "evolution --force-shutdown". after restarting, all dates are 3 hours long [BUG 4]. also, once suddenly the weekly recurrences became daily recurrences without changing the recurrence interval on my own, but i cannot reproduce that anymore now. :-/ so this seems still totally borked, therefore retargetting from 2.2.x to 2.4.1, sorry guys... feel free to ask for more information or stuff like that (i'm running rpm snapshot and do not compile on my own if i should retest stuff), but please don't let me write long how-to-reproduce instructions again ;-) good night.
uups, forgot to reopen. really gotta sleep.
Thanks for reporting. Modifying the recurrence instances is broken and the bug id for it is 310452. I have a patch for recurrence, bug id 266144, which breaks the API and would be committed for HEAD. That would be required for fixing all the recurrence related issues. Retargetting it to 2.5.
chenthill, thanks for your comment. i'm going to add comments/links to the two bugs you've added here. [would be cool if you could write the word "bug" in front of a bug id, so bugzilla can automatically add a link.]
[a comment for myself:] so this bug here depends on bug 318777 and bug 312533. bug 266144 has been fixed.
seems like this is fixed in 2.5.3. thanks :-)