Red Hat Bugzilla – Bug 220714
Clicking ok or cancel on a bad pops server will crash
Last modified: 2007-12-11 10:39:27 EST
Description of problem:
If you connect to a server (such as I do) that uses a self signed cert, the
dialog asking if it is ok (cancel/ok as answers) now always comes up.
Additionally, clicking either answer not nearlya lways causes a crash. It will
ALWAYS crash if the send/receive email dialog is up.
Version-Release number of selected component (if applicable):
Nearly every time.
Steps to Reproduce:
1. Set up a pops server with self signed cert
2. Send/receive email
3. Click ok or cancel on the dialog
Trace back attached.
Created attachment 144337 [details]
Created attachment 146207 [details]
Newer trace back / Shouldn't have any unknown symbol tables
Clicking ok seems fixed. Though this may have been just from me having the admin
regenerate the cert as it was expired. (Clicking cancel is what I did to create
the above trace back.)
Created attachment 146209 [details]
Trace back for clicking ok instead of cancel
146207 is for clicking cancel, this is for clicking ok.
Confirmed, I'm able to reproduce this. I don't think it's directly related to
certificates, but that certificate dialog does send it down a code path that
triggers the problem. Looks like memory corruption to me. Investigating.
*** Bug 228524 has been marked as a duplicate of this bug. ***
I think I may have found the problem. It looks like an error in some threading
logic I rewrote awhile back. An upstream bug  has all the gory details about
the source of the problem and the solution.
Please give evolution-2.9.91-3.fc7 a try. It should appear in Rawhide tomorrow.
At the moment this appears it may be fixed. However, I have occasionally had
success before so, give me another day or so to make sure.
I have only been able to get one crash. It seems unrelated (NEtworkManager
wouldn't setup the network and leave it, so I removed it again, having just
installed it) so I am closing the bug.
*** Bug 214307 has been marked as a duplicate of this bug. ***
*** Bug 231025 has been marked as a duplicate of this bug. ***