GNOME Bugzilla – Bug 355231
Creating appointment with attached email crashes Ev
Last modified: 2006-09-11 09:25:32 UTC
Distribution: Fedora Core release 5 (Bordeaux) Package: Evolution Severity: critical Version: GNOME2.14.3 2.6.x Gnome-Distributor: Red Hat, Inc Synopsis: Creating appointment with attached email crashes Ev Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: Attaching a mail message to an appointment crashes Evolution. Steps to reproduce the crash: 1. Create an appointment (File>New>Appointment) 2. Drag and drop an email message from an Inbox into the attachment bar for the appointment above 3. Crash (note: the UI does show the paper icon in the attachment bar just before the crash) Expected Results: Evolution should attach the email and not crash. How often does this happen? Always Additional Information: The attached email I tried resided in the inbox on an IMAP server. The header and body for the message had been downloaded fully before the attaching operation. The appointment was created in a local calendar. I am using Evolution 2.6.3 on a FC5 distribution. Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.6' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208330560 (LWP 3051)] [New Thread -1336161376 (LWP 3135)] [New Thread -1315812448 (LWP 3134)] [New Thread -1324205152 (LWP 3108)] [New Thread -1306940512 (LWP 3102)] [New Thread -1298547808 (LWP 3080)] [New Thread -1264723040 (LWP 3070)] [New Thread -1256330336 (LWP 3069)] [New Thread -1247937632 (LWP 3068)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 72023
Thread 1 (Thread -1208330560 (LWP 3051))
------- Bug created by bug-buddy at 2006-09-10 07:09 -------
*** This bug has been marked as a duplicate of 343369 ***