GNOME Bugzilla – Bug 537384
crash in Evolution Mail and Calendar: left evo running over we...
Last modified: 2008-06-16 21:36:20 UTC
What were you doing when the application crashed? left evo running over weekend 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: 198950912 vsize: 198950912 resident: 74469376 share: 24002560 rss: 74469376 rss_rlim: 4294967295 CPU usage: start_time: 1212768167 rtime: 14921 utime: 12214 stime: 2707 cutime:2965 cstime: 734 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 0xb68e06c0 (LWP 1661)] [New Thread 0xb19fdb90 (LWP 8561)] [New Thread 0xacf4cb90 (LWP 8560)] [New Thread 0xb250fb90 (LWP 12811)] [New Thread 0xb3d8db90 (LWP 12809)] [New Thread 0xb21feb90 (LWP 1789)] [New Thread 0xb4599b90 (LWP 1750)] [New Thread 0xb3496b90 (LWP 1732)] 0xb7fe5410 in __kernel_vsyscall ()
+ Trace 199924
Thread 2 (Thread 0xb19fdb90 (LWP 8561))
----------- .xsession-errors (52841 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 --------------------------------------------------
*** Bug 537385 has been marked as a duplicate of this bug. ***
Hey Reid, I'd say, this is bug 499975. Maybe you can find a testcase for that bug? *** This bug has been marked as a duplicate of 499975 ***