Description of problem:
I launched Evolution and it crashed.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#2 key_reservation_free at camel-object-bag.c:85
#3 object_bag_unreserve at camel-object-bag.c:103
#4 camel_object_bag_add at camel-object-bag.c:447
#5 camel_data_cache_add at camel-data-cache.c:399
#6 imapx_server_get_message at camel-imapx-server.c:7375
#7 camel_imapx_server_sync_message at camel-imapx-server.c:7445
#8 imapx_synchronize_message_sync at camel-imapx-folder.c:1000
#9 camel_folder_synchronize_message_sync at camel-folder.c:4351
#10 offline_folder_downsync_background at camel-offline-folder.c:111
#11 session_do_job_cb at camel-session.c:176
Created attachment 766873 [details]
Created attachment 766875 [details]
Created attachment 766876 [details]
Created attachment 766878 [details]
Created attachment 766879 [details]
Created attachment 766880 [details]
Created attachment 766881 [details]
Created attachment 766882 [details]
Created attachment 766883 [details]
Created attachment 766884 [details]
Thanks for a bug report. I added a note to an upstream bug report , which can be related, because it added changes to this code recently. Does it crash for you each start, now? The only thing I see from the backtrace is that one of your folders is downloading content for offline use.
No, I haven't seen any crash lately. I'll pay a closer attention to the download for offline use matter to see what I can find.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.