Bug 888657

Summary:

Evolution stop receiving messages and stuck

Product:

[Fedora] Fedora

Reporter:

Mikhail <mikhail.v.gavrilov>

Component:

evolution

Assignee:

Matthew Barnes <mbarnes>

Status:

CLOSED DUPLICATE

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

CC:

lucilanga, mbarnes, mcrha

Target Milestone:

---

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2013-01-07 10:40:31 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:

Attachments:

Description	Flags
evolution backtrace	none
evolution-addressbook-factory backtrace	none
evolution-calendar-factory backtrace	none
evolution-source-registry backtrace	none
evolution-alarm-notify backtrace	none
evolution backtrace	none
evolution-addressbook-factory backtrace	none
evolution-calendar-factory backtrace	none
evolution-source-registry backtrace	none
evolution-alarm-notify backtrace	none

Description Mikhail 2012-12-19 06:45:47 UTC

Description of problem:
Evolution stop receiving messages and stuck

Demonstration video: https://docs.google.com/open?id=0B0nwzlfiB4aQQ2FJMDBsTG9TRms

Comment 1 Mikhail 2012-12-19 06:53:38 UTC

Created attachment 665933 [details]
evolution backtrace

Comment 2 Mikhail 2012-12-19 06:54:15 UTC

Created attachment 665939 [details]
evolution-addressbook-factory backtrace

Comment 3 Mikhail 2012-12-19 06:55:06 UTC

Created attachment 665940 [details]
evolution-calendar-factory backtrace

Comment 4 Mikhail 2012-12-19 06:55:44 UTC

Created attachment 665941 [details]
evolution-source-registry backtrace

Comment 5 Mikhail 2012-12-19 06:57:01 UTC

Created attachment 665942 [details]
evolution-alarm-notify backtrace

Comment 6 Mikhail 2012-12-19 08:53:02 UTC

Stuck later again, new video: https://docs.google.com/open?id=0B0nwzlfiB4aQQU5PXzFNbUxBX1U

Comment 7 Mikhail 2012-12-19 08:57:32 UTC

Created attachment 665966 [details]
evolution backtrace

Comment 8 Mikhail 2012-12-19 08:58:54 UTC

Created attachment 665967 [details]
evolution-addressbook-factory backtrace

Comment 9 Mikhail 2012-12-19 09:11:07 UTC

Created attachment 665982 [details]
evolution-calendar-factory backtrace

Comment 10 Mikhail 2012-12-19 09:11:56 UTC

Created attachment 665983 [details]
evolution-source-registry backtrace

Comment 11 Mikhail 2012-12-19 09:13:56 UTC

Created attachment 665984 [details]
evolution-alarm-notify backtrace

Comment 12 Milan Crha 2013-01-07 10:40:07 UTC

Thanks for a bug report. I see the same cause as is in your bug #888172, thus I'm marking this as a duplicate of it. A basic rule on Evolution's quit is that the quit will not happen while there are pending activities in the status bar, or any other pending operations (some are not shown in status bar).

P.S.:
Feel free to create a script like this:
   #!/bin/bash

   FILENAME=/tmp/`date +%Y%m%d-%H%M%S`-$1-bt.txt

   gdb --batch --ex "t a a bt" -pid=`pidof $1` &>$FILENAME

to which you pass one argument only, a process name, and it'll create backtrace of it in /tmp with a date and process name as well. It can be enhanced to get backtraces of all known evolution processes (involving awk or such tool from the `ps ax | grep evolution` command, or just by name them all) like this:
   #!/bin/bash

   FILENAME_PREFIX=/tmp/bt-`date +%Y%m%d-%H%M%S`
   PROCESSES="evolution evolution-addressbook-factory evolution-calendar-factory evolution-source-registry evolution-alarm-notify evolution-user-prompter"

   for PROC in $PROCESSES; do
   {
	if [ "`pidof $PROC`" != "" ] ; then
		FILENAME=$FILENAME_PREFIX-$PROC.txt
		gdb --batch --ex "t a a bt" -pid=`pidof $PROC` &>$FILENAME
	fi
   };
   done

Comment 13 Milan Crha 2013-01-07 10:40:31 UTC


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