Editing calendar events to recur forever corrupts the calendar the event is tied to

Bug #362318 reported by Tim
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evolution
Expired
Critical
evolution (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: evolution

-create a calendar event that recurs weekly. Evolution defaults to 1 occurrence, which is a separate issue that I feel should be addressed (the point of a "recurring event" is that it happens more than once).
-save event. See that it's not recurring on the calendar.
-open event, click "Recurrence" and change "for 1 occurrence" to "forever".
-Close, Save.
-a window pops up asking "You are modifying a recurring event. What would you like to modify?" Select "All Instances" and "OK". Evolution immediately greys out and must be force quit.

After this, Evolution will start up fine in email mode, but when you switch to Calendar mode, Evolution locks up again and must be force quit each time you access the Calendar. The workaround is to go into home directory .evolution/calendar/local/system and delete the calendar.ics file. This erases your calendar so be sure you have a backup before continuing. You can re-import your calendar and start again.

Note: If you correctly set up the calendar event the first time (ie, weekly, recurring forever) without going back and editing the event, it will be created properly with no lock ups.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: evolution 2.26.1-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
Uname: Linux 2.6.28-11-generic x86_64

Revision history for this message
Tim (tzakharov) wrote :
Revision history for this message
taiebot65 (taiebot65) wrote :

I can confirm this bug. there is no log error in evolution

Changed in evolution (Ubuntu):
status: New → Confirmed
Revision history for this message
taiebot65 (taiebot65) wrote :

An easy way as well is to manually move a recurrent event and choose to change all the recurrent event

Revision history for this message
taiebot65 (taiebot65) wrote :

OK it seems that evolution is creating two events at a time and making it totally unusable. I have attached an ics calendar with an events which was moved and the bug occured

Revision history for this message
Pedro Villavicencio (pedro) wrote :

could somebody having the issue send this directly upstream at bugzilla.gnome.org where the software authors can read about it? for forwarding instructions please have a look to http://wiki.ubuntu.com/Bugs/Upstream/GNOME ; thanks in advance.

Changed in evolution (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
Revision history for this message
scrollo (invisibleaxeman) wrote :

Similar problem here, editing a recurring event, then choosing to update all instances immediately crashes evolution, with subsequent evolution launches freezing whenever the calendar is accessed - deleting ~/.evolution/calendar seems the only way i can unfreeze it at the moment. Seems to also happen if I set up a recurring event and try and add additional alarm notifications to it.

Revision history for this message
paraiko (paraiko) wrote :

I can also confirm the bug.
Editing a previously created recurring appointment (only 2 instances) freezes evolution and corrupts the calendar.

It seems to me that the importance classification low is maybe underestimating the situation?
Editing a recurring appointment is something that occurs quite often in day to day use. And the consequences are rather severe (unusable and corrupted calender.....) Not every user will know how to correct the problem or have a calendar backup.

Revision history for this message
Tim (tzakharov) wrote :

Has anyone been able to forward the bug upstream? Every time I click:
http://bugzilla.gnome.org/browse.cgi?product=Evolution

It takes minutes to load the page, only to load up a blank page. So I cannot progress further to forward the bug. If someone has better luck, please let me know so I do not duplicate the report.

Revision history for this message
Dan McArdle (zingermc) wrote :

Rather than trashing your calendar after you run into this bug, edit ~/.evolution/calendar/blahblahblah/calendar.ics

I searched for the name of my repeating event and came up with two items. For both of them I deleted everything from the "BEGIN" line to the "END" line (including those lines). Then I restarted evolution and it worked as if I never created that event in the first place.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Any news about this? did somebody sent the bug upstream?

Revision history for this message
Dan McArdle (zingermc) wrote :

I tried following Tim's link, but the page wouldn't load for me, either.

Revision history for this message
Tim (tzakharov) wrote :

Pedro,

I am still having the same problem with the link to Evolution's page on bugzilla.gnome.org not loading. See 3 posts above this one for the link. If someone can post a working link, I will report it upstream.

Revision history for this message
Tim (tzakharov) wrote :

Update: still cannot load the Evolution page at bugzilla. In the meantime, I posted about this on Nabble's Evolution page yesterday. Here's the link:

http://www.nabble.com/can%27t-report-bug-because-Evolution-page-not-loading-%40-bugzilla.gnome.org-to23284372.html

Revision history for this message
Vanostaajen (tvodeslimme) wrote :

I can confirm this bug. It's kinda fucked u for thse who don't have back-ups. Luckily I have my palm :-)

Revision history for this message
paraiko (paraiko) wrote :

I've already tried to report this bug upstream several times as well, but the evolution bugtracker is still broken.

Revision history for this message
Tim (tzakharov) wrote :

I got the bug reported:
http://bugzilla.gnome.org/show_bug.cgi?id=581688

I was not clicking "New bug" link from bugzilla main page, hence my earlier problems trying to report bug. Instead, I was clicking "Browse" link and attempting to browse to Evolution page (where I assumed I would find a "report bug" link), which is the page that is failing to load.

Changed in evolution (Ubuntu):
status: Confirmed → Triaged
Changed in evolution:
importance: Undecided → Unknown
status: New → Unknown
Changed in evolution:
status: Unknown → New
Revision history for this message
taiebot65 (taiebot65) wrote :

This bug has been solved

I'm closing it feel free to open if you are still affected by this bug.

Changed in evolution (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
taiebot65 (taiebot65) wrote :

 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)

Revision history for this message
Tim Tilberg (ttilberg) wrote :

I'm running a currently updated Jaunty 9.04, Evolution 2.26.1

I'm still having this issue:
To reproduce these are my exact steps:
-Go to Calendar
-Switch to Month View
-Double Click Friday May 22 and create the following event:
**Summary: Tim Card
**Location: https://website.com
**Unselect as Busy
**Select Recurring Event [2 weeks:Fri:forever]
(Event is Created correctly)
-Double Click event to edit information
-Edit Summary to "Time Card"
-Save
-Select All Instances
(note: Only selected event was changed-- the event for June 05, remains "Tim Card" -- I believe it is refreshed if you switch to mail and back to Calendar)
-Double Click May 22 event again and change summary to "Timee Card"
(Update is not displayed on calendar)
-Double Click May 22 event once more to change summary, as it didn't seem to reflect the change (also note in appointment popup, it appears Timee card was not saved at all). Change Time Card to Timee Card once more, all instances

**crash**

I came across this today while I was trying to get my Calendar set up for work purposes (obviously). I don't remember the exact edits I did the first time, but the above process crashed Evolution every time.

Also, after killing Evolution with xkill Evolution will not open again until the actual process is stopped from System Monitor.

I'm not sure if I should file a new bug report, or add to this one, and also if I should be including more information. I'm very new to officially reporting bugs.

Thank you

Revision history for this message
taiebot65 (taiebot65) wrote :

I can not reproduce your bug.

Have you checked that you ve got the package installed maybe it s on proposed not on the main repro.

Revision history for this message
Tim Tilberg (ttilberg) wrote : Re: [Bug 362318] Re: Editing calendar events to recur forever corrupts the calendar the event is tied to

I do not currently have "jaunty-proposed" enabled -- I previously did not
understand what you had posted above, but understood that it was fixed and
figured it would be in the main repo and fixed through system update.

Would you recommend enabling jaunty-proposed, or would that cause a certain
amount of instability?
How long does it typically take for a package to go from proposed to main?

Thank you for the assistance.

Revision history for this message
taiebot65 (taiebot65) wrote :

Yes you have to enable jaunty-proposed to get it fixed.
 I do not know how long it takes to get from proposed to main.
To be honest i have always used proposed repro and i have never had any problems.
So i would recommend it.

More info here.. https://help.ubuntu.com/community/Repositories/Ubuntu
I do not know if this is going to main.

Changed in evolution:
importance: Unknown → Critical
Changed in evolution:
status: New → Expired
Omer Akram (om26er)
Changed in evolution (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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