Description of problem: tried launching Geary, I have four accounts configured, one being yahoo mail which I recently changed the password and haven't updated the config so Geary popped up a dialog asking for the password which I canceled, it opened the main window and popped up a second dialog which I also canceled and then it crashed. Whether this was related to the yahoo account or one of the others I cannot say. I had this happen twice then I just updated the yahoo password and it opened and is working normally now. Version-Release number of selected component: geary-0.4.2-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: geary crash_function: geary_smtp_outbox_folder_add_to_containing_folders_async_co executable: /usr/bin/geary kernel: 3.13.4-200.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 geary_smtp_outbox_folder_add_to_containing_folders_async_co at /usr/src/debug/geary-0.4.2/src/engine/imap-db/outbox/smtp-outbox-folder.vala:110 #1 geary_smtp_outbox_folder_add_to_containing_folders_async at /usr/src/debug/geary-0.4.2/src/engine/imap-db/outbox/smtp-outbox-folder.vala:14 #2 geary_imap_db_account_get_containing_folders_async_co at /usr/src/debug/geary-0.4.2/src/engine/imap-db/imap-db-account.vala:941 #3 g_simple_async_result_complete at gsimpleasyncresult.c:777 #4 geary_db_database_exec_transaction_async_co at /usr/src/debug/geary-0.4.2/src/engine/db/db-database.vala:272 #5 g_simple_async_result_complete at gsimpleasyncresult.c:777 #6 geary_db_transaction_async_job_wait_for_completion_async_co at /usr/src/debug/geary-0.4.2/src/engine/db/db-transaction-async-job.vala:95 #7 g_simple_async_result_complete at gsimpleasyncresult.c:777 #8 geary_nonblocking_abstract_semaphore_real_wait_async_co at /usr/src/debug/geary-0.4.2/src/engine/nonblocking/nonblocking-abstract-semaphore.vala:135 #9 geary_scheduler_scheduled_instance_on_callback at /usr/src/debug/geary-0.4.2/src/engine/util/util-scheduler.vala:66
Created attachment 869508 [details] File: backtrace
Created attachment 869509 [details] File: cgroup
Created attachment 869510 [details] File: core_backtrace
Created attachment 869511 [details] File: dso_list
Created attachment 869512 [details] File: environ
Created attachment 869513 [details] File: exploitable
Created attachment 869514 [details] File: limits
Created attachment 869515 [details] File: maps
Created attachment 869516 [details] File: open_fds
Created attachment 869517 [details] File: proc_pid_status
Created attachment 869518 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.