GNOME Bugzilla – Bug 457267
crash in Evolution: Lancement Edition / Préf...
Last modified: 2007-07-19 13:07:32 UTC
What were you doing when the application crashed? Lancement Edition / Préférences Distribution: Mandriva Linux release 2007.1 (Official) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Ia Ora Blue Icon Theme: gnome Memory status: size: 218767360 vsize: 218767360 resident: 35557376 share: 22355968 rss: 35557376 rss_rlim: 4294967295 CPU usage: start_time: 1184562907 rtime: 304 utime: 288 stime: 16 cutime:2 cstime: 6 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 -1237399840 (LWP 5505)] [New Thread -1378956384 (LWP 5550)] [New Thread -1370080352 (LWP 5549)] [New Thread -1361687648 (LWP 5548)] [New Thread -1298642016 (LWP 5523)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 148285
Thread 1 (Thread -1237399840 (LWP 5505))
----------- .xsession-errors (6 sec old) --------------------- GTK Accessibility Module initialized ** (gnome_segv:5560): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (gnome_segv:5560): WARNING **: IOR not set. ** (gnome_segv:5560): WARNING **: Could not locate registry Bonobo accessibility support initialized GTK Accessibility Module initialized ** (bug-buddy:5561): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (bug-buddy:5561): WARNING **: IOR not set. ** (bug-buddy:5561): WARNING **: Could not locate registry --------------------------------------------------
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 ***