GNOME Bugzilla – Bug 584592
crash in Evolution Mail: 1. Create "Meeting" reco...
Last modified: 2009-06-02 13:01:14 UTC
What were you doing when the application crashed? 1. Create "Meeting" record 2. Edited "Meeting" record 2.1. Changed Time 2.2. Changed Event Repeating time (don't know how it is in English, cause using Ukrainian interface) from one to 1 time during next 2 weeks. 2.3. Clicked save 2.4. Got Bug Buddy :) Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.28.4-dv5-1004nr #1 SMP Tue Feb 10 11:35:38 EET 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Polycarbonate-One Icon Theme: G-Flat-SVG GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 796680192 vsize: 796680192 resident: 67739648 share: 29634560 rss: 67739648 rss_rlim: 18446744073709551615 CPU usage: start_time: 1243925138 rtime: 2413 utime: 2090 stime: 323 cutime:3 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fe24e396800 (LWP 12269)] [New Thread 0x7fe22bfff950 (LWP 15579)] [New Thread 0x7fe2315e4950 (LWP 12312)] [New Thread 0x7fe22699d950 (LWP 12310)] [New Thread 0x7fe227804950 (LWP 12286)] [New Thread 0x7fe22b7fe950 (LWP 12285)] [New Thread 0x7fe232e22950 (LWP 12275)] [New Thread 0x7fe233623950 (LWP 12273)] 0x00007fe24978031f in waitpid () from /lib/libpthread.so.0
+ Trace 215815
Thread 1 (Thread 0x7fe24e396800 (LWP 12269))
---- Critical and fatal warnings logged during execution ---- ** camel **: camel_object_is: assertion `o != NULL' failed ** evolution-mail **: mail_tools_folder_to_url: assertion `CAMEL_IS_FOLDER (folder)' failed ** calendar-gui **: simple_recur_to_comp: assertion `GTK_BIN (priv->special)->child != NULL' 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 579779 ***