GNOME Bugzilla – Bug 353012
month view does not display all items
Last modified: 2011-02-17 18:35:03 UTC
i got the strong feeling that i had filed this already, but cannot find it. evo 2.7.92, please take a look at the screenshots. they are all exactly the same calendar, i haven't changed anything except the amount of weeks to display by using my mouse in the mini calendar at the left bottom of the window. i especially have of course NOT changed any items of the calendar and did not enable/or disable anything. see the difference between the displayed items and the bold days in the mini calendar. obviously sometimes some items are not displayed at all. like always, i cannot reproduce it constantly, but i can reproduce it. seems like this happens when i select four to six weeks for multiple times and go ahead in time... scrolling back and forth by using the scroll bar at the right of the month view makes the month view render correctly. i also tried to check if this also affects the print preview, but am blocked once again by bug 272640 which let's me only view the first three of the six weeks. (three screenshots to come; please ignore the calendar content, it is only a draft)
Created attachment 71665 [details] screenshot 1 - nothing wrong yet.
Created attachment 71699 [details] screenshot 2 - missing appointments (see the bold dates in the mini calendar)
Created attachment 71700 [details] screenshot 3 - where are my appointments?
Created attachment 71733 [details] screenshot 4 - printing seems to be correct (the 90° degree bug is bug 272640)
Bumping version to a stable release.
Andre, it works for me, can you please try in current stable 2.22.3, thanks in advance. Print still has issues.
can't reproduce, let's close
Created attachment 124829 [details] Screenshot from 2.24.2 Just happen again in 2.24.2. Marked week 50 to 52 in the mini calendar, then weeks 50 to 1.
Ah well. Marking week 50 to 52 does not print output on the shell, while week 50 to 1 says: (evolution:32755): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `start < add_event_data->week_view->day_starts[num_days]' failed
I cannot reproduce missing events with actual trunk, means 2.26.1. I guess the issue with 2.24.2 was because of "backend busy" issue after a rewrite in bug #347287. I still can reproduce those runtime warnings, and after some investigation, the time range on a view's ECalModel is changed too late, after the UI time range notification, so the UI change reads components from the old interval. Changing time range in ECalModel before UI interval doesn't fix it too, because events are too fresh for the old UI view. Thus something more clever is needed here. The events are shown because every such change (from those two mentioned above) invokes view/UI regeneration, some changes more than once. I would like to know Chen's opinion before breaking anything here, as that seems to be an extensive change. If not in a code, then at least in behaviour. My proposal is to have some sort of locking/freezing for view updates, to not update too soon. What do you think, Chen?
I just want to add than I have the same or at least very similar problem as is described here, in 2.28.3. It is again not always reproducible but often happens to me when I scroll around in my calender. Random events don't show up until I scroll around some more and they reappear. It seams to happen more consistently at the first usage after a boot. This is probably the biggest nuisance I've found in Evolution. Great work.
Bob, could you run evolution from console, and check when you see some events missing, whether there will be any "Backend busy" warning on the console? There had been some fixes with this after 2.28.3, which are included in the current stable, 2.30.x, if I recall correctly. Note this usually happened with recurring events, not with non-recurring.
I actually get Evolution crashing now when I scroll enough. I hadn't used it a lot since my recent upgrade but I *thought* it had seen it dropping out events but now evolution actually crashes when I scroll enough. You hit it dead on Milan, I get: "libecal-Message: Failed to get recurrence objects for uid Backend is busy" about 10 times with: "Segmentation fault" at the end. Sorry for my misstatement about actually seeing dropped events (I'm pretty sure now I was just misremembering when my calenders were unexpectedly unchecked) but I am getting crashes in the same manner I remember getting dropped events in my previous install. I'll look into 2.30.x. Thanks!
*** Bug 596133 has been marked as a duplicate of this bug. ***
I'm closing this because actual stable (2.32.2) is not suffering of "Backend is busy" error. There wasn't other kind of reproducer here, especially with newer versions. I also found that if returned events are recurring and one is detached instance and this comes before master object then it's removed when master objects is received. I did commit some changes to evolution and evolution-data-server to prevent such things. Created commit a236208 in eds master (2.91.90+) Created commit b100881 in evo master (2.91.90+)