GNOME Bugzilla – Bug 486007
crash in Evolution: No se que pasa recien lo...
Last modified: 2007-10-12 13:22:42 UTC
What were you doing when the application crashed? No se que pasa recien lo abro y me sale esto, no entiendo................. 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-13mdvlegacy #1 SMP Fri Mar 23 19:05:24 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Ia Ora Orange Icon Theme: gnome Memory status: size: 108101632 vsize: 108101632 resident: 24645632 share: 17514496 rss: 24645632 rss_rlim: 4294967295 CPU usage: start_time: 1192191182 rtime: 189 utime: 165 stime: 24 cutime:2 cstime: 4 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 -1237506336 (LWP 8009)] [New Thread -1294054496 (LWP 8047)] [New Thread -1285661792 (LWP 8046)] [New Thread -1277269088 (LWP 8045)] [New Thread -1255449696 (LWP 8029)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 169719
Thread 1 (Thread -1237506336 (LWP 8009))
----------- .xsession-errors (188 sec old) --------------------- ** (gnome-terminal:7838): WARNING **: failure: no device event controller found. ** (gnome-terminal:7838): WARNING **: failure: no device event controller found. ** (gnome-terminal:7838): WARNING **: failure: no device event controller found. ** (gnome-terminal:7838): WARNING **: failure: no device event controller found. ...Too much output, ignoring rest... --------------------------------------------------
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 364700 ***