GNOME Bugzilla – Bug 455420
crash in Email: xcv
Last modified: 2007-07-11 18:39:38 UTC
What were you doing when the application crashed? xcv Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 93253632 vsize: 93253632 resident: 23220224 share: 14966784 rss: 23220224 rss_rlim: 4294967295 CPU usage: start_time: 1184046892 rtime: 191 utime: 155 stime: 36 cutime:0 cstime: 1 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/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209153824 (LWP 20680)] (no debugging symbols found) 0x0052d402 in __kernel_vsyscall ()
+ Trace 146912
Thread 1 (Thread -1209153824 (LWP 20680))
----------- .xsession-errors (27 sec old) --------------------- The user is root. Oracle Universal Installer cannot continue installation if the user is root. : No such file or directory (gnome-terminal:16612): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-terminal:16612): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-help:18275): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed (vino-preferences:20673): GLib-CRITICAL **: g_base64_decode_step: assertion `out != NULL' failed CalDAV Eplugin starting up ... (evolution:20680): evolution-smime-WARNING **: initializing security library without cert databases. (evolution:20680): e-data-server-DEBUG: Loaded default categories --------------------------------------------------
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 425129 ***