Bug 388914 - Assign calendar color dialog does not remember 'custum colors'
Summary: Assign calendar color dialog does not remember 'custum colors'
Status: RESOLVED WORKSFORME
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 5.7.1
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-13 16:29 UTC by Achim Bohnet
Modified: 2022-12-10 05:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Achim Bohnet 2018-01-13 16:29:10 UTC
I see this on 5 kde neon and 2 Kubuntu installations: laptops, desktops and VBox.  This was at least never working in KF5 based korganizer.

Reproduce:
* right click on calendar -> Calendar Color -> Assign Color ...
* click 'Add to custom colors' button 
-> color is added. Good!
* close dialog
* open dialog again
-> saved color still there. Good!
* Close korganizer and start it again
* open 'Assign Color' dialog again
-> saved color is _NOT shown anymore.  Bug!

Not being able to save a set of colors makes bug

 https://bugs.kde.org/show_bug.cgi?id=328862
 https://bugs.kde.org/show_bug.cgi?id=273978

even more anoying, as I have to reassign all (ten) calendar colors again
from time to time (Bug 273978).
Comment 1 Allen Winter 2018-01-13 17:18:20 UTC
I tested setting a calendar color to 110/110/110,
add that value as a custom color, and making sure to select that custom color.

I see that this value is stored in ~/.config/eventviewsrc
I see that this value is used when I restart Kontact

so far so good.

can try looking in ~/.config/eventviewsrc and making sure the custom color is save there?
Comment 2 Achim Bohnet 2018-01-17 18:36:54 UTC
Hi Allen,
I can confirm that when you change some RGB values it works.

But when you use the procedure I described it's not saved.
(I just wanted to save my current set of color that I use)
I assume it's due to the fact that the color is not changed.
I only added, to the custom palette.  so I guess an 
  oldcolor == newcolor then return
test is done before a writeconfig() of the custom palette
Comment 3 Justin Zobel 2022-11-10 22:33:15 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-11-25 05:21:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-12-10 05:18:03 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!