Using kate 16.12.2 (this version was not available in the drop-down menu on bugs.kde.org) on a KDE Neon 5.9.1 system. I'm using breeze dark for the desktop theme. Kate looks OK, but the font unfortunately is from the normal theme - it's black, so practically unreadable with the dark background. When I go to Settings-> Kate Settings -> Fonts & Colors, I can see that it uses the "Normal" theme as the default. If a click Use KDE color theme, nothing happens. If I click "Normal" and select Breeze Dark, and then either OK or Apply, the font looks as expected (readable). Without restarting, if I go back to the settings, they are saved. But as soon as I close kate and reopen it, it goes back to "Normal" default theme.
This might be related: if I open kwrite, I get this error: Configuration file "/home/tori/.config/kwriterc" not writable. Please contact your system administrator. And has the same problem with the color theme. Probably kate could use a similar error?
ll /home/tori/.config/kwriterc -rw------- 1 root root 324 paź 8 01:03 /home/tori/.config/kwriterc
ll /home/tori/.config/kwriterc -rwxrwxrwx 1 tori tori 324 lut 10 19:33 /home/tori/.config/kwriterc* No change, still doesn't remember, but now I'm not getting the error while starting kwrite
(In reply to darktori from comment #3) > ll /home/tori/.config/kwriterc > -rwxrwxrwx 1 tori tori 324 lut 10 19:33 /home/tori/.config/kwriterc* > > No change, still doesn't remember, but now I'm not getting the error while > starting kwrite I think you have wrong permissions still or sth. Can you delete kwriterc? What is the asterisk in your output above? Is it from the -F flag of ls? Can you also show the output of "ls -d ~/.config"?
(In reply to Nikolaos Kakouros from comment #4) > I think you have wrong permissions still or sth. Can you delete kwriterc? > What is the asterisk in your output above? Is it from the -F flag of ls? Can > you also show the output of "ls -d ~/.config"? Deleted the file, still no change. After I run kwrite, the file regenerated: tori@tori-neon:~$ ll /home/tori/.config/kwriterc -rw------- 1 tori tori 239 lut 16 19:26 /home/tori/.config/kwriterc Btw, the star form earlier was because it was set to executable I think, since I gave it all the permissions. tori@tori-neon:~$ ls -d ~/.config /home/tori/.config
Sorry, I meant ls -dl ~/.config . The info for the kate schema is in the .katerc file not in the .kwriterc. See the permissions of the files there and also in the .config folder
(In reply to Nikolaos Kakouros from comment #6) > Sorry, I meant ls -dl ~/.config . The info for the kate schema is in the > .katerc file not in the .kwriterc. See the permissions of the files there > and also in the .config folder ls -dl ~/.config drwx------ 27 tori tori 4096 lut 16 19:26 /home/tori/.config ls -l ~/.config/katerc -rw------- 1 tori tori 1210 lut 12 14:24 /home/tori/.config/katerc Some files in the .config folder: -rw------- 1 tori tori 124 paź 8 00:23 kaccessrc -rw------- 1 tori tori 176 paź 8 00:16 kactivitymanagerdrc -rw------- 1 tori tori 3376 lut 12 15:13 katemetainfos -rw------- 1 root root 1647 lis 26 21:19 katepartrc -rw------- 1 tori tori 1210 lut 12 14:24 katerc -rw------- 1 tori tori 1797 sty 31 16:08 kateschemarc -rw------- 1 tori tori 8783 sty 31 16:08 katesyntaxhighlightingrc -rw------- 1 root root 419 paź 8 01:02 katevirc -rw------- 1 tori tori 33 paź 17 01:32 kcalcrc -rw------- 1 tori tori 193 paź 11 21:27 kcminputrc -rw------- 1 tori tori 212 lut 12 02:30 kcmshell5rc -rw------- 1 tori tori 798 lut 15 17:17 kconf_updaterc
Oh man.. I really need sleep.. I meant the katepartrc.. Which is owned by root in your system. Change also the permissions of katevirc.
(In reply to Nikolaos Kakouros from comment #8) > Oh man.. I really need sleep.. I meant the katepartrc.. Which is owned by > root in your system. Change also the permissions of katevirc. Ok, changed ownership for both katepartrc and katevirc, and automatically, the font color has been fixed. Looks perfect now! I wonder though why the files related to kate were set to root:root, even though the rest were fine.
Glad it is solved. Could you set the bug status to resolved?