Bug 1322757

Summary: Evolution sometimes dies when trying to expand recipients list on incoming mail
Product: [Fedora] Fedora Reporter: Artur Flinta <aflinta>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 23CC: lucilanga, mbarnes, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-01 08:21:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
gdb output none

Description Artur Flinta 2016-03-31 09:28:29 UTC 
Description of problem:
For few days I'm facing problem with expanding recipients list of incoming mail (exchange server). Clicking on plus sing next to sender name causing sometimes evolution crashing. 
Unfortunately ABRT is unable to report this cause of possible leaking of sensitive information.

Version-Release number of selected component (if applicable):
evolution-3.18.5.2.1.fc23.x86_64

How reproducible:
Sometimes, depend of evolution session, but in mine case is about 50% chance to encounter this problem after evolution restart.

Steps to Reproduce:
1. Receive mail sent to at least three persons. 
2. In evolution main window on message preview try to expand recipients list clicking on plus sign. 

Actual results:
Sometimes evolution crashes.

Expected results:
Expand recipients list.

Additional info:
I'm open to help tracing this problem ;)
Comment 1 Milan Crha 2016-03-31 16:14:55 UTC 
Thanks for a bug report. I tried to reproduce this, but no luck here. The backtrace of the crash will give a clue where to look, at least. Could you run the evolution under gdb and get the backtrace? The best if you run the evolution, wait until the initial update is finished, then reproduce the crash. That way the backtrace will contain minimal information. Plase make sure that you've installed debuginfo package for the evolution (not necessary for its dependencies), of the same version as the binary package (rpm -qa | grep evolution).

The gdb command would look like this:
   $ gdb evolution --ex r --ex bt --ex "t a a bt" --ex q

Mark a place in the terminal where is the last output before you'll start reproducing the crash, then copy everything from that point to the end of the output. Please check the output for any private information, like passwords, email address, server addresses,... I usually search for "pass" at least (quotes for clarity only).
Comment 2 Artur Flinta 2016-03-31 19:46:15 UTC 
Created attachment 1142354 [details]
gdb output

gdb output from crash
Comment 3 Milan Crha 2016-04-01 08:21:36 UTC 
Thanks for the backtrace. I see it crashes under the same function as already filled bug #1321722, thus I'm marking this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 1321722 ***