GNOME Bugzilla – Bug 492070
crash in Evolution: starting up
Last modified: 2008-02-11 04:44:36 UTC
What were you doing when the application crashed? starting up 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-14mdv #1 SMP Wed May 9 21:11:43 MDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Free Icon Theme: gnome Memory status: size: 44810240 vsize: 44810240 resident: 12140544 share: 9797632 rss: 12140544 rss_rlim: 4294967295 CPU usage: start_time: 1193834656 rtime: 23 utime: 17 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1237051680 (LWP 10924)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 174156
Thread 1 (Thread -1237051680 (LWP 10924))
----------- .xsession-errors (18 sec old) --------------------- X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3e00003 CalDAV Eplugin starting up ... (evolution:10888): libsoup-CRITICAL **: soup_message_set_request: assertion `SOUP_IS_MESSAGE (msg)' failed (evolution:10888): libsoup-CRITICAL **: soup_message_set_flags: assertion `SOUP_IS_MESSAGE (msg)' failed (evolution:10888): libsoup-CRITICAL **: soup_session_send_message: assertion `SOUP_IS_MESSAGE (msg)' failed X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3c00003 --------------------------------------------------
*** Bug 492094 has been marked as a duplicate of this bug. ***
*** Bug 512817 has been marked as a duplicate of this bug. ***
*** Bug 511801 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 453932 ***