Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#2 g_malloc0 at gmem.c:189
#3 g_malloc0_n at gmem.c:424
#4 g_hash_table_new_full at ghash.c:667
#5 g_hash_table_new at ghash.c:623
#6 camel_mime_message_init at camel-mime-message.c:379
#7 g_type_create_instance at gtype.c:1917
#8 g_object_constructor at gobject.c:1855
#11 camel_mime_message_new at camel-mime-message.c:408
#12 imapx_get_message_sync at camel-imapx-folder.c:631
#13 camel_folder_get_message_sync at camel-folder.c:3765
Potential duplicate: bug 879098
Created attachment 770989 [details]
Created attachment 770990 [details]
Created attachment 770991 [details]
Created attachment 770992 [details]
Created attachment 770993 [details]
Created attachment 770994 [details]
Created attachment 770995 [details]
Created attachment 770996 [details]
Created attachment 770997 [details]
Created attachment 770998 [details]
Created attachment 770999 [details]
Thanks for a bug report. Abrt found a similar bug, from Fedora 17, at bug #879098, but it's currently in a need-info state. I'll use the same question:
Do you know any way how to reproduce this, please? Or it was just a one-time crash, and you do not see it anymore? I cannot tell from the backtrace much, it might be some memory corruption, most likely, when a message was read from a your IMAP+ account, but I do not see anything more.
I can't give you much information. I was reading some mail (gmail via IMAP), clicked on another and then it crashed.
I'm not sure it'll help you a lot.
Since yesterday, it didn't crash again.
OK, that's no problem, Reproduce a memory corruption bug is quite tricky - using the same steps can sometimes crash the application, and sometimes not, on exactly the same code. I'll mark the other bug as a duplicate of this one, to let the issue live for few more releases.
*** Bug 879098 has been marked as a duplicate of this bug. ***
I had this crash this morning. I was tethering to my phones wifi when we went through a tunnel so my phone lost its signal. I hit 'reply to group' and it said retrieving email 956565 (or something like that) then I hit 'reply' as I didn't want to reply to all and it said he same thing about retrieving then it crashed.
Hope this helps.
I had the same problem few minutes ago, abrt reported it. I was on gmail with imap. The only thing I noticed was the the network was very slow, I was pull some git repositories at the same moment.
I hope this helps a little bit.
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.