Opening calendar applet on gnome-panel in Ubuntu 10.10 is slow

[PJSingh5000]

Binary package hint: gnome-panel

Clicking on the Clock applet on gnome-panel takes a few seconds to display the calendar. This occurs with Google Calendar enabled in Evolution and Evolution in "online" mode. With Evolution in "off-line" mode, the applet opens quickly.

In System Monitor, I can see the Network utilization spike each time I click on the Clock applet. Referencing Bug #87796, other users have suggested that the clock applet is retrieving information from Google each time it is opened.

This behavior is exhibited in Ubuntu 10.10 (x64).

[AlexHofbauer (alex-derhofbauer)]

Confirming that problem.

With four Google calendars (CalDAV) opening the clock applet takes about 5-7 seconds every time, depending on network connection.

[Kip Warner (kip)]

I confirm OP's observations. I am using local calendar and not Google Calendar backend though.

[Leonardo Montecchi (lmontecchi)]

I confirm this bug too, although I'm using network calendars other than Google's.

[homayoun (amirhomayoun26)]

I confirm it. If you have online calendars and if Evolution is in online mode, there is always a lag when you click on the clock applet (can go up to 5-6 seconds).

[Craig Barnes (craigbarnes-deactivatedaccount)]

I can also confirm this bug. It's extremely annoying when using the menu for task-list management.

[Scott_W (d38dm8nw81k1ng)]

As an extension to this issue: if you're offline when you click on the clock applet, the applet will freeze whilst it attempts to connect to Google Calendar.

[ropic (roberto-pineda-c)]

Same problem, with offline and online mode, without google calendar

[ropic (roberto-pineda-c)]

I discovered a curious issue that fix my problem

Disabling Tasks > On this Computer > Personal

Then i detect i have had a task with a lot of information, i deleted and reactivate Tasks > On this Computer > Personal

Now my calendar applet is working good

[wilbur.harvey (wilbur-harvey)]

I have the same issue, Ubuntu 10.10, latest updates, fast quad core machine with SSD.
By setting File-->Work Offline in Evolution, the problem went away.
I wasted half an hour researching and figuing out what to do.
I didn't have offline selected because I didn't want it selected, but that time delay is too annoying.
I am using a Google Calendar from my Evolution.

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version. Thanks in advance and sorry for the late response.

[Kip Warner (kip)]

Hey Pedro, I'm not running Natty, but perhaps someone else can confirm. Please don't close this bug, because it probably is still there in the newer Natty builds.

[PJSingh5000 (pjsingh5000)]

Pedro,

I am running Maverick, and I experience up to a 2 second delay clicking on the Clock applet before the calendar appears.

If the portion of code that responds to the first user click in the applet is the same in Natty as it was in Maverick, I would expect the issue is still there.

Is there someone on this bug report who has Natty and can check?

[PJSingh5000 (pjsingh5000)]

For testing, I just installed Natty in a x64 Virtual Machine.

I was rewarded with a "zippy" response from the Clock applet;
I do not notice a delay when clicking on the applet.

I think this issue is resolved in Natty.
If someone else can confirm, we may be able to close out this bug?

[Launchpad Janitor (janitor)]

[Expired for gnome-panel (Ubuntu) because there has been no activity for 60 days.]

[Martin Stjernholm (msub)]

I still experience this problem in Natty (haven't tested Oneiric since it's unusable on a desktop).

I can confirm that the delays are much worse with Google calendars as opposed to "On the Web" calendars.

[PJSingh5000 (pjsingh5000)]

I have not experienced this issue in 12.04 or 12.10 so I am marking it as "Fix Released" to bring closure to this bug.