GNOME Bugzilla – Bug 475315
crash in Tasks: Deleted an e-mail addres...
Last modified: 2007-10-23 11:26:16 UTC
Version: 2.10 What were you doing when the application crashed? Deleted an e-mail address in the CC: field and clicked on the BCC: field when my friend Bug Buddy appeared. 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: OSX Memory status: size: 385048576 vsize: 385048576 resident: 133754880 share: 96759808 rss: 133754880 rss_rlim: 4294967295 CPU usage: start_time: 1189368649 rtime: 27204 utime: 24411 stime: 2793 cutime:3 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208928544 (LWP 3394)] [New Thread -1295774832 (LWP 8806)] [New Thread -1349112944 (LWP 3439)] [New Thread -1325761648 (LWP 3436)] 0x00110402 in __kernel_vsyscall ()
+ Trace 161672
Thread 1 (Thread -1208928544 (LWP 3394))
----------- .xsession-errors (17 sec old) --------------------- warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libssl.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libkrb5support.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libldap-2.3.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations beryl: water: GL_ARB_fragment_program is missing --------------------------------------------------
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 in the development version. The fix will be available in the next major software release. Thank you for your bug report.
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 458670 ***