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 311313 - Invalid remote calendar cause evolution-data-server to die
Invalid remote calendar cause evolution-data-server to die
Status: RESOLVED DUPLICATE of bug 271322
Product: libsoup
Classification: Core
Component: API
2.2.x
Other All
: High critical
: ---
Assigned To: Dan Winship
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-07-23 04:25 UTC by Michael Wiktowy
Modified: 2005-10-26 20:13 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
list of testing steps taken and gdb output (10.89 KB, text/plain)
2005-07-29 01:23 UTC, Michael Wiktowy 		Details

Description Michael Wiktowy 2005-07-23 04:25:19 UTC 
Steps to reproduce:
1. set up a remote calendar (webcal)
2. stop the webcal server or make it unavailable
3. try opening the calendar section of Evo or the popup calendar in the panel
clock applet.


Stack trace:
stack trace is unavailable as e-d-s is not run manually and seems to
automagically respawn.

Other information:
This bug causes Evo to lock up solid and makes it very hard to recover from. If
you switch to calendar view, it gets stuck there and prevents you from getting
back into you mail. It will also sometimes prevent mail folders from showing up.

May be related to gnome bug 300320.
Comment 1 Michael Wiktowy 2005-07-23 04:27:49 UTC 
e-d-s version is 1.0.4 but that was not an option in the bugzilla form
Evo version is 2.0.4
Distro is Fedora Core 3
Comment 2 Boris de Laage 2005-07-28 09:31:53 UTC 
It's possible to attach gdb to a running process, with the --pid command line
option.
Comment 3 Michael Wiktowy 2005-07-29 01:23:38 UTC 
Created attachment 49907 [details]
list of testing steps taken and gdb output

Thanks for the --pid tip. That isn't mentioned in the gdb man pages at all.
Attached are some steps that I tried to take to get some useful gdb backtraces.
Hopefully some of them are useful but unfortunately I could not capture things
as I might have wanted.
Comment 4 Chenthill P 2005-08-12 15:28:37 UTC 
I see from the traces that the crash happens in libsoup. Changing the component.
Comment 5 Dan Winship 2005-10-26 20:13:38 UTC 

*** This bug has been marked as a duplicate of 271322 ***