Version-Release number of selected component: evolution-3.6.2-3.fc18 Additional info: backtrace_rating: 4 cmdline: evolution crash_function: field_set_to_none executable: /usr/bin/evolution kernel: 3.7.2-204.fc18.x86_64 remote_result: 746144 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 field_set_to_none at e-dateedit.c:1707 #1 e_date_edit_check_date_changed at e-dateedit.c:2141 #2 e_date_edit_get_date at e-dateedit.c:883 #3 task_details_page_fill_component at task-details-page.c:362 #4 comp_editor_get_current_comp at comp-editor.c:3485 #5 save_and_close_editor at comp-editor.c:1000 #10 _gtk_action_emit_activate at gtkaction.c:801 #11 gtk_action_activate at gtkaction.c:832 #12 button_clicked at gtktoolbutton.c:877 #13 _g_closure_invoke_va at gclosure.c:840 Potential duplicate: bug 746144
Created attachment 685302 [details] File: backtrace
Created attachment 685303 [details] File: cgroup
Created attachment 685304 [details] File: core_backtrace
Created attachment 685305 [details] File: dso_list
Created attachment 685306 [details] File: environ
Created attachment 685307 [details] File: limits
Created attachment 685308 [details] File: maps
Created attachment 685309 [details] File: open_fds
Created attachment 685311 [details] File: proc_pid_status
Created attachment 685313 [details] File: smolt_data
Created attachment 685314 [details] File: var_log_messages
Thanks for a bug report. I see a similar bug had been reported in time of evolution 3.2.x, and the associated upstream bug report is still opened, thus we can move there, but I would like to ask for more details first: I see from the backtrace that you were finishing addition or modification of a task, but I do not see from the backtrace what could break. Do you have any steps for this, please? Especially what values were set in task's date edits, the start date and due date.
I tried to replicate it using the same steps but nothing occurred. I created the task naming it "Call Andre" then opened it to edit the due date. I changed the start and end date to the same date; in this case Jan 22. Then hit the save and close task editor. Thats when the crash occurred. Let me know if you need more info. Thanks.
Thanks for the update. I'm wondering whether it was caused by a hand-written date, in some form which the date widget doesn't understand, and thus tries to change it to "None" - that's what the backtrace suggests. I tried some combinations here, but whenever I move out of the date entry it either claims that the date is not valid (and changes it to current day) or lefts it as is.
I just logged in my Gnome 3 session. backtrace_rating: 4 Package: evolution-3.6.3-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.