Mageia 4 just offered KDE 4.12.5 as an update from 4.11.4. But now kwrite always starts with a black background color, which means my text files are all black on black. In the preferences panel, I see that the background color is already set to white. If I click the "Apply" button, the background color changes to white, but the next time I restart kwrite, the background color changes to black again. This is a regression as I never had this bug before.
CC: (none) => lmenut, neoclust
Did you restart KDE after the full update ?
Depends on: 13221 => (none)
Yes, I rebooted my machine.
Works for me. If you create new users, does it work there?
CC: (none) => mageia
(In reply to Sander Lepik from comment #3) > Works for me. If you create new users, does it work there? I tested with an existing user account with which I never(?) used kwrite before. The text is black on white, as expected. I tested with 2 user accounts with which I use kwrite a lot. Both have text black on black, despite preferences say black on white. I guess the kwrite config file from 4.11.4 makes things go wrong with the upgrade to 4.12.5.
Ah, interesting findings: a) Rename ~/.kde4/share/config/kwriterc to ~/.kde4/share/config/kwriterc.old b) Start kwrite: text is black on white. c) Restart kwrite: text is still black on white. d) Go to you preferences ("Configuration > Configurer l'éditeur" in french), click "Apply" and then "OK". No need to edit anything, just do that. e) Restart kwrite: text is black on black. Restarting kwrite again doesn't help. f) kill kwriterc, and then restart kwrite: text is black on white again. So the problem is not the old config file. The problem is kwrite 4.12.5 itself which is buggy.
Can you diff the 2 config files and see what goes wrong during saving?
(In reply to Sander Lepik from comment #6) > Can you diff the 2 config files and see what goes wrong during saving? [Kate Renderer Defaults] -Schema=Normal +Schema= So "Normal" goes away.
It works fine for me, and I can't reproduce; kwrite always saves correctly Schema=Normal here. Please, could you verify that all KDE packages are updated rpm -qa |grep -- "-4.11.[45]"
OK, found the problem, it's a packaging issue in kate. 3 configuration files are incorrectly packaged in kate, while they should be in katepart. I will fix this tonight. In the meantime, you can install kate, the advanced text editor.
Hardware: i586 => AllAssignee: bugsquad => lmenutSource RPM: kwrite-4.12.5-1.mga4 => kate-4.12.5-1.mga4
katepart-4.12.5-1.1.mga4 is available in updates_testing and should fix this bug.
Summary: kwrite 4.12.5 doesn't save parameters - the background color remains black on restart => kwrite 4.12.5 doesn't save color schema - the background color remains black on restart
Suggested advisory : This update fixes a packaging issue in kate (configuration files missing in katepart), that prevents kwrite 4.12.5 to properly save the color schema. Reference: https://bugs.mageia.org/show_bug.cgi?id=14416 Updated packages in core/updates_testing: srpm: kate-4.12.5-1.1.mga4.src.rpm i586: kate-4.12.5-1.1.mga4.i586.rpm kate-devel-4.12.5-1.1.mga4.i586.rpm kate-handbook-4.12.5-1.1.mga4.noarch.rpm katepart-4.12.5-1.1.mga4.i586.rpm kate-plugin-pate-4.12.5-1.1.mga4.i586.rpm ktexteditor-4.12.5-1.1.mga4.i586.rpm kwrite-4.12.5-1.1.mga4.i586.rpm kwrite-handbook-4.12.5-1.1.mga4.noarch.rpm libkateinterfaces4-4.12.5-1.1.mga4.i586.rpm libkatepartinterfaces4-4.12.5-1.1.mga4.i586.rpm libktexteditor-codesnippets0-4.12.5-1.1.mga4.i586.rpm x86_64: kate-4.12.5-1.1.mga4.x86_64.rpm kate-devel-4.12.5-1.1.mga4.x86_64.rpm kate-handbook-4.12.5-1.1.mga4.noarch.rpm katepart-4.12.5-1.1.mga4.x86_64.rpm kate-plugin-pate-4.12.5-1.1.mga4.x86_64.rpm ktexteditor-4.12.5-1.1.mga4.x86_64.rpm kwrite-4.12.5-1.1.mga4.x86_64.rpm kwrite-handbook-4.12.5-1.1.mga4.noarch.rpm lib64kateinterfaces4-4.12.5-1.1.mga4.x86_64.rpm lib64katepartinterfaces4-4.12.5-1.1.mga4.x86_64.rpm lib64ktexteditor-codesnippets0-4.12.5-1.1.mga4.x86_64.rpm
Assignee: lmenut => qa-bugs
Testing on Mga4, i586. I could reproduce the bug (steps d and e of comment 5 are all it takes). After the update, you have to set the correct colour schema manually once more, but after that kwrite keeps the correct setting, even when closing and reopening the program. So I consider this bug fixed, and set the appropriate whiteboard marker.
CC: (none) => wassiWhiteboard: (none) => MGA4-32-OK
(In reply to user7 from comment #12) > Testing on Mga4, i586. > > I could reproduce the bug (steps d and e of comment 5 are all it takes). > After the update, you have to set the correct colour schema manually once > more, but after that kwrite keeps the correct setting, even when closing and > reopening the program. So I consider this bug fixed, and set the appropriate > whiteboard marker. You need to test still Mageia 4 64 too,you need to have both stable releases Mageia 4 and Mageia 3 with bot arch x86 and x86_64 at least in virtualbox to test packages in qa team testing.
CC: (none) => ozkyster
Wassi knows the procedure Otto :-) Any single test is useful, we don't ask testers to test all arches and releases by themselves. Feel free to test Mageia 4 x86_64 and to validate the update afterwards.
CC: (none) => remi
No he don't know if he let testing to this and thinks it's finished when he tested only one arch.
Please mind how you speak about other contributors Otto, in this case you misunderstood Wassi's comment. He said that he "consider[s] the bug fixed, and set[s] the appropriate whiteboard marker", that is MGA4-32-OK. That's about as good as a testing report can be, there is nothing to complain about here.
Test Mga4, Version : 2:4.12.5-1.mga4 i586. Ok.
CC: (none) => nmrk.n
Otto: If you look at the history of the wiki page you sent me on another bug report, you will see that I even wrote (small) parts of it: https://wiki.mageia.org/en/QA_process_for_validating_updates That being said, you are of course right when you say that an update candidate must be tested on both arches. However, you are wrong when you say it must be tested by the same tester (i.e. me) on both arches. Personally, I prefer to only test on one arch (the one I am using on real hardware). I am aware that this update is not yet good to go. As indicated by the introduction of comment 12 ("Testing on Mga4, i586."), I am reporting the results of my testing, i.e. that the bug seems fixed on Mga4 i586. Finally, please try to phrase your thoughts in a more friendly way. I understand your intentions are good, but your wording is quite aggressive. If I was a new contributor, I would have probably stopped contributing by now. Rémi: Thanks! I know I haven't been very active the last months, but I still like to test packages here and there (as time permits). It's nice to know I haven't been forgotten. :)
Testing Mageia4 x64 real hardware Thanks to previous testers for their precisions. Ensured I had *all* (except devel) pkgs cited in the update, from normal repositories; version 4.12.5-1.mga4. Tried the problem with Kate (in case) - no problem! Having never used Kwrite since installation, the file ~/.kde4/share/config/kwriterc contained only the final [MainWindow] section. Kwrite started up OK black-on-white. As user7 suggested, just doing Settings -> Configure Editor -> Apply was sufficient to turn the screen all black; and it stayed that way on re-launching Kwrite. The config file was fully populated, including the troublesome line Kate Renderer [Defaults] Schema= Updated from Updates Testing all the components (except devel) to 4.12.5-1.1.mga4 . The config file remained deformed as above, and Kwrite when first launched still showed a black screen. Doing Settings -> Configure Editor -> Fonts & Colours/Colours/Editor Background Colours/Text Area setting to white -> Apply reverted the screen to white, and it stayed that way on re-launching Kwrite. The config file correctly shows [Kate Renderer Defaults] Schema=Normal So the update is OK. BUT: if possible, it should warn the user of the need to re-set the Kwrite background colour once subsequently.
CC: (none) => lewyssmithWhiteboard: MGA4-32-OK => MGA4-32-OK MGA4-64-OK
Here kwrite works just normally without updating it from testing,i can save color scheme normally it even loads that saved colors scheme at kwrite restart.
(In reply to Otto Leipälä from comment #20) > Here kwrite works just normally without updating it from testing,i can save > color scheme normally it even loads that saved colors scheme at kwrite > restart. This bug affects only the users who don't have kate installed (default install).
Validating. Advisory uploaded.
Keywords: (none) => validated_updateWhiteboard: MGA4-32-OK MGA4-64-OK => MGA4-32-OK MGA4-64-OK advisoryCC: (none) => sysadmin-bugs
CC: (none) => detlefschmidt
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2014-0189.html
Status: NEW => RESOLVEDResolution: (none) => FIXED