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 688620 - "No output stream" (bug summary intentionally left vague...)
"No output stream" (bug summary intentionally left vague...)
Status: RESOLVED DUPLICATE of bug 573240
Product: evolution
Classification: Applications
Component: Mailer
3.6.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-11-19 08:47 UTC by Guy Lunardi
Modified: 2013-06-20 14:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of the No Output Stream message (361.84 KB, image/png)
2012-11-19 21:21 UTC, Guy Lunardi
Details

Description Guy Lunardi 2012-11-19 08:47:02 UTC
While the new information messages in Evolution are very nice (well done),
some of the content is less than useful for the average user.

One of them is "Error while Retrieving list of folders at '<email/>'
with the subline "No output stream".

The bold text is really quite hard to decypher I am certain for a normal but the addition of "No output stream" makes certain that if they weren't sure they were confused... they are now.

Maybe it could be replaced with an easier to understand email. This seems to be likely caused by an internal error (camel store or else).

A sub-line along the lines of "Please try again to Retrieve your messages".

If it is just a one time issue (I only see this message when resuming from suspend), maybe we could let the system retry once before displaying the error message.
Comment 1 Guy Lunardi 2012-11-19 21:21:10 UTC
Created attachment 229408 [details]
Screenshot of the No Output Stream message
Comment 2 Milan Crha 2013-06-20 14:01:53 UTC
Thanks for a bug report. This is related to bug #573240, thus I'm marking this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 573240 ***