GNOME Bugzilla – Bug 472050
crash in Tasks: was copying and pasting ...
Last modified: 2007-12-04 18:24:25 UTC
Version: 2.10 What were you doing when the application crashed? was copying and pasting a resolved name from my personal address book from the CC to the BCC field 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.18-8.1.8.el5xen #1 SMP Tue Jul 10 07:06:45 EDT 2007 x86_64 X Vendor: The XFree86 Project, Inc X Vendor Release: 40300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 858632192 vsize: 858632192 resident: 120287232 share: 90316800 rss: 120287232 rss_rlim: 18446744073709551615 CPU usage: start_time: 1188514339 rtime: 879 utime: 704 stime: 175 cutime:202 cstime: 44 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912498520224 (LWP 5044)] [New Thread 1115699536 (LWP 5124)] [New Thread 1115965776 (LWP 5104)] [New Thread 1084229968 (LWP 5079)] (no debugging symbols found) 0x0000003e39a0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 159236
Thread 1 (Thread 46912498520224 (LWP 5044))
----------- .xsession-errors (32272531 sec old) --------------------- XIO: fatal IO error 104 (Connection reset by peer) on X server "unix:1000.0" after 0 requests (0 known processed) with 0 events remaining. --------------------------------------------------
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 469574 ***
*** Bug 478502 has been marked as a duplicate of this bug. ***
*** Bug 478873 has been marked as a duplicate of this bug. ***