GNOME Bugzilla – Bug 451016
crash in Evolution: Opened application for t...
Last modified: 2007-06-26 17:18:40 UTC
Version: 2.12.x What were you doing when the application crashed? Opened application for the first time after update Distribution: Mandriva Linux release 2008.0 (Cooker) for i586 Gnome Release: 2.19.4 2007-06-17 (Mandriva) BugBuddy Version: 2.18.1 System: Linux 2.6.17-5mdv #1 SMP Wed Sep 13 14:32:31 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 211832832 vsize: 211832832 resident: 57225216 share: 49889280 rss: 57225216 rss_rlim: 4294967295 CPU usage: start_time: 1182798202 rtime: 145 utime: 128 stime: 17 cutime:0 cstime: 0 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 -1237739808 (LWP 5391)] [New Thread -1385743456 (LWP 5423)] [New Thread -1394136160 (LWP 5422)] [New Thread -1368958048 (LWP 5409)] [New Thread -1360565344 (LWP 5408)] [New Thread -1352172640 (LWP 5407)] [New Thread -1343779936 (LWP 5406)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 143655
Thread 1 (Thread -1237739808 (LWP 5391))
----------- .xsession-errors (6 sec old) --------------------- ** (gnome_segv:5426): WARNING **: Could not locate registry Bonobo accessibility support initialized GTK Accessibility Module initialized ** (bug-buddy:5427): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (bug-buddy:5427): WARNING **: IOR not set. ** (bug-buddy:5427): WARNING **: Could not locate registry X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 160 Minor opcode: 6 Resource id: 0xc1 QApplication::postEvent: Unexpected null receiver --------------------------------------------------
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 425093 ***