https://bugs.kde.org/show_bug.cgi?id=376098
Raghavendra kamath <raghavendr.ra...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|grave |critical
CC| |raghavendr.ra...@gmail.com
--- Comment #3 from Raghavendra kamath <raghavendr.ra...@gmail.com> ---
When I try to do ctrl + S on a read only file , it behaves as if it is saving,
but the title bar clearly shows a star and "(write protected)" is suffixed
after the document name, this is the only indication that it is readonly. it
doesn't show dialog box or warning message. The user who somehow missed the
title bar change wouldn't know if the file is readonly.
The actual saving does happen though, even if the file is marked readonly for
user. Even if the owner is "root" in linux systems a user can overwrite the
file.
This gets confusing as the title bar shows a star and "write protected but the
file actually gets saved . And again when you try to close the file , it
prompts for saving, when you click yes then the file is saved and the file
permission is restored to read and write for the user.
I tested with a file whose owner was root and group + others only had read
permission. After making some changes the files ownership and permission were
reverted back to user.
I think
1) Krita shouldn't change file ownership and permissions (somewhat serious and
dangerous)
2) It should have proper warning that the file is just read only
3) It also shouldn't do the save when the file is read only, it may offer save
as option so that user can save a copy of the file.
P.S. I am marking this critical as files owned by root can be changed. In
future when we scripting ability this can turn into a nightmare in my opinion.
--
You are receiving this mail because:
You are watching all bug changes.
