When saving a symbol or schematic on a network drive (QNAP NAS) , an error 95 “Failed to set temporary file permissions (error 95: Operation not supported)” is reported, and saving fails.
No problem when saving a footprint.
The network drive on a QNAP NAS is available in Nautilus before starting KiCad and projects, symbols, footprints etc can be read. Other programs have no problems writing files, including the .~lock. LibreOffice file as a temporary file.
The network drive is a Samba share and it has Cifs file-system.
[tryitagain] has reported a solution working from him, but I prefer not having a password written in a file.
Does anybody has found an other solution in the meantime?
Version is:
Application: KiCad x86_64 on x86_64
Version: 8.0.8-2.fc41, release build
Libraries:
wxWidgets 3.2.6
FreeType 2.13.3
HarfBuzz 9.0.0
FontConfig 2.15.0
libcurl/8.9.1 OpenSSL/3.2.4 zlib/1.3.1.zlib-ng libidn2/2.3.7 nghttp2/1.62.1
Platform: Fedora Linux 41 (Workstation Edition), 64 bit, Little endian, wxGTK, X11, gnome, wayland
Build Info:
Date: Jan 14 2025 00:00:00
wxWidgets: 3.2.6 (wchar_t,wx containers) GTK+ 3.24
Boost: 1.83.0
OCC: 7.8.0
Curl: 8.9.1
ngspice: 44
Compiler: GCC 14.2.1 with C++ ABI 1019
Build settings:
Same thought here. However, my logic was/is that in order to see that NAS password a bad actor would already have access to the files on that computer anyway.
I have not discovered a better method to automatically mount my NAS in Linux (Fedora). My knowledge of Linux is just adequate enough to get me in trouble.
I can’t find that topic but I think in the past people have tried using gvfs for mounting Samba shares and found it deficient for KiCad’s purposes. gvfs is a user-space implementation of a Samba client which is what Nautilus uses as opposed to a kernel Samba client, whcih is what tryitagain is using.
You can mitigate the risk by putting the credentials file in a root owned file, thus a bad actor would have to be root first to get the password.
For automounting network shares you can use the autofs feature, but this is an advanced Linux feature.
Projects can be loaded from the Samba share.
After opening the schematic of the project it is also possible to export a Net list, a Spire .cir file and I also see a ~project.kicad_sch.lck as well as a _autosave-project.kicad.sch file, both with a size > 0.
Hence it seems to be different to write a file and to rename temporary files.
It is a renaming of a local file in /tmp to the network share …
I now have several eeschemaxxxxxxxx files being not deleted after closing Kicad, but which can be easily deleted, just for information.
