[Digikam-devel] [Bug 145252] Umask settings used for album directory, not for image files

Arnd Baecker arnd.baecker at web.de
Fri Oct 19 20:43:16 BST 2007

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
arnd.baecker web de changed:

           What    |Removed                     |Added
  Attachment #21852|0                           |1
        is obsolete|                            |

------- Additional Comments From arnd.baecker web de  2007-10-19 21:43 -------
Created an attachment (id=21865)
 --> (http://bugs.kde.org/attachment.cgi?id=21865&action=view)
respect umask for newly created files.

> If something must be done to solve this file, this must be done in

Yes - you are (of course) right!
The relevant part is
    // store old permissions
    mode_t filePermissions = S_IREAD | S_IWRITE;
(If a file previously exists, `filePermissions` is modified, so that
its protections are used.)
So instead of S_IREAD | S_IWRITE, the umask has to
be taken into account.

The attached patch tries to do so and also applies the permissions
in both situations of overwritten or newly created files.

Achim, could you maybe test the patch, if everything is ok?

Best, Arnd

More information about the Digikam-devel mailing list