GNOME Bugzilla – Bug 466624
crash in Evolution: Getting mail prefences f...
Last modified: 2007-08-17 09:33:30 UTC
Version: 2.12.x What were you doing when the application crashed? Getting mail prefences from "Edit" title Distribution: openSUSE 10.3 (X86-64) Alpha7 Gnome Release: 2.19.4 2007-07-31 (SUSE) BugBuddy Version: 2.18.1 System: Linux 2.6.22.1-10-default #1 SMP 2007/07/27 07:42:18 UTC x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Gilouche Icon Theme: Industrial Memory status: size: 651849728 vsize: 651849728 resident: 30982144 share: 68972544 rss: 99954688 rss_rlim: 888417280 CPU usage: start_time: 516034 rtime: 974 utime: 884 stime: 90 cutime:30 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b42520e4690 (LWP 2837)] [New Thread 0x42845950 (LWP 2943)] [New Thread 0x42044950 (LWP 2937)] [New Thread 0x42003950 (LWP 2936)] [New Thread 0x41802950 (LWP 2917)] [New Thread 0x41001950 (LWP 2913)] [New Thread 0x40800950 (LWP 2867)] (no debugging symbols found) 0x00002b424bf59acf in waitpid () from /lib64/libpthread.so.0
+ Trace 155153
Thread 1 (Thread 0x2b42520e4690 (LWP 2837))
----------- .xsession-errors --------------------- ** (gnome_segv:4412): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (gnome_segv:4412): WARNING **: IOR not set. ** (gnome_segv:4412): WARNING **: Could not locate registry Bonobo accessibility support initialized GTK Accessibility Module initialized ** (bug-buddy:4413): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (bug-buddy:4413): WARNING **: IOR not set. ** (bug-buddy:4413): WARNING **: Could not locate registry glibtop: cannot find btime in /proc/stat: 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 426496 ***