I had this problem also with the old KDE 4.3.5 and it is not gone after upgrading to 4.4.4: digital clock shows no "holidays region" entries in the Calendar tab. However, the calendar option in kontact does. I can correctly choose my region and the holidays appear on kontact's calendar. The problem is still there even after fully wiping out the contents of /var/tmp/kdecache-mysuer and starting with a fresh ~/.kde4 folder Manually setting "holidaysRegion=es" in "~/.kde4/share/config/plasma-desktop-appletsrc" makes no difference. I see "Do not show holidays" in Digital Clock's calendar tab. Reproducible: Always
If I understand correctly, we should have in the system plasma-dataengine-calendar.desktop But I do not have this. May be because in ./configure of plasma-workspace -DWITH_KdepimLibs=OFF ? (KDE PIM libraries Needed for building several plasma dataengines) P.S. kdepimlibs installed on my system. P.P.S. How to change -DWITH_KdepimLibs ? P.P.P.S. Sorry for my English ;)
I was right, I deleted plasma-dataengine-calendar.desktop in Arch Linux and reproduce this bug. But I am not programmer, I do not know how to fix it :(
try to enable rss useflag on plasma-workspace
Strange, but it works :) It may be necessary to add a use flag for the holidays? Rss is quite another.
(In reply to comment #3) > try to enable rss useflag on plasma-workspace > I can confirm enabling the "rss" USE flag solves the problem. But I still can't understand what the hell has the "rss" USE flag to do with holidays region in digital clock's calendar, and why they appear in kontact's calendar instead without the cited USE flag.
Shouldn't be 'rss' USE-flag renamed to 'pim' or something similar? Just because it enables all plasma integration with PIM (not only rss. As we can see, calendar and holidays too, maybe something else). Just a quote from ebuild: mycmakeargs=( ... $(cmake-utils_use_with rss KdepimLibs) ... ) When rss USE-flag is enabled, plasma compiles with all KDEPIM support. Name 'rss' for this flag really confuses users (as example you can see this bug :) ).