GNOME Bugzilla – Bug 537385
crash in Evolution Mail and Calendar: restart after prior cras...
Last modified: 2008-10-03 16:43:34 UTC
What were you doing when the application crashed? restart after prior crash - evo sync'ing mailbox data Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.22.2 2008-06-02 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.24-gentoo-r8 #1 SMP PREEMPT Tue May 13 08:35:55 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: marble-look Icon Theme: gnome Memory status: size: 141852672 vsize: 141852672 resident: 40079360 share: 19742720 rss: 40079360 rss_rlim: 4294967295 CPU usage: start_time: 1213010867 rtime: 475 utime: 387 stime: 88 cutime:139 cstime: 32 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/evo/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb68766c0 (LWP 22804)] [New Thread 0xb1403b90 (LWP 23362)] [New Thread 0xb4d30b90 (LWP 23355)] [New Thread 0xb3bfeb90 (LWP 22915)] [New Thread 0xb1326b90 (LWP 22911)] [New Thread 0xb43ffb90 (LWP 22889)] [New Thread 0xb2b29b90 (LWP 22888)] [New Thread 0xb332ab90 (LWP 22879)] 0xb7f7b410 in __kernel_vsyscall ()
+ Trace 199925
Thread 4 (Thread 0xb3bfeb90 (LWP 22915))
----------- .xsession-errors (226224 sec old) --------------------- compiz (animation) - Debug: polygon.c: pset null at line 1443 compiz (animation) - Debug: polygon.c: pset null at line 1443 compiz (animation) - Debug: polygon.c: pset null at line 1443 compiz (animation) - Debug: polygon.c: pset null at line 1443 compiz (animation) - Debug: polygon.c: pset null at line 1443 compiz (animation) - Debug: polygon.c: pset null at line 1443 ########### /usr/bin/lsof -F +c0 -s ########### /usr/bin/lsof -F +c0 -s ########### /usr/bin/lsof -F +c0 -s --------------------------------------------------
possibly a duplicate of bug #537384 *** This bug has been marked as a duplicate of 537384 ***
*** Bug 548902 has been marked as a duplicate of this bug. ***