GNOME Bugzilla – Bug 504947
crash in Evolution Mail: Eine Mail geöffnet, und ...
Last modified: 2008-02-11 05:22:22 UTC
What were you doing when the application crashed? Eine Mail geöffnet, und bevor sie richtig angezeigt wurde, wieder geschlossen. Distribution: Debian lenny/sid Gnome Release: 2.20.1 2007-10-26 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 103768064 vsize: 103768064 resident: 27553792 share: 15290368 rss: 27553792 rss_rlim: 4294967295 CPU usage: start_time: 1198267833 rtime: 4027 utime: 3713 stime: 314 cutime:105 cstime: 96 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb67006b0 (LWP 14318)] [New Thread 0xb2b1cb90 (LWP 14562)] [New Thread 0xb3c40b90 (LWP 14508)] [New Thread 0xb4441b90 (LWP 14506)] [New Thread 0xb4c42b90 (LWP 14502)] [New Thread 0xb5701b90 (LWP 14433)] [New Thread 0xb5f83b90 (LWP 14431)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 182578
Thread 1 (Thread 0xb67006b0 (LWP 14318))
----------- .xsession-errors (31 sec old) --------------------- Major opcode: 19 Minor opcode: 0 Resource id: 0x1c04d2c X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x1c050f2 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x1c054f6 (evolution:14318): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel' (evolution:14318): e-table-CRITICAL **: e_table_model_pre_change: assertion `E_IS_TABLE_MODEL (e_table_model)' failed --------------------------------------------------
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 ***