Bug 237153 - No existing events displayed on start up in Month view
Summary: No existing events displayed on start up in Month view
Status: VERIFIED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-10 21:11 UTC by Sabine Faure
Modified: 2010-07-04 23:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sabine Faure 2010-05-10 21:11:02 UTC
Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

- Prerequisite: having at least ten already existing events.
- Switch on your computer
- Launch KOrg
- Click on 'Month view' button

No existing event is displayed until you uncheck and recheck the calendars in the folders/resources view.

Once you do that the existing events are displayed properly.

Note: this only seems to happen after I build a new revision. If I just switch off my computer and switch it on again the bug does not happen.

Also a newly created event is not displayed when created before redisplaying all the existing events. 
Even when the existing events are displayed again the new event is still not displayed in Month or Agenda view until quitting and relaunching KOrg.

Trunk, Svn Rev 1125123
Comment 1 Sergio Martins 2010-06-02 20:15:37 UTC
SVN commit 1133884 by smartins:


Finally found the cause behind events not appearing at startup from time to time.

Race between the model used by AkonadiCollectionView and calendarSearch's model, when the first model's selection model
gets an item selected calendarSearch's model might not know about the collection yet.


BUG: 237153


 M  +4 -1      calendarsearch.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1133884
Comment 2 Sabine Faure 2010-07-04 23:56:55 UTC
This has not happened in a while now so I think it is corrected now.

So I am verifying this bug now.

Trunk, Svn Rev 1145265