1.4.0 appimage bug on Ubuntu 18.04 and Samba share mounted as CIFS

Hi.

I have mounted Samba share on my local network using below command:

mount -t cifs //192.168.1.1/backup -o username=okropnick,vers=1.0,sec=ntlm /home/kuba/mnt

When I am copying file to vault on Samba share each time I have below errors:

20:05:17.901 [Thread-5010] ERROR o.c.f.fuse.ReadWriteFileHandler - Flushing file failed.
java.nio.file.FileSystemException: /home/kuba/mnt/PGD/d/DF/5XHFOP2HETY32TGCUFJMYVFL4QJ76F/LRBGJYHHRTDTDGJDLZTO6ZCWPLWG622D.lng: Operation unallowed
at java.base/sun.nio.fs.UnixException.translateToIOException(Unknown Source)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
at java.base/sun.nio.fs.UnixFileAttributeViews$Basic.setTimes(Unknown Source)
at org.cryptomator.cryptofs.OpenCryptoFile.force(OpenCryptoFile.java:198)
at org.cryptomator.cryptofs.CryptoFileChannel.force(CryptoFileChannel.java:217)
at org.cryptomator.frontend.fuse.OpenFile.flush(OpenFile.java:102)
at org.cryptomator.frontend.fuse.ReadWriteFileHandler.flush(ReadWriteFileHandler.java:102)
at org.cryptomator.frontend.fuse.ReadWriteAdapter.flush(ReadWriteAdapter.java:270)
at ru.serce.jnrfuse.AbstractFuseFS.lambda$init$6(AbstractFuseFS.java:144)
at jnr.ffi.provider.jffi.NativeClosureProxy$$impl$$12.invoke(Unknown Source)
20:05:17.941 [Thread-5012] ERROR o.c.f.fuse.ReadOnlyFileHandler - Error closing file.
java.nio.file.FileSystemException: /home/kuba/mnt/PGD/d/DF/5XHFOP2HETY32TGCUFJMYVFL4QJ76F/LRBGJYHHRTDTDGJDLZTO6ZCWPLWG622D.lng: Operation unallowed
at java.base/sun.nio.fs.UnixException.translateToIOException(Unknown Source)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
at java.base/sun.nio.fs.UnixFileAttributeViews$Basic.setTimes(Unknown Source)
at org.cryptomator.cryptofs.OpenCryptoFile.force(OpenCryptoFile.java:198)
at org.cryptomator.cryptofs.CryptoFileChannel.lambda$implCloseChannel$10(CryptoFileChannel.java:262)
at org.cryptomator.cryptofs.FinallyUtil.guaranteeInvocationOf(FinallyUtil.java:36)
at org.cryptomator.cryptofs.FinallyUtil.guaranteeInvocationOf(FinallyUtil.java:40)
at org.cryptomator.cryptofs.FinallyUtil.guaranteeInvocationOf(FinallyUtil.java:28)
at org.cryptomator.cryptofs.FinallyUtil.guaranteeInvocationOf(FinallyUtil.java:19)
at org.cryptomator.cryptofs.CryptoFileChannel.implCloseChannel(CryptoFileChannel.java:260)
at java.base/java.nio.channels.spi.AbstractInterruptibleChannel.close(Unknown Source)
at org.cryptomator.frontend.fuse.OpenFile.close(OpenFile.java:98)
at org.cryptomator.frontend.fuse.OpenFileFactory.close(OpenFileFactory.java:74)
at org.cryptomator.frontend.fuse.ReadOnlyFileHandler.release(ReadOnlyFileHandler.java:83)
at org.cryptomator.frontend.fuse.ReadOnlyAdapter.release(ReadOnlyAdapter.java:198)
at ru.serce.jnrfuse.AbstractFuseFS.lambda$init$7(AbstractFuseFS.java:147)
at jnr.ffi.provider.jffi.NativeClosureProxy$$impl$$13.invoke(Unknown Source)

I want only to mention, that I am using Cryptomator with Samba share for years. Problem started with version 1.4.0.