It looks like signald creates directories on demand : /var/lib/signald/{attachments/,avatars/,stickers/} at least. Stickers is the most problematic as it contains subfolders.
Not sure if mautrix-signal should be able to write to them, but it certainly needs to read from them.
Currently, they are created with 700 permissions. This despite the systemd unit containing:
Maybe these folders should be created ahead of time as a first approach. I'm unsure if there's more of those. They should have proper group permissions if we are to use the fix I suggested in #13.
Given that the umask seems correct, it might be an upstream issue.
Logs
This is the error message:
File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mausignald/signald.py", line 51, in _run_event_handler
await handler(event)
File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mautrix_signal/signal.py", line 54, in on_message
await self.handle_message(user, sender, evt.data_message)
File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mautrix_signal/signal.py", line 106, in handle_message
await portal.handle_signal_message(user, sender, msg)
File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mautrix_signal/portal.py", line 488, in handle_signal_m
essage
sticker=True)
File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mautrix_signal/portal.py", line 573, in _handle_signal_attachment
with open(attachment.incoming_filename, "rb") as file:
PermissionError: [Errno 13] Permission denied: '/var/lib/signald/stickers/9acc9e8aba563d26a4994e69263e3b25/16'
[2021-08-07 16:53:48,669] [WARNING@mausignald] No handlers for RPC request unreadable_message
Describe the bug
It looks like signald creates directories on demand :
/var/lib/signald/{attachments/,avatars/,stickers/}
at least. Stickers is the most problematic as it contains subfolders.Not sure if mautrix-signal should be able to write to them, but it certainly needs to read from them.
Currently, they are created with 700 permissions. This despite the systemd unit containing:
Maybe these folders should be created ahead of time as a first approach. I'm unsure if there's more of those. They should have proper group permissions if we are to use the fix I suggested in #13.
Given that the umask seems correct, it might be an upstream issue.
Logs
This is the error message: