Description: LO 6.1 snapshot 2018-02-28 is not honoring Linux umask. The files are being saved 600, even if umask requests 666. This will cause serious problems on any multi-user deployments. Steps to Reproduce: 1.Set umask to 000 2.Create a new document, and save 3.Note file permissions Actual Results: File is saved 600 Expected Results: File should be saved 666 Reproducible: Always User Profile Reset: No Additional Info: drichard@desktopnxcloud:/home/largo/tmp$ ls -lad kirk* -rw------- 1 drichard drichard 8254 Mar 1 10:00 kirk.odt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Reproduced and bibisected using repo bibisect-linux-64-6.1 to the commit referenced below. Adding Cc: to Miklos Vajna, please take a look. https://cgit.freedesktop.org/libreoffice/core/commit/?id=2157a3536f97ff5ae7c82611a801fef7e3708983 author Miklos Vajna <vmiklos@collabora.co.uk> 2018-01-08 16:49:25 +0100 committer Miklos Vajna <vmiklos@collabora.co.uk> 2018-01-09 09:09:27 +0100 sfx2 store: try rename before copying
Note that no actual changing of umask is needed for repro, eg. by default files on my system are saves as 644 (umask is 0022), but after the commit in LO they're saved as 600.
Miklos Vajna committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=fb04780cf8523ad4e900ae8b9cecbe7a2697a12a tdf#116117 sfx2 store: don't inherit temp file permissions when renaming It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(No backport, regression was master-only.)
this bug is still actual on 6.1.0.3
(In reply to deant from comment #5) > this bug is still actual on 6.1.0.3 Should be bug 119050 instead.
Both are actual. Overwriting pdfs (i didnt test that) and overwriting native format still is bugged (i tested that-https://bugs.documentfoundation.org/show_bug.cgi?id=119505)