abrt detected a crash. How to reproduce ----- 1. 2. 3. Additional information ====== Attached files ---- backtrace cmdline ----- evolution --sm-config-prefix /evolution-ndfMJR/ --sm-client-id 102b2cdf088414cebd125593832925581700000012700080 --screen 0 component ----- evolution executable ----- /usr/bin/evolution kernel ----- 2.6.31.5.bernie package ----- evolution-2.28.0-2.fc12 reason ----- Process was terminated by signal 11
Created attachment 366545 [details] File: backtrace
*** Bug 531682 has been marked as a duplicate of this bug. ***
I could reproduce it by clicking on a message in message list. Noteworthy facts: * It only seems to happen in offline mode * It does not happen all the time, so it seems like a race condition * The column you click on does not seem to matter * A single click is sufficient to trigger the bug, but also a double-click will. I'm not publishing the coredump because it might contain my IMAP and SMTP passwords. If you need to analyze this, I could send it privately.
It's crashing in an autosave of a (previously?) composed message. Is it that you composed a message, maybe saved it as a draft, and then closed it, gone offline, and while playing with other message in a message list, the timeout of the autosave triggered and it tried to save something what doesn't exist any more? Thread 1 (Thread 1772): #0 command (html=0x0, com_type=GTK_HTML_COMMAND_SAVE_DATA_ON) at gtkhtml.c:5071 #1 0x000000300903eadd in gtk_html_command (html=0x0, command_name= 0x30092cdac0 "\215") at gtkhtml.c:6009 #2 0x00007fdd037d028d in build_message (r=0x4105c30, html_content=<value optimized out>, save_html_object_data=<value optimized out>) at e-msg-composer.c:593 #3 0x00007fdd037d09e0 in e_msg_composer_get_message_draft (r=0x4105c30) at e-msg-composer.c:3717 #4 0x00007fdd037c6f2a in autosave_snapshot_cb (autosave_file=0x5e03a00, result=0x7fdcb40aed80, data=0x3c44a40) at e-composer-autosave.c:325
(In reply to comment #4) > It's crashing in an autosave of a (previously?) composed message. Is it that > you composed a message, maybe saved it as a draft, and then closed it, gone > offline, and while playing with other message in a message list, the timeout of > the autosave triggered and it tried to save something what doesn't exist any > more? It could very well be. I always have a bunch of unfinished messages open in the background :-)
*** Bug 532636 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > ... while playing with other message in a message list, the timeout of > the autosave triggered and it tried to save something what doesn't exist any > more No, I just tried this and it cannot happen. but there is one possibility, I see quite many runtime warnings on console when I'm closing evolution while at least one composer is opened. It starts with > gtk_ui_manager_get_action_groups: assertion `GTK_IS_UI_MANAGER (self)' failed and the message is actually not saved, as the recover on next start shows an empty message with "No Subject" as a subject text. Are you able to collect more detailed steps what to do, please? As this is crashing for you on a different place than mine critical warnings are coming from.
In my case it happens in online mode. I only have one account defined, and it is a MS Exchange account. I use evolution-mapi.
*** Bug 536821 has been marked as a duplicate of this bug. ***
I found an upstream bug [1] for this, thus moving it there. Thank you all for cooperation. [1] https://bugzilla.gnome.org/show_bug.cgi?id=596566
*** Bug 537211 has been marked as a duplicate of this bug. ***
*** Bug 537923 has been marked as a duplicate of this bug. ***
*** Bug 538194 has been marked as a duplicate of this bug. ***
*** Bug 539089 has been marked as a duplicate of this bug. ***
*** Bug 530546 has been marked as a duplicate of this bug. ***
*** Bug 540823 has been marked as a duplicate of this bug. ***
*** Bug 540828 has been marked as a duplicate of this bug. ***
*** Bug 541365 has been marked as a duplicate of this bug. ***
*** Bug 540542 has been marked as a duplicate of this bug. ***
*** Bug 543657 has been marked as a duplicate of this bug. ***
*** Bug 543902 has been marked as a duplicate of this bug. ***
*** Bug 543904 has been marked as a duplicate of this bug. ***
*** Bug 544267 has been marked as a duplicate of this bug. ***
*** Bug 545071 has been marked as a duplicate of this bug. ***
*** Bug 545566 has been marked as a duplicate of this bug. ***
*** Bug 545716 has been marked as a duplicate of this bug. ***
*** Bug 545790 has been marked as a duplicate of this bug. ***
*** Bug 546609 has been marked as a duplicate of this bug. ***
*** Bug 547986 has been marked as a duplicate of this bug. ***
*** Bug 548486 has been marked as a duplicate of this bug. ***
*** Bug 548981 has been marked as a duplicate of this bug. ***
*** Bug 548988 has been marked as a duplicate of this bug. ***
*** Bug 549403 has been marked as a duplicate of this bug. ***
*** Bug 554816 has been marked as a duplicate of this bug. ***