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 571829 - Lock-up when attempting open_calendar_source
Lock-up when attempting open_calendar_source
Status: RESOLVED FIXED
Product: gnome-python-desktop
Classification: Deprecated
Component: evolution
2.25.x
Other Linux
: Normal normal
: ---
Assigned To: John Stowers
Python bindings maintainers
Depends on:
Blocks: 561354
 
 
Reported: 2009-02-15 13:35 UTC by Toms Bauģis
Modified: 2009-02-24 11:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Toms Bauģis 2009-02-15 13:35:53 UTC 
Deriving from bug 571503, something has changed in 2.25.90 version of evolution which results in a lockup when trying to get Tasks from evolution via API.

Sample code to reproduce the problem:

import evolution
from evolution import ecal
sources = ecal.list_task_sources()

data = ecal.open_calendar_source(sources[0][1],ecal.CAL_SOURCE_TYPE_TODO)
Comment 1 Michael 2009-02-23 12:39:48 UTC 
The test case seems to work here

Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49) 
[GCC 4.3.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import evolution
>>> from evolution import ecal
>>> sources = ecal.list_task_sources()
>>> 
>>> data = ecal.open_calendar_source(sources[0][1],ecal.CAL_SOURCE_TYPE_TODO)
** (process:28752): DEBUG: Opening calendar source uri: file:///home/michaelt/.evolution/tasks/local/system

>>> data
<ecal.ECal object at 0xb7d6d89c (ECal at 0x88762c0)>
Comment 2 John Stowers 2009-02-23 12:59:24 UTC 
Works for me to. There is a bug here somewhere, and I am convinced this has something to do with running in a threaded environment
Comment 3 Toms Bauģis 2009-02-23 15:21:19 UTC 
Hmmm, now updated to most recent version of Jaunty and now it also doesn't lock up anymore.
Now i wonder how do we turn this into something more scientific - wouldn't like to enable evo backend if there is a risk that users of 2.26 will catch the lockup.
Comment 4 Dominic Evans 2009-02-23 15:32:49 UTC 
can confirm the hang no longer occurs on latest Jaunty updates using the testcase in bug 571829

does gnome-python-desktop have a regression testsuite that this can be added to, in order to prevent the bug returning?
Comment 5 Gustavo Carneiro 2009-02-23 18:53:02 UTC 
(In reply to comment #4)
> can confirm the hang no longer occurs on latest Jaunty updates using the
> testcase in bug 571829
> 
> does gnome-python-desktop have a regression testsuite that this can be added
> to, in order to prevent the bug returning?

Yes.  Test case added.

So closing for now.  Re-open if it reappears.
Comment 6 John Stowers 2009-02-23 19:37:00 UTC 
Gustavo, can you please run my, *new*, test case from bug #561354 because I am still getting lockups.
Comment 7 John Stowers 2009-02-23 19:38:54 UTC 
Actually, can everyone please run that test and report their results?

This reliably triggers the bug on two Ubuntu Intrepid systems I tested.
Comment 8 Gian Mario Tagliaretti 2009-02-23 19:58:51 UTC 
I can confirm the bug, I'm on Ubuntu Intrepid as well as you.
Tomorrow I can try on Fedora 10.
Comment 9 Dominic Evans 2009-02-23 22:43:33 UTC 
John's test case in bug #561354 (http://bugzilla.gnome.org/show_bug.cgi?id=561354#c17) reliably triggers the problem on Ubuntu Jaunty with latest updates as of 2009/02/23
Comment 10 Gustavo Carneiro 2009-02-24 11:09:19 UTC 
Turned out to be needing to initialize bonobo before using e-d-s APIs.  Should be fixed now, if not reopen.