GNOME Bugzilla – Bug 461867
crash in Evolution: updating mono
Last modified: 2007-08-01 13:27:36 UTC
Version: 2.12.x What were you doing when the application crashed? updating mono Distribution: openSUSE 10.3 (X86-64) Alpha6plus Gnome Release: 2.19.4 2007-07-21 (SUSE) BugBuddy Version: 2.18.1 System: Linux 2.6.22.1-6-default #1 SMP 2007/07/23 08:21:49 UTC x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70000001 Selinux: No Accessibility: Enabled GTK+ Theme: QtCurve Icon Theme: Tango Memory status: size: 505901056 vsize: 505901056 resident: 19615744 share: 51281920 rss: 70897664 rss_rlim: 1569331200 CPU usage: start_time: 242478 rtime: 766 utime: 685 stime: 81 cutime:35 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 0x2b01fa1dcba0 (LWP 1477)] [New Thread 0x41843950 (LWP 1524)] [New Thread 0x41802950 (LWP 1521)] [New Thread 0x41001950 (LWP 1519)] [New Thread 0x40800950 (LWP 1518)] (no debugging symbols found) 0x00002b01f4053acf in waitpid () from /lib64/libpthread.so.0
+ Trace 151643
Thread 1 (Thread 0x2b01fa1dcba0 (LWP 1477))
----------- .xsession-errors --------------------- (bug-buddy:3336): GConf-WARNING **: Owner of /tmp/gconfd-david2 is not the current user (bug-buddy:3336): GConf-WARNING **: Owner of /tmp/gconfd-david3 is not the current user Bonobo accessibility support initialized GTK Accessibility Module initialized ** (bug-buddy:3336): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (bug-buddy:3336): WARNING **: IOR not set. ** (bug-buddy:3336): 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 the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 426496 ***