Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 451508 - unhelpful error warnings
Summary: unhelpful error warnings
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-15 03:47 UTC by Tim
Modified: 2008-07-10 12:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-10 12:20:18 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
GNOME Bugzilla 542361 None None None Never

Description Tim 2008-06-15 03:47:33 UTC
Description of problem:
When fetching mail, you might get a warning about being unable to refresh a
folder, but it doesn't say which folder.  Opening the debug logs from the help
menu doesn't help (they remain totally blank).  When dealing with mail from
multiple servers, and with multiple folders, this lack of information makes it
hard to manage.

Version-Release number of selected component (if applicable):
evolution-2.22.2-2.fc9.i386

How reproducible:
Any time there's a problem fetching mail (e.g. network was down when you tried
to fetch mail, mail server was extremely busy, etc.).

Steps to Reproduce:
1. Try to get mail when there's some sort of server/network problem.
2. See a useless error warning "Error while Refreshing folder".
3.
  
Actual results:


Expected results:
To be told, somewhere, WHICH specific thing that it couldn't do (e.g. the folder
name, and/or which mail server).

Additional info:

Comment 1 Matthew Barnes 2008-07-10 12:20:18 UTC
Definitely agree, but this would best be handled upstream.  Please see [1] for
further updates.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=542361


Note You need to log in before you can comment on or make changes to this bug.