Prior to my upgrade from Kubuntu 13.10 to 14.04, this was not a problem. After the upgrade, all categories disappeared. This part of it wasn't a huge problem since I simply went into Settings ==> Manage Categories and created the categories that I use. I then went into Settings ==> Configure KOrganizer ==> Colors and Fonts and assigned colors to all my categories. For example, Skype = blue, Meeting = Red, Pencil-in = gray This is a good way to use KOrganizer because my schedule is then color coded. However, whenever, I exit KOrganizer and boot back into it, my colors assigned to categories have disappeared and I have do do them over again. Reproducible: Always Steps to Reproduce: 1. Use: Settings ==> Manage Categories to create categories like "Skype," "Meeting" "Pencil-in", etc. 2. Use: Settings ==> Configure KOrganizer ==> Colors and Fonts to assign different colors to each of your categories. 3. Create some appointments and assign them different categories. They will come up in different colors, based on what you've assigned. 4. Exit KOrganizer 5. Restart KOrganizer. You'll find that the color scheme you set up is gone and you have to reset them. Actual Results: When you exit KOrganizer and restart it, the assigned colors go away. Expected Results: KOrganizer should have kept the color scheme that you set up. This bug appeared immediately after the upgrade from Kubuntu 13.10 to 14.04. Prior to that the color scheme stayed in tact and there were some preinstalled categories that are no longer there.
KOrganizer 4.13.2, Arch Linux: The color definititions seem to be present in ~/.kde4/share/config/korganizerrc even after restart. But in KOrganizer all categories are colored in default color green. ===== [Category Colors2] Privat=151,235,121 Projekte=192,0,192
I have a similar problem with two installations of Linux Mint 17 Cinnamon 64-bit and Cinnamon 2.2.13 on two different machines. The finished installation uses the calendar file from the previous Mint 16 installation and KOrganizer 3.11.x The first machine is a Toshiba Laptop with Intel Core 2 Duo CPU, 3.7 GB of RAM using an Intel graphics controller. The second machine machine is an HP desktop with a AMD Athlon IIX4 630 Processor x 4, 15.4 GB of RAM and NVIDEA graphics card. Did a clean install of Mint 17 on July 30, 2014 Then installed KOrganizer 4.13.2 First, before adding any previously used calendar file, I used Settings:Manage Categories to establish the calendar categories I normally use. The dialog box, now named "Manage Tags - KOrganizer", contained no entries. When entries were added in alphabetical order, the categories or tags are then listed in reverse order in the Settings:Configure KOrganizer:Colors and Fonts settings box and also in the New Entry dialog box. The apparent workaround is to initially enter the new Tags in reverse order so that most used categories are at the top of the list. I actually like the use of check boxes for the tags which will lessen the accidental entry of incorrect tags found in previous editions. Second, category or tag colors designated using the Colors and Fonts settings box only work while KOrganizer remains open. As soon as KOrganizer is closed and reopened, the designated colors are lost. Category Colors2 section of .kde/share/config/korganizerrc contains the both the categories and colors: [Category Colors2] BRCalendar=191,217,255 BirthdayCalendar=255,255,0 ChurchCalendar=223,191,255 Education/RVSrs=222,188,133 HolidayCalendar=255,221,0 HouseRepair=221,221,221 KatyCalendar=249,202,222 Rotary=128,179,255 SpecialEvent=255,221,0 TravelCalendar=128,255,128 The problem apparently reported in several distributions: Arch Linux, Kubuntu, Linux Mint, and Xubuntu https://bugs.kde.org/show_bug.cgi?id=335559 https://bugs.kde.org/show_bug.cgi?id=334793 https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1311152 Are there any workarounds, for example, manually editing a different configuration file, that would help? KOrganizer is a startup program on my computers and one of the first thing I see in the office every morning. Any help appreciated.
*** This bug has been marked as a duplicate of bug 333754 ***