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 552615 - Calendar blocked
Calendar blocked
Status: RESOLVED DUPLICATE of bug 515948
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-09-17 10:39 UTC by Carlos
Modified: 2008-09-21 15:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Carlos 2008-09-17 10:39:05 UTC 
Please describe the problem:
If I add a new google calendar in Evolution, the calendar in the superior panel gets blocked when I try to see it, and this cause that whole the deskbar gets blocked.
If I remove that new google calendar in Evolution, the calendar work properly.

I think, the connection to google calendar cause this. I recommend you that the connection could be in a different thread and not in the same thread of events processing.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?
Yes

Other information:
Comment 1 Sebastian Pölsterl 2008-09-18 09:43:35 UTC 
This bug is not related to deskbar-applet. Reassigning to evolution team.
Comment 2 Carlos 2008-09-20 21:00:13 UTC 
Yes, but the calendar applet(the About... say "Clock 2.22.2") could be more robust if the connection to evolution calendar service is in a different thread.
So I recommend you the changing in some little features in the architecture.
Comment 3 Carlos 2008-09-20 21:01:50 UTC 
(In reply to comment #1)
> This bug is not related to deskbar-applet. Reassigning to evolution team.
> 

Yes, but the calendar applet(the About... say "Clock 2.22.2") could be more
robust if the connection to evolution calendar service is in a different
thread.
So I recommend you the changing in some little features in the architecture.
Comment 4 André Klapper 2008-09-21 15:03:00 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 515948 ***
Comment 5 André Klapper 2008-09-21 15:03:41 UTC 
This is fixed in Evolution 2.22.3. Please update, or ask your distribution for updates.