GNOME Bugzilla – Bug 255908
New Appointments/Events/Tasks don't show in Calendar
Last modified: 2013-09-10 14:03:10 UTC
Steps to reproduce the problem: 1. Upgrade to 1.4.6 via RedCarpet 2. Add an appointment, task or all-day event from Calendar Actual Results: New events don't show up in any of the Calendar views but they do in the Summary view. Expected Results: All events should show up in the Calendar and in the Summary page How often does this happen? Always Additional Information: All appointments that were added previous to the upgrade continue to show in the calendar. But all new events don't. Will attach screenshots... ~/evolution/local/Calendar/calendar.ics is updated correctly.
Created attachment 43457 [details] Screenshot of Calendar. Events that show were added before the upgrade. Note the blank March 25 date.
Created attachment 43458 [details] Summary View that correctly shows all events under the Appointments section
All the items magically appeared in my calendar after a reboot of the machine (for other reasons). I'm guessing some evolution process needs to be restarted after an upgrade and it wasn't after RedCarpet installed the RPM's....
Confirmed here on RH7.3. Running killev will get rid of the Evolution background processes without a reboot, and restarting Evolution will show the newly-added events in the Calendar window. The problem persists across reboots for me.
experiencing the same on debian sid, using evolution-1.4.6-2 really annoying problem. evolution --force-shutdown solves the problem. All the added tasks now appear.
*** bug 259647 has been marked as a duplicate of this bug. ***
*** bug 256787 has been marked as a duplicate of this bug. ***
*** bug 259107 has been marked as a duplicate of this bug. ***
according to gerardo on irc, this is fixed in 1.5. closing.
*** bug 263210 has been marked as a duplicate of this bug. ***
*** bug 268744 has been marked as a duplicate of this bug. ***
*** Bug 301374 has been marked as a duplicate of this bug. ***
*** Bug 266470 has been marked as a duplicate of this bug. ***