Bug 451508 - unhelpful error warnings
unhelpful error warnings
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
9
All Linux
low Severity low
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-14 23:47 EDT by Tim
Modified: 2008-07-10 08:20 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-10 08:20:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Desktop 542361 None None None Never

  None (edit)
Description Tim 2008-06-14 23:47:33 EDT
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 08:20:18 EDT
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.