GNOME Bugzilla – Bug 532480
crash in Evolution Mail and Calendar: It
Last modified: 2009-02-13 12:20:33 UTC
What were you doing when the application crashed? It's not possible to write a new message or answer to a previous one. Evolution crashes. Distribution: openSUSE 10.3 (X86-64) Gnome Release: 2.22.1 2008-04-08 (GNOME.Org) BugBuddy Version: 2.22.0 System: Linux 2.6.25-26.1-default #1 SMP 2008-04-30 07:56:05 +0200 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: imetalV3e Icon Theme: Docang Memory status: size: 575229952 vsize: 575229952 resident: 52916224 share: 25841664 rss: 52916224 rss_rlim: 893900800 CPU usage: start_time: 7820 rtime: 1962 utime: 1848 stime: 114 cutime:55 cstime: 27 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [?1034hUsing host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x7f8bcfca46f0 (LWP 11627)] [New Thread 0x408c0950 (LWP 11650)] 0x00007f8bc3f8a7bf in __libc_waitpid (pid=11827, stat_loc=0x7fffd7d190b0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 197372
Thread 1 (Thread 0x7f8bcfca46f0 (LWP 11627))
----------- .xsession-errors --------------------- ** (evolution:11627): WARNING **: invalid source position for horizontal gradient ** (evolution:11627): WARNING **: invalid source position for horizontal gradient ** (evolution:11627): WARNING **: invalid source position for horizontal gradient ** (evolution:11627): WARNING **: invalid source position for horizontal gradient (evolution:11627): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed glibtop: cannot find btime in /proc/stat: No existe el fichero o el directorio 41 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory. --------------------------------------------------
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 502914 ***