GNOME Bugzilla – Bug 500421
crash in Tasks: Tömde papperskorg
Last modified: 2007-12-02 12:40:06 UTC
Version: 2.10 What were you doing when the application crashed? Tömde papperskorg Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Grand-Canyon Icon Theme: Clearlooks Memory status: size: 297050112 vsize: 297050112 resident: 104034304 share: 68222976 rss: 104034304 rss_rlim: 4294967295 CPU usage: start_time: 1196338513 rtime: 6760 utime: 6329 stime: 431 cutime:3881 cstime: 282 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 -1208550672 (LWP 3737)] [New Thread -1438131312 (LWP 4568)] [New Thread -1427641456 (LWP 4547)] [New Thread -1272468592 (LWP 4358)] [New Thread -1303671920 (LWP 3769)] [New Thread -1314161776 (LWP 3746)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 180086
Thread 1 (Thread -1208550672 (LWP 3737))
----------- .xsession-errors --------------------- report junk?? Re: en fråga (evolution:3737): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel' (evolution:3737): e-table-CRITICAL **: e_table_model_pre_change: assertion `E_IS_TABLE_MODEL (e_table_model)' failed report junk?? adresser report junk?? SV: Joulu Julitassa report junk?? Undelivered Mail Returned to Sender report junk?? VB: Fw: Cantabria-Spania report junk?? [SPAM] Look in the mirror and enjoy the new you --------------------------------------------------
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 ***