GNOME Bugzilla – Bug 515948
clock window not shown if e-d-s has not authenticated to google calendar
Last modified: 2008-10-04 19:17:52 UTC
1 set up a google calendar in evo 2 log out & log in 3 open the clock applet by clicking the time of the day 4 wait forever because google calendar is not available unless evo authenticates it Nasty problem.
Reproduced here (was trying to figure out what the problem was, deleted Google Calendar entry -- now it works).
Does it eventually show up for either of you? For me, I can wait a long time (over 10 minutes) and it still won't show up, and gnome-panel hangs. (In reply to comment #1) > Reproduced here (was trying to figure out what the problem was, deleted Google > Calendar entry -- now it works). For what it's worth, just unchecking the calendar in Evo is enough for me, so you may not have to delete it completely.
Same here.
For me, this hangs gnome-panel forever. I let it sit for a few hours. It doesn't seem to slow down my computer at all because I browsed the web and use Eclipse while the panel was hung. Ultimately, I had to control-alt-backspace to get it to come back.
Bumping severity. I wanted to fix this for 2.22.1, but using e_cal_open_async() needs some important restructuring :/
*** Bug 525198 has been marked as a duplicate of this bug. ***
Bug 525198 has a backtrace that may be useful: attachment 108593 [details].
*** Bug 528601 has been marked as a duplicate of this bug. ***
I was wonder if there were any updates on this bug.
I'm having the same problem with a Zimbra account configured on Evolution 2.22. Here are the sources for the zimbra evolution connector. Simply not showing the Zimbra Calendar is ok. Is there any trick in the evolution connectors ? or does it come from the applet ?
Can confirm this here. Evolution/2.22.1.1 from Ubuntu 8.04/AMD64 with latest updates.
chen, suman: one week left until 2.22.3. any chance to get this improved/fixed?
Andre, am working on it. Will be posting the patch today or tomorrow.
Created attachment 113248 [details] [review] Opens the calendar asyncronously. Included exchange and groupwise protocols to the appointment filter.
*ping* - 2.22.3 release on monday.
Vuntz, Mark - could you review/test the patch please? :) Or, is it okay to commit it?
(In reply to comment #16) > Vuntz, Mark - could you review/test the patch please? :) > Or, is it okay to commit it? Why NEEDINFO? AFAIU, NEEDINFO means that more information is required, but that information must be given by the user, not the developer. In this case is required an action from the developers, not the user. According to in http://live.gnome.org/Bugsquad/TriageGuide every example using NEEDINFO belongs a information requested to the user. am I missing something?
(In reply to comment #17) > am I missing something? nope.. you are correct.. my bad :-/
I've committed the patch with slight changes. Hopefully, it still works :-) Thanks!
*** Bug 537947 has been marked as a duplicate of this bug. ***
Thanks everybody involved for resolving this for 2.22.3.
*** Bug 541070 has been marked as a duplicate of this bug. ***
*** Bug 552615 has been marked as a duplicate of this bug. ***
This has been marked as the same bug as launchpad 203527 (https://bugs.edge.launchpad.net/ubuntu/+source/gnome-panel/+bug/203527) but that bug has several people without google calender, and I'm seeing this hang on a fresh install of Ubuntu 8.10 with Gnome 2.23.91. Can anyone here take a look at the stacktraces in that bug report and help me find a duplicate or make a useful bug report here with gnome?