Bug 1139166

Summary: Limit number of notification retries
Product: Red Hat Enterprise Linux 6 Reporter: Jiri Koten <jkoten>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: medium    
Version: 6.6CC: fidencio, mcrha, tlavigne, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: evolution-2.32.3-34.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-14 04:41:25 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
notification-daemon backtrace none

Description Jiri Koten 2014-09-08 09:22:59 UTC 
Description of problem:
Currently when evolution don't receive reply on notification send, it tries to resend it indefinitely. This is causing a freeze of evolution and all gtk applications on my system. It lasts couple of minutes and even though I'm unable to reproduce on purpose, I experience it almost every day.   

Version-Release number of selected component (if applicable):
evolution-2.32.3-33.el6
evolution-data-server-2.32.3-21.el6
notification-daemon-0.5.0-1.el6
gtk2-2.24.23-6.el6
glib2-2.28.8-2.el6
at-spi-1.28.1-2.el6
Comment 1 Jiri Koten 2014-09-08 09:26:59 UTC 
Created attachment 935281 [details]
evolution backtrace

Backtrace of evolution during freeze.
Comment 2 Jiri Koten 2014-09-08 09:28:51 UTC 
Created attachment 935282 [details]
notification-daemon backtrace

Notification-daemon backtrace during freeze
Comment 3 Milan Crha 2014-09-08 12:34:31 UTC 
Devel-acking, easy fix
Comment 6 errata-xmlrpc 2014-10-14 04:41:25 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1416.html