Bug 584592 – crash in Evolution Mail: 1. Create "Meeting" reco...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 584592 - crash in Evolution Mail: 1. Create "Meeting" reco...


Summary:	crash in Evolution Mail: 1. Create "Meeting" reco...


Status:	RESOLVED DUPLICATE of bug 579779

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.26.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-06-02 07:43 UTC by abo
Modified:	2009-06-02 13:01 UTC

See Also:
GNOME target:	---
GNOME version:	2.25/2.26

Description abo 2009-06-02 07:43:04 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))

#0 waitpid
from /lib/libpthread.so.0
#1 IA__g_spawn_sync
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gspawn.c line 382
#2 IA__g_spawn_command_line_sync
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gspawn.c line 694
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 comp_util_sanitize_recurrence_master
at comp-util.c line 823
#6 save_comp
at comp-editor.c line 804
#7 save_comp_with_send
at comp-editor.c line 913
#8 action_save_cb
at comp-editor.c line 1186
#9 IA__g_closure_invoke
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gclosure.c line 767
#10 signal_emit_unlocked_R
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 3247
#11 IA__g_signal_emit_valist
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 2980
#12 IA__g_signal_emit
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 3037
#13 _gtk_action_emit_activate
at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtkaction.c line 727
#14 button_clicked
at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtktoolbutton.c line 705
#15 IA__g_closure_invoke
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gclosure.c line 767
#16 signal_emit_unlocked_R
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 3247
#17 IA__g_signal_emit_valist
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 2980
#18 IA__g_signal_emit
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 3037
#19 gtk_real_button_released
at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtkbutton.c line 1702
#20 IA__g_closure_invoke
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gclosure.c line 767
#21 signal_emit_unlocked_R
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 3177
#22 IA__g_signal_emit_valist
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 2980
#23 IA__g_signal_emit
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 3037
#24 gtk_button_button_release
at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtkbutton.c line 1594
#25 _gtk_marshal_BOOLEAN__BOXED
at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtkmarshalers.c line 84
#26 IA__g_closure_invoke
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gclosure.c line 767
#27 signal_emit_unlocked_R
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 3285
#28 IA__g_signal_emit_valist
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 2990
#29 IA__g_signal_emit
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gsignal.c line 3037
#30 gtk_widget_event_internal
at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtkwidget.c line 4761
#31 IA__gtk_propagate_event
at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtkmain.c line 2396
#32 IA__gtk_main_do_event
at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtkmain.c line 1601
#33 gdk_event_dispatch
at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkevents-x11.c line 2364
#34 IA__g_main_context_dispatch
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c line 1814
#35 g_main_context_iterate
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c line 2448
#36 IA__g_main_loop_run
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c line 2656
#37 bonobo_main
from /usr/lib/libbonobo-2.so.0
#38 main
at main.c line 704
#0 waitpid
from /lib/libpthread.so.0



---- 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

Comment 1 Fabio Durán Verdugo 2009-06-02 13:01:14 UTC

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 ***