Distribution: Debian 3.1
Package: Evolution
Priority: Blocker
Version: GNOME2.8.1 2.0.3
Gnome-Distributor: Debian
Synopsis: slight deviations in vCal-format cause evolution-crash
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.0.3
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
Upon viewing a mail with a slightly broken vCal-attachment, evolution
crashes.

Steps to reproduce the crash:

1. write these lines to a file:
=== start ===
BEGIN:VCALENDAR
PRODID:-//DUMMY//blah//EN
VERSION:1.0
BEGIN:VEVENT
DTSTART:20041213T160000Z
DTEND:20041213T220000Z
DESCRIPTION; ENCODING=QUOTED-PRINTABLE: blah...
SUMMARY: blah...
LOCATION: blah...
END:VEVENT
END:VCALENDAR
=== end ===
Note, that there is a single blank before "ENCODING=".
This blank triggers the bug. (Other deviations may do, too, 
but I happened to stumble over that extra blank.)

2. mail or copy a mail with this file attached to one of evolution's
     mail-folders.  In my tests, the attachment was base64 encoded. 
     This may or may not be necessary for reproducing the bug.

3. View the mail with evolution: crash.

Expected Results:
  evolution really should not crash with any kind of rubbish sent as
vCal attachment.

How often does this happen?
  100% deterministically. - whenever I view such a mail.

Additional Information:
   On request, I can provide a crash.mbox file that crashes evo.


Debugging Information:

I've condensed a bunch of "(no debugging symbols found)"-lines,
leaving just the first and last of each separate bunch, plus 
a note of the number of elided lines.

There is a thread with SSL-stuff.  This is, because I've 
got an imaps-box configured. Though, my testcase was
in a local folder, so it crashed while the dialog for 
accepting imaps-server's certificate was still waiting
for my Ok/Cancel.

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
((( 51 "no debugging symbols found" lines elided)))
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1094487616 (LWP 32187)]
[New Thread 1164786608 (LWP 32197)]
[New Thread 1156398000 (LWP 32196)]
[New Thread 1148009392 (LWP 32194)]
[New Thread 1138121648 (LWP 32193)]
[New Thread 1129712560 (LWP 32191)]
[New Thread 1121323952 (LWP 32190)]
[New Thread 1112935344 (LWP 32189)]
(no debugging symbols found)
((( 61 "no debugging symbols found" lines elided)))
(no debugging symbols found)
0x40f90511 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 55259

Unknown reporter: avl@logic.at, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.