GNOME Bugzilla – Bug 433646
crash in Evolution: replying to an e-mail
Last modified: 2007-06-21 21:51:48 UTC
What were you doing when the application crashed? replying to an e-mail Distribution: Mandriva Linux release 2007.1 (Official) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-5mdv #1 SMP Wed Sep 13 14:32:31 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Blue Icon Theme: gnome Memory status: size: 71782400 vsize: 71782400 resident: 21958656 share: 9089024 rss: 21958656 rss_rlim: 4294967295 CPU usage: start_time: 1177597763 rtime: 833 utime: 602 stime: 231 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/evolution-exchange-storage' (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1239447200 (LWP 21305)] [New Thread -1253889120 (LWP 24943)] [New Thread -1241199712 (LWP 24939)] [New Thread -1240859744 (LWP 21307)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 130726
Thread 3 (Thread -1241199712 (LWP 24939))
----------- .xsession-errors (11 sec old) --------------------- Resource id: 0x3c00029 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 25 Minor opcode: 0 Resource id: 0x3c00029 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 25 Minor opcode: 0 Resource id: 0x3c00008 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 25 Minor opcode: 0 Resource id: 0x3c00023 (evolution:21300): e-data-server-DEBUG: Loading categories from "/home/mbrice/.evolution/categories.xml" (evolution:21300): e-data-server-DEBUG: Loaded 29 categories --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 348258 ***