abrt 1.0.3 detected a crash.
Comment: This is likely a fluke, or at least a hard-to-reproduce problem. Evolution seg faulted when I clicked the 'New Email' button from the taskbar. This was the first email I attempted to compose after waking the computer up from hiberation this morning. Maybe the debuginfo might provide some useful info.
Attached file: backtrace
reason: Process was terminated by signal 11
Created attachment 382366 [details]
Thanks for a bug report. It's trying to create a new composer window bug fails somewhere "in the middle". Evolution used to be very bad with respect of hibernation, but usually with lost network connections and such, and this bug is somewhere in gtk, with newly allocated memory, thus it seems to me like a coincidence, than a necessary step to resume from hibernation. The most i can see in the backtrace is that you were creating a new message in your IMAP Inbox folder. Are you able to reproduce this even without hibernation, and what is your gtk2 version, please?
*** Bug 553660 has been marked as a duplicate of this bug. ***
I am not able to reproduce it sans hibernation and moreover I'm no longer able to reproduce it after getting a yum gtk update.
During when the problem was occurring consistently I was at gtk2-2.18.5-4.fc12.i686. It looks like I updated to gtk2-2.18.6-3.fc12.i686 on Jan 29th and the problem seems to have gone away.
I spoke too soon - I had another crash with the "wake up from hibernate, try to compose a message" scenario this morning. I've still been unable to reproduce this without the hibernate.
Would you like for me to upload the latest crash (and if so, do you mind if I just use the automated abrt method instead of trying to figure out how to attach it to this bug)?
I guess not(In reply to comment #5)
> Would you like for me to upload the latest crash (and if so, do you mind if I
> just use the automated abrt method instead of trying to figure out how to
> attach it to this bug)?
I guess not, the above is good. As a workaround, try to close Evolution before you suspend your machine.
*** Bug 575405 has been marked as a duplicate of this bug. ***
*** Bug 585929 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. 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 '12'.
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 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.
Thank you for reporting this bug and we are sorry it could not be fixed.