I'm not entirely surprised at the read only thing (see https://ask.libreoffice.org/en/question/3827/doc-files-open-as-read-only/) though I'm a little surprised about the inconsistent behavior that under some file managers that happens and under others, it doesn't. That's not really relevant here, but may be worth some investigating.
My past experience tells me that the dialog about the file being locked for editing comes up when someone using the share has the file open and someone else tries to open it. Another possibility is if someone has it open and then their system/LibreOffice crashes. I haven't investigated this but I suspect a lock file is being used to indicate whether or not it's being used.
The output from PCManFM-Qt is actually quite useful. Those "file monitor cannot be created" warnings originate from some SMB-specific code. It would be interesting to compare this to what Thunar is doing, so if you could test it, that would be great.
I'm not entirely surprised at the read only thing (see https:/ /ask.libreoffic e.org/en/ question/ 3827/doc- files-open- as-read- only/) though I'm a little surprised about the inconsistent behavior that under some file managers that happens and under others, it doesn't. That's not really relevant here, but may be worth some investigating.
My past experience tells me that the dialog about the file being locked for editing comes up when someone using the share has the file open and someone else tries to open it. Another possibility is if someone has it open and then their system/LibreOffice crashes. I haven't investigated this but I suspect a lock file is being used to indicate whether or not it's being used.
The output from PCManFM-Qt is actually quite useful. Those "file monitor cannot be created" warnings originate from some SMB-specific code. It would be interesting to compare this to what Thunar is doing, so if you could test it, that would be great.
As always, thank you, Leó!