Summary: | Fails to save file on systemd.automount smb3 share | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Paul Worrall <p.r.worrall> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | aacid |
Priority: | NOR | ||
Version First Reported In: | 24.12.2 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Screen recording |
Description
Paul Worrall
2025-03-02 16:43:17 UTC
Why not open a bug against x-systemd.automount? Can you please record a video so we can see what's happening? Created attachment 179198 [details]
Screen recording
Screen recording is attatched.
I'm not sure it's appropriate to report a bug against x-systemd.automount given that no other application I've tried has issues with opening, editing and saving files on this share. (I've tried Gwenview, LibreOffice Writer, Kate, KMyMoney, Krita and KolourPaint). Also, I can open and browse the share using Dolphin so it appears to be mounted OK.
The fstab entry looks like this:
//nas.local/shared /remote/shared smb3 credentials=/etc/paul.credentials.nas,uid=1001,gid=5000,file_mode=0664,dir_mode=0775,x-systemd.automount 0 0
... and if I edit it just to remove the `,x-systemd.automount` bit and reboot then no problem with okular either.
Well, reading the code, that is impossible to happen :D But it clearly happens ... If you give us very detailed and very easy to follow instructions on how to reproduce your setup (and no "Have an SMB share from another device mounted on your PC with the option "x-systemd.automount" in its fstab entry" is not enough) we may try to reproduce ourselves. |