Description of problem: Recreate steps: 1. Install geary 2. Run geary an configure new email account 3. Maximize Geary window by double clicking on titlebar Version-Release number of selected component: geary-0.2.2-1.fc18 Additional info: backtrace_rating: 4 cmdline: geary crash_function: geary_imap_fetch_results_get_body_data executable: /usr/bin/geary kernel: 3.7.9-201.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 geary_imap_fetch_results_get_body_data at /usr/src/debug/geary-0.2.2/src/engine/imap/decoders/imap-fetch-results.vala:106 #1 geary_imap_mailbox_list_set_async_co at /usr/src/debug/geary-0.2.2/src/engine/imap/transport/imap-mailbox.vala:267 #2 g_simple_async_result_complete at gsimpleasyncresult.c:775 #3 geary_nonblocking_batch_execute_all_async_co at /usr/src/debug/geary-0.2.2/src/engine/nonblocking/nonblocking-batch.vala:154 #4 g_simple_async_result_complete at gsimpleasyncresult.c:775 #5 geary_nonblocking_abstract_semaphore_real_wait_async_co at /usr/src/debug/geary-0.2.2/src/engine/nonblocking/nonblocking-abstract-semaphore.vala:135 #6 geary_scheduler_scheduled_instance_on_callback at /usr/src/debug/geary-0.2.2/src/engine/util/util-scheduler.vala:66 #7 _geary_scheduler_scheduled_instance_on_callback_gsource_func at /usr/src/debug/geary-0.2.2/src/engine/util/util-scheduler.c:152 #12 gtk_main at gtkmain.c:1160 #13 yorba_application_run at /usr/src/debug/geary-0.2.2/src/common/common-yorba-application.vala:143
Created attachment 701164 [details] File: backtrace
Created attachment 701166 [details] File: build_ids
Created attachment 701168 [details] File: cgroup
Created attachment 701170 [details] File: core_backtrace
Created attachment 701173 [details] File: dso_list
Created attachment 701175 [details] File: environ
Created attachment 701177 [details] File: limits
Created attachment 701178 [details] File: maps
Created attachment 701179 [details] File: open_fds
Created attachment 701180 [details] File: proc_pid_status
Created attachment 701181 [details] File: var_log_messages
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.