Version: 1.3 (using KDE 4.1.0) OS: Linux Installed from: Ubuntu Packages This could be a wishlist item, but I feel it's a bug due to a circumstance which I'm guessing is quite frequent. If you have in KOrganizer a calendar which is the KAddressbook Birthdays and Anniversaries which I'm thinking would be quite normal so you see birthdays on your calendar. And if you have KSummary setup to show upcoming events which is set to show birthdays and anniversaries which I believe is quite normal because that's where you normally want to see them. Then you end up getting these duplicates. It would nice to be able to choose which calendars you want to show in the KSummary windows to remove this unwanted functionality as well as any other calendar events which you might have in KOrganizer but not want to show in KSummary.
Kontact in KDE 4.2 will have an option to not show birthdays and anniversaries in the Upcoming Events summary. Is that enough to close this bug? Or do you still want to configure which calendar resources to show in the summary?
I'm not entirely sure how you'll know it's a birthday or anniversary accept by looking for those words in the keywords. But if you're able to do that I would say that would close this as a "bug". However, I still think it would be a great feature for to be able to choose what calendars display on the summary page. With more and more sites releasing rss feeds of events which can be used as a calendar I might want to display a sports teams games on my calendar without having it crowd my upcomming events summary page which I use to check what's next all day long. So I guess this should be changed to a feature request though.
I just thought about my previous statement and realized that I hope the "Don't show anniversaries or Birthdays" functionality isn't just based on simply finding a keyword like "Birthday" because this might then not show evens such as Birthday party which would still need to be shown.
The remaining parts of this wish report are already reported in bug 105728. Merging. *** This bug has been marked as a duplicate of bug 105728 ***