When setting up a Vault, the installer denies changing the installation folder. When changing it from its default $user/.local/share/plasma-vault/...and so on, it throws the error "the specified path does not exist". So, for me, this renders the software useless. For security reasons and drive space restrictions, I need to store the vault files on another folder.
I can't reproduce your issue. I was able to successfully make a new vault on an external drive with Plasma version 5.26.5. Would you be able to provide your system information (can be found in system settings -> about this system) as well as instructions on what you did when making the vault? This should help a developer or another triager figure out what the problem is.
Created attachment 156358 [details] Screenshot of the error Steps to reproduce: 1. Install plasma-vault and gocryptfs via pamac 2. Rebooting 3. Create a new vault, name 'test', setting password 4. Trying to change the path of either the encrypted data location or the mount point results in error 'The specified path does not exist'. It occurs immediately, when changing the first letter of the defaults. It also does not matter, wether the new path / folder exists, or not. See attached screenshot. System: Kernel: 6.1.11-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1 Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux CPU: Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP smt: enabled arch: Zen 2 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: NVIDIA GA104 [GeForce RTX 3070] vendor: ZOTAC driver: nvidia v: 525.89.02 arch: Ampere pcie: speed: 16 GT/s lanes: 16 bus-ID: 2d:00.0 chip-ID: 10de:2484 class-ID: 0300 Display: x11 server: X.Org v: 21.1.7 compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0 screens: 1 API: OpenGL v: 4.6.0 NVIDIA 525.89.02 renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2 direct-render: Yes Drives: Local Storage: total: 2.96 TiB used: 576.48 GiB (19.0%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B2QEXM7 temp: 25.9 C scheme: GPT ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B2QEXM7 temp: 44.9 C scheme: GPT ID-3: /dev/sda vendor: Samsung model: SSD 870 QVO 2TB size: 1.82 TiB speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: GPT Partition: ID-1: / size: 227.88 GiB used: 54.11 GiB (23.7%) fs: ext4 dev: /dev/nvme1n1p2 ID-2: /boot/efi size: 299.4 MiB used: 312 KiB (0.1%) fs: vfat dev: /dev/nvme1n1p1
After some more testing, I stumbled upon something. If the vault location is selected with the file dialog button (which is what I done initially), there are no errors and the vault gets created successfully. However if a file path is typed out manually (which is what the reporter is doing), then the "this specified path does not exist" error appears. When typing the file path, it has to point to an empty folder (without *.enc) to be accepted. What is confusing to me is that the default path provided has *.enc added to the end (ironically it doesn't actually exist yet), which is implying to the end user that it also needs to be added to the new path, which causes the error if they do so. I don't know if this is a bug per-se, but it does cause some confusion.
(In reply to Ben Bonacci from comment #3) > After some more testing, I stumbled upon something. If the vault location is > selected with the file dialog button (which is what I done initially), there > are no errors and the vault gets created successfully. However if a file > path is typed out manually (which is what the reporter is doing), then the > "this specified path does not exist" error appears. > When typing the file path, it has to point to an empty folder (without > *.enc) to be accepted. What is confusing to me is that the default path > provided has *.enc added to the end (ironically it doesn't actually exist > yet), which is implying to the end user that it also needs to be added to > the new path, which causes the error if they do so. > > I don't know if this is a bug per-se, but it does cause some confusion. I'd rather say broken (or not optimized) than confusing. :) a) When entering a path manually (as I did) that actually does exist, it still shows the error "path does not exists". b) Contrary to your observation, the error also occurs when not providing the *.enc file at the end of a path. Suggestion: When a user enters a path that does not exists, it should just silently create it - or at least ask the user, if he wants to create it.