In Cauldron, I edited a file whose permissions were root.apache using kwrite. On save, file permissions were reset to root.root, making the configuration file unreadable by Apache.
Assignee: bugsquad => mageia
Assignee: mageia => kde
is it still valid with current cauldron ?
CC: (none) => mageia
(In reply to Nicolas Lécureuil from comment #1) > is it still valid with current cauldron ? Yes, I can still reproduce with kate-16.12.3-2.mga6.src.rpm.
Source RPM: kate-15.12.3-1.mga6.src.rpm => kate-16.12.3-2.mga6.src.rpm
Source RPM: kate-16.12.3-2.mga6.src.rpm => kwrite-16.12.3-2.mga6
CC: (none) => zen25000
This probably explains why I had permissions changed from root:apache to root:root last week (just before Mga6 release). I had been editing a zoneminder configuration file. (using Kate I suspect as it's my usual editor of choice).
Pfff... I just broke Bugzilla due to this bug, because kwrite reverted file permissions from root.apache to root.root, making some files unreadable by apache.
Whiteboard: (none) => MGA6TOOTarget Milestone: --- => Mageia 6Priority: Normal => High
For the record, it's no longer possible to use kate/kwrite as root in Cauldron: # kwrite .bashrc Executing KWrite as root is not possible. To edit files as root use: SUDO_EDITOR=kwrite sudoedit <file> KDE enforced this in 17.04, see: https://phabricator.kde.org/D4634 This means we won't get any help from upstream to fix this bug. :( Note: sudoedit doesn't fit my workflow, because changes are copied into the original file only when you quit kate/kwrite. Saving changes while keeping the application opened will only save changes into the copy of the original file, not in the original file itself. Looks like I will have to find another text editor...
I just stumbled onto this bug while searching for something else. I can tell you that somewhere along the line the decision about running various GUI apps like Kwrite and Dolphin as root was reversed. I just ran Kwrite as root within Mageia 7, with no problem whatsoever. So perhaps somebody should check to see if this bug is still valid.
CC: (none) => andrewsfarm
Yes, this is fixed in Mageia 7.
Status: NEW => RESOLVEDResolution: (none) => FIXED