Description of problem:
Periodically starting and using Evolution in RHEL 5.2 beta generates backtraces
in evolution-data-server-1.12. Evolution does _not_ crash but the backtraces are
Version-Release number of selected component (if applicable):
rpm -qa | grep evolution
Occurs frequently when starting and using Evolution in 5.2 beta, although no
known steps to reliably reproduce.
Steps to Reproduce:
attaching generated backtrace
Created attachment 300058 [details]
Can you please install the following debuginfo packages and submit a new
sure... where do I get the debuginfo packages?
I believe there's an RHN channel for them, but I'm never been real clear to me.
If you're behind the VPN, I usually just grab them from brewroot.
(Make sure these links agree with the package versions you have installed.)
Created attachment 300128 [details]
Backtrace with debuginfo
Note: backtrace occurs with regularity when starting Evolution the first time
for a new login session. Exiting and restarting Evolution without logging
out/logging in again does not appear to cause the problem as much/at all.
The new backtrace looks good. Thanks.
Evolution appears to be dying in its CalDAV module.
That sounds right; I just received another backtrace when someone sent me a
Chris, could you possibly attach a calendar invite here that causes the crash
for you, so we can try to reproduce it for ourselves?
Unfortunately I no longer have access to a system with this software installed.
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
(In reply to comment #11)
> Unfortunately I no longer have access to a system with this software installed.
Ouch, the data seems to be crucial for this report to be fixed properly.
I reinvestigated and based on the source lines, it seems your uri in a CalDAV preferences was broken, thus the soup_message_new returned NULL.
This had been fixed recently, in bug #477815. We can backport that fix.
(In reply to comment #3)
> sure... where do I get the debuginfo packages?
For posterity, you can grab debuginfo packages from RHN or public FTP server.
Máirín has a redirector to proper FTP directory:
On RHEL5, you should be able to fetch them from public FTP using:
yum install foo-debuginfo --enablerepo rhel-debuginfo
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.