GNOME Bugzilla – Bug 520075
crash in Evolution:
Last modified: 2008-03-03 20:50:59 UTC
What were you doing when the application crashed? 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-16mdv #1 SMP Wed Sep 26 16:10:48 EDT 2007 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: 128962560 vsize: 128962560 resident: 27566080 share: 16175104 rss: 27566080 rss_rlim: 4294967295 CPU usage: start_time: 1204545173 rtime: 770 utime: 592 stime: 178 cutime:2 cstime: 6 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 -1237358880 (LWP 4507)] [New Thread -1320158304 (LWP 4547)] [New Thread -1310012512 (LWP 4529)] [New Thread -1281360992 (LWP 4528)] [New Thread -1271338080 (LWP 4527)] [New Thread -1262945376 (LWP 4526)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 191143
Thread 1 (Thread -1237358880 (LWP 4507))
----------- .xsession-errors (7 sec old) --------------------- (bug-buddy:4487): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x4200003 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0xa0007b CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4507): DEBUG: mailto URL command: evolution %s ** (evolution:4507): DEBUG: mailto URL program: evolution (evolution:4507): e-data-server-WARNING **: Could not open converter for 'X-roman8' to 'UTF-8' charset --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 364700 ***