GNOME Bugzilla – Bug 478530
crash in Tasks: Started application Clic...
Last modified: 2007-09-24 17:37:01 UTC
Version: 2.10 What were you doing when the application crashed? Started application Clicked on Send/receive Send & Receive window poping up and showing that my first (pop) account has been checked and it's completed, my second account (pop) is getting message 1 of 2 and SMTP completed Then I got this error. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 117207040 vsize: 117207040 resident: 36696064 share: 29147136 rss: 36696064 rss_rlim: 4294967295 CPU usage: start_time: 1190280090 rtime: 89 utime: 80 stime: 9 cutime:1 cstime: 1 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 -1208551712 (LWP 8969)] [New Thread -1253495920 (LWP 9023)] [New Thread -1242567792 (LWP 8993)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 164084
Thread 1 (Thread -1208551712 (LWP 8969))
----------- .xsession-errors (169246 sec old) --------------------- Resolving wmscr1.dr.dk for AF_INET... Connecting to server wmscr1.dr.dk[195.85.253.69]: 1755... Connected unknown object unknown object file object, packet length = 5493 (5493) unknown object stream object, stream ID: 3 unknown object unknown object data object mmst packet_length = 5493 Cache size set to 2048 KBytes Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache f ...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 ***