Bug 1039689

Summary:	evolution stop working silently
Product:	Red Hat Enterprise Linux 6	Reporter:	Aleš Mareček <amarecek>
Component:	evolution	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED DUPLICATE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.5	CC:	amarecek, fidencio, mcrha, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-25 14:48:24 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:
Embargoed:

Description Aleš Mareček 2013-12-09 19:13:07 UTC

Description of problem:
After some period of time Evolution stop working silently without letting you know something has happened. I can recognize it like I have no new e-mail and "proceed bars" are working without stop and any other activity.
The worst problem is when it just "crashes" like this it won't notify me my e-mail(s) haven't been sent and it looks like they have. At this time I use "kill -9" and after next start all e-mails are in "recover" mode so I can see they haven't been sent.

Version-Release number of selected component (if applicable):
evolution-2.32.3-30.el6

How reproducible:
From time to time :(

Steps to Reproduce:
1. run Evolution for some period of time (I would say a week)
2. When receiving mail seems to be odd and it still do "something" without any result, it crashed probably.


Actual results:
Some kind of freeze when user live with pink glasses that everything is ok.

Expected results:
Stable client + some notification.

Additional info:
I tried to use strace and other tools but I haven't collect useful data.

Comment 1 Milan Crha 2014-01-13 14:57:37 UTC

Thanks for a bug report. Do you really have it running for a week (or more) in a row? If I may guess, I'd say evolution got out of memory, due to some memory leak, which might be repeated many times, causing a huge memory leak. But that's only a guess.

Could you, please, install debuginfo packages for evolution-data-server and evolution (make sure their version will be the same as the one for binary packages), and then run evolution from a terminal like this:

$ evolution &>log.txt

and just use evolution for the long time? When it gets to the wrong state, open another terminal and get backtrace of running evolution. You can do that with a command like this:

$ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt

Then get the process status, with this command:
$ cat /proc/`pidof evolution`/status &>status.txt

And then close the evolution. When it closes, upload here the three files, for investigation (can be as a single zip or similar compressed file, as I guess it'll be quite long after a week of usage). Please note that the files (especially the bt.txt) can contain private information, like your passwords, email addresses and so on. I usually search for "pass" (quotes for clarity only), to check for possible password occurrences.

Could you provide some configuration details, please? I'm interested at least in a list of used Mail account types (you can see that in Edit->Preferences->Mail Accounts, the Type column in the list) and types of the Calendars/Address Books/Memos/Tasks, if you use these parts of evolution too.

Comment 2 Aleš Mareček 2014-01-13 15:21:14 UTC

Hi, Milan,
thanks for you suggestions, I'll do that.
To specify my use of Evolution: it's only 1 (RH) account (imap), all shipped plugins enabled - default configuration. I also use PGP/GPG signatures. I don't use it as calendar, address book, etc.

Comment 5 Milan Crha 2014-02-25 14:48:24 UTC

It turned out that this is the same as bug #1040178, thus I mark this as a duplicate of it. I'll provide a rebuilt test package for you shortly.

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