Hide Forgot
Created attachment 812622 [details] yum update done this morning, when issue started Description of problem: I cannot create a new email message or reply to an existing one Version-Release number of selected component (if applicable): 3.8.5-2 How reproducible: Every time. Steps to Reproduce: 1.Start Evolution 2.Click on "New" to create a new mail (or Reply or Forward from an existing email) 3.Evolution crashes Actual results: Evolution crashes Expected results: Evolution should open a new window so I can write an email Additional info: I tried to downgrade to 3.8.3 but the same thing happens, however it is only happening since I upgraded the following packages with yum this morning (see attachments)
Created attachment 812624 [details] abrt data
After several verifications, it appears that this crash only happens when my external encrypted hard disk (left encrypted, or after entering the key) is connected to the computer. When I disconnect it, Evolution can open the New Message window and I can work properly without any issue. So I would say that it is reproductable when I plug-in my external hard disk, which is encrypted. So I am not sure if is only happening with Evolution, apparently it is also happening with gedit when I want to "Save As ..." or save if it needs to open the Save As window. There seems to be an error with some library, not with Evolution itself. However I can reproduce it whenever I want, as I know exactly what to do, so please let me know if you need additional information.
Thanks for a bug report. The abrt raw data are kind of useless, the best is to provide a backtrace (or basically let abrt fill the bug). As you describe it, I'd say it's a bug in gtk3 itself, thus I move it there. If you can provide the backtrace too, then it'll help. You can get the bakctrace even without abrt, enough to install debuginfo packages for gtk3 and run evolution under gdb, then reproduce the crash, get the backtrace and quit gdb (one command for this looks like): $ gdb evolution --ex r --ex "t a a bt" --ex q and get basically everything what gdb will print just before the crash.
Hello, I guess you can close this bug as with the latest updates, this is not a problem any more. Thank you for your help