After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 319810 - Panel Calendar queries Evolution Data Server EDS slow startup
Panel Calendar queries Evolution Data Server EDS slow startup
Status: RESOLVED DUPLICATE of bug 413107
Product: gnome-panel
Classification: Other
Component: clock
2.12.x
Other All
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-10-26 03:05 UTC by David Escott
Modified: 2015-03-24 13:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description David Escott 2005-10-26 03:05:50 UTC 
Please describe the problem:
The first time the panel calender is clicked on the startup is interminable, (on
the order of 10-15 seconds when the load is high). I think this is because it is
querying EDS, because afterwards it is lightning fast. I don't even use
Evolutions calendar features, all I want to know is what day the 8th will be (or
something like that). Ideally it would display the calendar and then propogate
the events as they come in from EDS.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Vincent Untz 2005-12-31 11:07:18 UTC 
Totally agree.
Comment 2 Wouter Bolsterlee (uws) 2008-01-20 15:22:32 UTC 
I'm not sure whether it has to do with EDS, but opening the clock window takes > 1 second on my trunk build right now. This is a 1.73GHz processor with unused memory and load < 0.10, so that's not the reason. It's very annoying and should definitely be fixed sometime... perhaps using async querying/loading instead of waiting before the window shows up.
Comment 3 André Klapper 2009-12-19 21:45:16 UTC 
Bug 413107 is more active, hence closing as a dup of that one.

*** This bug has been marked as a duplicate of bug 413107 ***