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 460441 - When in search for unread mail, message window for any mail item displays as blank
When in search for unread mail, message window for any mail item displays as ...
Status: RESOLVED DUPLICATE of bug 467892
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-26 03:25 UTC by Andrew J. Montalenti
Modified: 2008-01-09 02:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
example of a "blank" message window (17.38 KB, image/png)
2007-07-26 03:26 UTC, Andrew J. Montalenti
Details

Description Andrew J. Montalenti 2007-07-26 03:25:47 UTC
Please describe the problem:
I have a search folder for all unread mail on a certain set of folders.  If I try to read this mail one by one, the message preview pane works fine.  But if I double-click any mail item (or press "Enter" while selected on any item), the message window will appear, but will be blank.

If I simply clear the search filter (Shift+Ctrl+Q), and then double-click the item, it will open properly.

Steps to reproduce:
1. Search for unread mail. 
2. Double-click any item (or press "Enter" on any item)
3. Notice blank window


Actual results:
Blank window

Expected results:
Window with message contents

Does this happen every time?
Yes

Other information:
Comment 1 Andrew J. Montalenti 2007-07-26 03:26:16 UTC
Created attachment 92431 [details]
example of a "blank" message window
Comment 2 Basilio Kublik 2008-01-09 02:42:03 UTC
this issue has also reported at https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/181387
Comment 3 Basilio Kublik 2008-01-09 02:54:57 UTC
i'm linking this report to bug #467892 since that one is more widely discussed, and about the exact same issue.

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