Kate (?and Quanta and KDevelop user preferences) do not save

Thanks for the report.

I have tried to reproduce this and was successful, however, I noticed that there is one step that might be missing. In case of the original color being black, after clicking on the color palette to change the new color, I also had to change the And after selecting a color, I needed to change the value bar in order that the correct values are transferred into the RGB fields. After this, the color is correctly selected.

Can you confirm this behaviour?

Thanks

I was the original poster on the forums and it will hold most of the highlights set, but will not hold the standard text color and background to an inverse of the default...i.e. I want to get black background with white text. and then color accordingly. Also the shortcuts are not holding in kate, haven't seen any issue there for quanta or kdevelop(don't really use this one though)

I have tried exactly the same what you describe. I cannot reproduce it. I needed to change the background color under the tab Colors instead of Highlighting Text Styles. However if the colors are set and kate is exited, after reloading the file it shows the same colors as set.

I am using gutsy with the newest upgrades. My KDE Version is 3.5.8 and Kate Version is 2.5.8. DO you have other versions?

I have the latest versions as well and actually teh background will hold now that I tried it again and I recall that was what was happening, it is that the text in white does not ever show up...it always resets to black. I have tried setting normal text in both the normal styles and highlighting styles and it just keeps resetting to black.

@ Ralph Janke

Thanks for your reply. I am using the same versions of Gutsy, Kate and KDE as you.

>In case of the original color being black, after clicking on the color palette to change the new color,
> I also had to change the And after selecting a color, I needed to change the value bar in order that the
> correct values are transferred into the RGB fields.

I don't think I can reproduce this behaviour (however I'm not sure I follow 100% what you mean). I do notice that the Kate custom colour selector defaults to black though, so you have to drag the selector to a 'brighter' location each time you use it. After pressing OK in the color selector the correct colour appears in the "Highlight Text Styles" tab, but after pressing Apply and/or OK, the colour is not applied, and the settings are lost.

Is there no one else who cannot change the normal text color styles? Whenever I change them, I can see it change in the settings dialog, but once I click okay, things are back to defaults.

When I follow the above procedure that I stated, the settings are applied and also saved and recalled when I restart Kate.

Maybe you have a different version of Kate. Please go to help->About Kate and help->About KDE and give us the versions.

Thanks

My KDE Version is 3.5.8 and Kate Version is 2.5.8. Being that this happens across some other editing app, I feel like it might be mostly a KDE/permissions thing.

Just to be more clear on what I am seeing as people don't seem to be able to duplicate this issue.

I first open Kate, then type some text, anything will do, just something to see the changes applied.

Then I load Settings->Fonts&Colors->Normal Text Styles
Next I change the normal color for normal text to anything other than the default of black
I do this by clicking on the the little black box indicating the current color, then on the dropdown I select forty colors to get simple ones to choose from I select something like red or w/e and click Ok, then Apply and nothing, if I click ok from there it exits the settings and if I go back, it is set to black again.

I too encountered this behavior, and it's related to a bug I encountered earlier when trying to open kwrite instead of kate in kubuntu 7.10.

Everytime kwrite was opened (but not kate) , I would get a permission error on the file ~/.kde/share/config/kwriterc stating, more or less, that any configuration changes i made would not be saved. It turns on that my kubuntu install had set the file to be owned by root. Changing the owner to my username/group ('sudo chown myusername:myusername ~/.kde/share/config/kwriterc') made the error disappear.

While I could change many settings in kwrite without problem, changing text colours and syntax highlighting colours was problematic as the colours would not change with the 'apply' button. I decided to try to do the same kate, and experienced the exact same problem (I believe kwrite is a simplified version of kate that still uses many kate configuration files, or something like that.)

Investigation of file permissions in ~/.kde/share/config revealed three of kate's configuration files were also set to root;

katepartindentjscriptrc
katepartluaindentscriptrc
katesyntaxhighlightingrc

I believe that while kateschema controls the background colour et. al., katesyntaxhighlightingrc controls all text colouring. I changed the permissions of all three back to my account, and presto, now I can change colours! I suspect only katesyntaxhighlightingrc is needed, but I also think that changing the permissions on the other two would fix future grief if I ever had to change the default indentation.

Aside: In total, my installation had nine files in ~/.kde/share/config that had root permissions. The other four are:

knetworkconfrc
adept_batchrc
adept_installerrc
adept_updaterrc

My problems using adept (while not signifigant as I don't use it much) went away after I changed the adept_* file permissions. Also, the inconsistencies I've noticed (settings didn't always save) when setting the network up manually (static IP) in the KDE control center disappeared after changing the permissions on knetworkconfrc.

I'm sure the file permissions are not applied as such on all kubuntu 7.10 installs (or these bugs would be far more widespread), so I'm looking for the common denominator. The only thing I can think of is, I experienced the 'Kicker adds _: Entries in K-menu: to certain programs', (https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/135084) which was linked to application of kde settings from the en_CA (and others) locales. What locales are you using?

Hi David,

Brilliant useful post, thank you! I have not tried yet, but it sounds exactly the same, so I am hopeful your solution will work for me.

I also had the locale en_CA issue with Kicker, so these problems all seem related somehow.

Word up, changing permissions on these files

katepartindentjscriptrc
katepartluaindentscriptrc
katesyntaxhighlightingrc

made all my syntax issues go away, thanks...question I have is how did those files get set to root in the first place?

I've also resolved it. The particular files involved differed from those mentioned by David Knippers and newsun.

The solution was:

sudo chown all files mentioned by David Knippers to your own username. My settings still would not save.

Next

sudo chown -R username ~/.kde/share/apps kate
sudo chown -R username ~/.kde/share/apps katepart

This removes all settings files from root ownership and readonly status for other users.

I can't see that there's ever a good reason why files in ~/.kde should be owned by root, so I was happy to chown everything.

I'd be interested to know if all users (like me) use or have used English locale settings set to something non-standard (ie not US) and/or had the problem with borked text in the KDE menu. See https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/135084

Obvious typos corrected:

sudo chown -R username ~/.kde/share/apps/kate
sudo chown -R username ~/.kde/share/apps/katepart

I also had an issue the other day with kde totally locking me out after a language update, requiring jiggery-pokery with apt-get and Gnome to solve it. It's effected quite a few people. See http://ubuntuforums.org/showthread.php?t=695073&page=2

So issues with non us_EN locale seem persistent. I've had these problems since a fresh install of Feisty on a clean hard disk.

Arrgggh! I mean Gutsy!

Is it ok to close this report?

Yes

thanks

I'm having this issue, but specifically with the function names in Kdevelop 3.9.91.

They're stuck on an almost black looking purple, and I can't see them.

I've found the files that (I think) are associated with the config for kdevelop, but chowning them hasn't made a difference. I tried 'chown -R' ing the whole share directory and even the file kdeveloprc specifically, but nothing has changed.

Is this possibly associated with the silly little "Code Browser" tooltip that pops up?

Is this (old) bug really fixed? I have the same "root" permission problem under Kubuntu Lucid (64-bit) as described in post #10.