GNOME Bugzilla – Bug 486882
crash in Evolution Mail: Opening an IMAP folder
Last modified: 2007-10-28 14:07:57 UTC
What were you doing when the application crashed? Opening an IMAP folder Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-amd64 #1 SMP Tue Jul 10 21:39:38 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 660766720 vsize: 660766720 resident: 227463168 share: 20389888 rss: 227463168 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192446888 rtime: 38068 utime: 32978 stime: 5090 cutime:1 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b2e67f56860 (LWP 25810)] [New Thread 0x42003950 (LWP 26345)] [New Thread 0x43847950 (LWP 25874)] [New Thread 0x43806950 (LWP 25868)] [New Thread 0x43005950 (LWP 25852)] [New Thread 0x42804950 (LWP 25833)] [New Thread 0x41802950 (LWP 25830)] [New Thread 0x41001950 (LWP 25828)] [New Thread 0x40800950 (LWP 25827)] (no debugging symbols found) 0x00002b2e6004bc7f in waitpid () from /lib/libpthread.so.0
+ Trace 170372
Thread 1 (Thread 0x2b2e67f56860 (LWP 25810))
----------- .xsession-errors (3718754 sec old) --------------------- ** (tsclient:17341): WARNING **: Autoselected keyboard map en-us WARNING: Remote desktop does not support colour depth 24; falling back to 16 NOT IMPLEMENTED: System pointer message 0x7f00 X Error of failed request: BadAtom (invalid Atom parameter) Major opcode of failed request: 23 (X_GetSelectionOwner) Atom id in failed request: 0x0 Serial number of failed request: 627 Current serial number in output stream: 627 ...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 239441 ***