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 548035 - Evolution Mail and Calendar: Using Evolution Calendar...
Evolution Mail and Calendar: Using Evolution Calendar...
Status: RESOLVED DUPLICATE of bug 592117
Product: evolution
Classification: Applications
Component: Calendar
2.22.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-08-16 16:40 UTC by thadm
Modified: 2010-03-31 07:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description thadm 2008-08-16 16:40:05 UTC
Using Evolution Calendar feature in Month mode is unusable when the calendar is very full with a lot of appointments.  The print preview and print out have characters and graphics overlapping such that information becomes illegible.  I also notice a real problem with the days of the week and numbers merging in the tiny stamp size month window shown in both the month selector and the header of the print out.  I believe this has already been reported in the Evolution Users Forum.
This Evolution calendar problem is a bummer as I was switching my household from Microsoft Vista to Ubuntu Linux but with my wife making heavy use of calendar for planning, syncing with her Palm TX as well as printing month calendars for the household, she is unable and unwilling to move to Linux until this is fixed.  BUMMER!!!  :-(


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.3 2008-07-09 (Ubuntu)
BugBuddy Version: 2.22.0
Comment 1 André Klapper 2008-08-16 22:42:43 UTC
What about using the List view?
Comment 2 Akhil Laddha 2010-03-31 07:32:22 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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