Bug 975394

Summary:	"Can not connect to destination" on webcal calendar produces a pop-up instead of status-bar warning
Product:	Red Hat Enterprise Linux 6	Reporter:	David Jaša <djasa>
Component:	evolution	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.5	CC:	jkoten, lnovich, mcrha, tpelka
Target Milestone:	beta
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	evolution-2.32.3-8.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-21 04:53:13 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 David Jaša 2013-06-18 11:15:40 UTC

Description of problem:
"Can not connect to destination" on webcal calendar produces a pop-up instead of status-bar warning.

Pop-ups are bad because they block response of parent window. If the condition is deemed important enough to bug the users with notification, standard libnotify-based nofitication should be used

Version-Release number of selected component (if applicable):
evolution-2.32.3-5.el6.x86_64
evolution-data-server-2.32.3-5.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. have a webcal calendar where evolution "Cannot connect to destination"
2. open evo Calendar window
3. wait

Actual results:
evolution produces pop ups saying:
"""
Error in webcal://example.com/path/file.ics
Can not connect to destination
"""

Expected results:
The error is reported just in status bar, as it is alredy reported for imap email accounts

Additional info:

Comment 1 Milan Crha 2013-06-19 13:29:16 UTC

Current upstream code has this done differently, but that's no problem.

Comment 8 errata-xmlrpc 2013-11-21 04:53:13 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/RHSA-2013-1540.html