[Bug]: Linux/NixOS issues with file-permissions of new created project #1322
Comments
|
|
I would like to add my two cents here. To be able to delete files, by default you only need "-wx" in the parent directory and no rights or ownership of the file itself. I skimmed through the source code and couldn't find anything. The mode parameter for writeFile is not set and chmod is not used either. The umask is left unchanged. So the default should apply: (0777 & ~umask) and (0666 & ~umask). How is your Which command line is used to start Publii? If Publii's developers worked around the problem, it would only lead to further complications. |
I didn't ever change/touch the umask - my default is: I can create a wrapper and set the correct umask/use setfacl before starting Publii, do you have a suggestion on what to set/which value?
"Publii" in the NixOS-case is a binary-wrapper providing dependencies and starting the original Publii binary.
I see, I'm totally open to fix it in our packaging if it's not an issue on any other platform :) |
A process's umask is inherited by its child processes. So either there is another process in between or the permissions are changed somewhere else after they have been created correctly (wrapper, createHome/homeMode, setfacl, tmpfiles, ). What umask is output by
You can set a default value with |
|
Hello @SebTM, have you had success yet? Is everything working now? 🤔 |
|
Hey, sorry somehow it got lost on my to-do list ✌🏻 I got the output of Publii is under "/run/current-system/systemd/lib/systemd/systemd --user --deserialize=26" -> "/nix/store/aqjspdaxc3iq935hqzhlnsyapi3j9w01-gnome-shell-45.3/bin/gnome-shell". The result of the relevant pids: I can't find the place where the umask is changed? |
|
I couldn't figure out so far why this is happening/where the umask got changed, but the I wold leave it open for further input/others having the same issues. |
|
No problem and I'm glad to hear that Publii is now running. Please note that both setfacl commands have to be issued. One for future files (-d) and the other for existing ones. ;-) It's just a workaround and if you would like to research a little further: The file system also plays a role, I would check that too. For example, look at Then the next step would be to monitor file access. |
This should be the relevant mount entry as the directory is created in "/home/sebtm/Documents/Publii". Will check sysdig soon, need to reboot to get it working ✌🏻 |
|
sysdig-publii.log |
|
There is nothing unusual in the attached file - all calls are made with the correct modes and only from Publii. It would be interesting to see a log when the error occurs. Please also paste the output of |
|
Hey, I ran the sysdig (with completely reset .dotfiles for Publii) again and ensured to try to preview multiple times which causes the issue The error-message in Publii:
I don't have a general issue with sharing it but as it exposes my whole filesystem and files I would prefer to share a specific part or not publicly if possible? ✌️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Operating system
NixOS Unstable
Publii version
0.44.4
Post editor
WYSIWYG editor
Bug description
After opening Publii for the first time and creating an test-project which works I get the following error when trying to preview:
on further inspection I found out that a couple of files are created with "r-xr-xr-x" instead of at least "rwxr-xr-x" from my expectation?
Is this expected/can this be solved or did I miss something when packaging Publii for NixOS? Appreachiate your input ✌🏻
Steps to reproduce
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: