GNOME Bugzilla – Bug 491788
crash in Evolution: Borrando correos de una ...
Last modified: 2007-12-19 03:24:23 UTC
What were you doing when the application crashed? Borrando correos de una carpeta remota en evolution Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Beastie Icon Theme: gartoon Memory status: size: 572301312 vsize: 572301312 resident: 52060160 share: 20656128 rss: 52060160 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193709507 rtime: 4211 utime: 3839 stime: 372 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.10' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2aeef2c58f90 (LWP 18747)] [New Thread 0x43847950 (LWP 18795)] [New Thread 0x43806950 (LWP 18793)] [New Thread 0x43005950 (LWP 18792)] [New Thread 0x42804950 (LWP 18773)] [New Thread 0x42003950 (LWP 18772)] [New Thread 0x41001950 (LWP 18766)] [New Thread 0x40800950 (LWP 18764)] (no debugging symbols found) 0x00002aeeeab3cc7f in waitpid () from /lib/libpthread.so.0
+ Trace 173965
Thread 1 (Thread 0x2aeef2c58f90 (LWP 18747))
----------- .xsession-errors (91134 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ...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 426496 ***