Changing the Calendar of an existing recursive schedule hides all entries except the first one

Bug #376110 reported by ClaudioRJ on 2009-05-13
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evolution
Expired
Medium
evolution (Ubuntu)
Low
Ubuntu Desktop Bugs
Jaunty
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Scenario:
1. I have a schedule that was registered in a especific calendar.
2. I created this schedule with recurence (it does not matter with wich type of recurrence, as I noticed the bug with diferent types of recurrence, but for this scenario lets assume 1 day per week, monday, from 9pm to 10pm, lasting forever).
3. Later, I notice that I have to change the calendar of this schedule. So, I edit it and in the calendar combo box I choose other calendar. And save. When asked about if I want to change only this occurence or all of them, I choose all of them.
4. All other entries of this schedule, except that in the first day that it occurs, gets hidden in any type of view of the Evolution calendar (day, month, week, etc).

Notes:
- after all the steps above, if i try to edit this schedule and change the note field, for example, when I save it Evolution asks me if I want to change only this entry or all of them; so, there's still other entries (recurrence) of it, although they are not being displayed.
- when I open my calendar.ics file, in .evolution/calendar/local/system, and search for this schedule resume, I noticed that it is private, instead of public (really don't know if this information helps...). In time: I do not save this .ics file.

(sorry for my english, as I use Evolution in portuguese-BR and some key words I don't know exactly how they are in the english translation)

The way I'm fixing this bug is by deleting this schedule (and again Evolution here asks me if is to delete that entry only or all of them, as it has recurrence, and I answer all), and creating it again in the correct calendar. But this is a little bit annoying, as if I have some exception dates in this schedule I have to first write them down to reproduce in the new schedule, for to keep my data correct.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/evolution
Package: evolution 2.26.1-0ubuntu1
PackageArchitecture: i386
SourcePackage: evolution
Uname: Linux 2.6.28-12-generic

Thanks!

Related branches

Ben Crisford (bencrisford) wrote :

I have this problem also.

Well, I think I do. Its just my evolution crashes when I try and reproduce this. But before it crashes I see the effects you refer to so therefore I will confirm this.

Changed in evolution (Ubuntu):
status: New → Confirmed
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, that's similar to http://bugzilla.gnome.org/show_bug.cgi?id=580724 too

Changed in evolution (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → High
status: Confirmed → Triaged
Changed in evolution (Ubuntu Jaunty):
importance: Undecided → Low
status: New → Invalid
Changed in evolution (Ubuntu):
status: Triaged → Fix Committed
Changed in evolution (Ubuntu):
importance: High → Low
Changed in evolution:
status: Unknown → New
Changed in evolution (Ubuntu Jaunty):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: Invalid → Triaged
Sebastien Bacher (seb128) wrote :

using http://git.gnome.org/cgit/evolution/diff/?id=9896e4f7db7817087b7c18793682a4ab5f7c63e2 that works almost correctly, only the first instance is not moved as it should

Changed in evolution (Ubuntu):
status: Fix Committed → Triaged
Sebastien Bacher (seb128) wrote :
Martin Pitt (pitti) wrote :

Accepted evolution into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in evolution (Ubuntu Jaunty):
status: Triaged → Fix Committed
tags: added: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package evolution - 2.26.1-0ubuntu2

---------------
evolution (2.26.1-0ubuntu2) jaunty-proposed; urgency=low

  * debian/patches/90_git_change_fix_recurrent_event_edition.patch:
    - git change to make editing recurrent events work correctly
      (lp: #372503, #376110)

 -- Sebastien Bacher <email address hidden> Thu, 14 May 2009 16:18:51 +0200

Changed in evolution (Ubuntu Jaunty):
status: Fix Committed → Fix Released
Shahar Or (mightyiam) wrote :

Thanks!

Changed in evolution:
importance: Unknown → Medium
Changed in evolution:
status: New → Incomplete
Changed in evolution:
status: Incomplete → Expired
Jörg Frings-Fürst (jff-de) wrote :

bug from 2009. Version not more supported.
change status to invalid.
Sry Fix released pushed

Changed in evolution (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.