Bug 445803 - Doesn't honor the umask while saving xml FILE in .local/share/okular/docdata/
Summary: Doesn't honor the umask while saving xml FILE in .local/share/okular/docdata/
Status: REPORTED
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 21.08.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-20 11:56 UTC by 0BADC0DE
Modified: 2024-03-29 07:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description 0BADC0DE 2021-11-20 11:56:19 UTC 
SUMMARY
***
No matter what umask is set, XML files are saved with 0644 permissions.
***


STEPS TO REPRODUCE
1.  Setup umask at, say, 0077 (no permissions for G and O).
2.  Open a document with ocular and browse it.
3.  Check file permissions in  .local/share/okular/docdata/ for the file named after the browsed document

OBSERVED RESULT
XML file has permissions 0644

EXPECTED RESULT
XML file permissions should obey umask (0600 in the example case)

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 0BADC0DE 2024-03-29 07:33:04 UTC 
I think I have got the issue to the core.
The entire KDE environment COULD NOT started AFTER the user initialization script have been run.
In my case, it seems .bashrc is not read and thus no user-defined setting is run.
Since I have put the UMASK setting also inside /etc/login.defs this "bug" is not triggered any more.