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 402529 - no memos in the Calendar window
no memos in the Calendar window
Status: RESOLVED DUPLICATE of bug 359267
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-01-30 18:23 UTC by Andy
Modified: 2008-02-15 14:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Andy 2007-01-30 18:23:52 UTC 
What were you doing when the application crashed?
Evolution 2.8.1
I can not see my memos when I am in the Calendar window. I can see a widget to display my memos list underneath my todo list, but I can not see any of my memos.

If I go to the memo window itself, I can see my memos just fine.

If you have any questions, feel free to contact me.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0
Comment 1 André Klapper 2007-02-09 00:49:58 UTC 
here it is the other way round. :-)
Comment 2 Milan Crha 2007-09-05 11:17:42 UTC 
The view there is only for those memos which are in a selected time range (time range on the left bottom small calendar), at the moment. All others are hidden. Even it is now possible to create memos with no start date, then these are not shown there. I would like to suggest to improve it in a way that there will be shown those without start date always, others will "gone" if they don't "fit" into time range. Does it make sense?
Comment 3 Juha Siltala 2008-02-15 13:14:40 UTC 
Milan,

That would be my suggestion exactly. No start date -> always show.
Comment 4 Milan Crha 2008-02-15 14:11:02 UTC 
Thanks for you reply, this has been fixed in bug #359267, and is included in 2.12.3, even the real fix is in 2.21.9x development version (see bug #501474).
I'm marking this as a duplicate of the former bug.

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