GNOME Bugzilla – Bug 338279
Crash when sending Exchange invitation with attachement
Last modified: 2006-09-01 04:39:43 UTC
Distribution: Gentoo Base System version 1.12.0_pre17 Package: Evolution Severity: critical Version: GNOME2.12.3 2.4.x Gnome-Distributor: Gentoo Synopsis: Crash when sending Exchange invitation with attachement Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.12.1) Description: Description of the crash: Crashed trying to send a meeting invitation using Exchange and Exchange Calendar with an attachment (an email message, dragged-n-dropped). Steps to reproduce the crash: 1. Create Meeting with participants, etc. Use Exchange calendar to see busy/free times. 2. Drag message and drop into Attachment Bar 3. Press OK. Expected Results: Meeting dialog disappears & email sent. How often does this happen? Every time I try this particular sequence of actions. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47089538956288 (LWP 13392)] [New Thread 1216682320 (LWP 13465)] [New Thread 1157933392 (LWP 13410)] [New Thread 1157667152 (LWP 13409)] [New Thread 1149274448 (LWP 13408)] [New Thread 1140881744 (LWP 13406)] [New Thread 1132489040 (LWP 13405)] [New Thread 1124096336 (LWP 13404)] [New Thread 1115703632 (LWP 13403)] [New Thread 1107310928 (LWP 13402)] [New Thread 1098918224 (LWP 13401)] [New Thread 1090525520 (LWP 13396)] [New Thread 1082132816 (LWP 13395)] 0x00000030fc00c92f in waitpid () from /lib/libpthread.so.0
+ Trace 67598
Thread 1 (Thread 47089538956288 (LWP 13392))
Vladimir G. Ivanovic Palo Alto, CA 94306 +1 650 678 8014 ------- Bug created by bug-buddy at 2006-04-12 23:40 ------- Bugreport had an attachment. This cannot be imported to Bugzilla. Contact bugmaster@gnome.org if you are willing to write a patch for this.
unqiue stacktrace according to simple-dup-finder
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Bug is reproducible always, stack traces in my system.
+ Trace 69725
Thread 1 (Thread -1233693008 (LWP 25284))
*** This bug has been marked as a duplicate of 343369 ***