After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 494392 - no indication about failed calendars
no indication about failed calendars
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.12.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks: 502515
 
 
Reported: 2007-11-07 00:31 UTC by Sam Morris
Modified: 2012-12-03 16:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Sam Morris 2007-11-07 00:31:55 UTC 
Please describe the problem:
The user has no way to know that a calendar on their list of calendars has failed. For instance, a calendar that 404s still shows up in the list and the user is able to toggle its visibility, but they can never work out why there are no events displayed, or find out what the error is.

Steps to reproduce:



Actual results:


Expected results:
Failed calendars could have their 'visible' checkbox disabled and have an error icon displayed in their row in the calendar list; the icon could display a tooltip containing the actual error message.

Does this happen every time?


Other information:
Comment 1 André Klapper 2007-11-07 10:41:44 UTC 
i wonder if we have a system to forward an error message (like a 404) to the user frontend?
gicmo, any idea?
Comment 2 Milan Crha 2012-12-03 16:30:24 UTC 
I consider this obsolete these days. The errors from calendars are propagated to UI, and shown to a user. The only thing was that there was no identification of the calendar, which I changed just recently for 3.7.3 at [1]. I'm closing this as such.

Please note that different calendar backends can deal with such errors differently. For example, CalDAV, if you was ever able to connect to it, behave like the server is temporarily unavailable, and will show you its previous content, if any. Of course, the 404 is special, but again, it's for calendars where you were able to connect to at least once. The CalDAV will claim the error to a user too, to let him/her know about that.

[1] http://git.gnome.org/browse/evolution/commit/?id=4c699e7e03975639