Created attachment 180534 [details] What happens when you try to make a Vault. SUMMARY Can't make a vault STEPS TO REPRODUCE 1. Install KDE Plasma 2. Follow the steps to make a Plasma Vault specified by the Welcome Center 3. Input a name OBSERVED RESULT The "Next" button does not activate EXPECTED RESULT Activation of the "Next" button, or an error if the name doesn't meet a requirement. SOFTWARE/OS VERSIONS ERROR: VkInstanceCreateInfo::pApplicationInfo::apiVersion has value of 0 which is not permitted. If apiVersion is not 0, then it must be greater than or equal to the value of VK_API_VERSION_1_0 [VUID-VkApplicationInfo-apiVersion] Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.3.80 KDE Frameworks Version: 6.14.0 Qt Version: 6.8.3 Kernel Version: 6.11.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700F Memory: 32 GiB of RAM (31.2 GiB usable) Graphics Processor: NVIDIA GeForce RTX 3070 ADDITIONAL INFORMATION Hardware, KDE info are all pasted straight from kinfo. If something changes after a reboot, I'll include an updated version in the next comment.
The info changed, but both errors still persist. ERROR: VkInstanceCreateInfo::pApplicationInfo::apiVersion has value of 0 which is not permitted. If apiVersion is not 0, then it must be greater than or equal to the value of VK_API_VERSION_1_0 [VUID-VkApplicationInfo-apiVersion] Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.3.80 KDE Frameworks Version: 6.14.0 Qt Version: 6.8.3 Kernel Version: 6.11.0-24-generic (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700F Memory: 32 GiB of RAM (31.2 GiB usable) Graphics Processor: NVIDIA GeForce RTX 3070
I can't reproduce this on git-master, Solus. Typing in a vault name activates the Next button as expected. I *am* able to reproduce on Neon Unstable This may be a packaging issue in Neon
Created attachment 180535 [details] attachment-283974-0.html Could be a Neon Unstable problem, what package do I install? On Tue, 22 Apr 2025, 21:56 TraceyC, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=503188 > > TraceyC <kdedev@tlcnet.info> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |kdedev@tlcnet.info > Status|REPORTED |CONFIRMED > Ever confirmed|0 |1 > > --- Comment #2 from TraceyC <kdedev@tlcnet.info> --- > I can't reproduce this on git-master, Solus. Typing in a vault name > activates > the Next button as expected. > I *am* able to reproduce on Neon Unstable > This may be a packaging issue in Neon > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug.
I forgot not to reply through Gmail again
The only backend supported now for new vaults is Gocryptfs; I suspect Neon doesn't include that. It needs to.
(In reply to Nate Graham from comment #5) > The only backend supported now for new vaults is Gocryptfs; I suspect Neon > doesn't include that. It needs to. Maybe the problem could be the not installed vault snap?
Also, I'm changing the packages to unstable Edition since that's what this is on.
Does the bug go away if you manually install the "gocryptfs" package?
(In reply to Nate Graham from comment #8) > Does the bug go away if you manually install the "gocryptfs" package? yup.
Then the proximate cause is Neon not shipping that package by default. The root cause may be Plasma Vaults not enforcing this in CMake; I'll investigate.
Yep, that's it. The project has no dependency on gocryptfs declared, which is my bad. I forgot to add this when I made gocryptfs the only supported backend.
(In reply to Nate Graham from comment #11) > Yep, that's it. The project has no dependency on gocryptfs declared, which > is my bad. I forgot to add this when I made gocryptfs the only supported > backend. I see, what about the kinfo error? I think I'll have to submit a bug for that if it's still there
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-vault/-/merge_requests/65
(In reply to Nik Nikovsky from comment #12) > I see, what about the kinfo error? This is unrelated and needs its own bug report.
(In reply to Nate Graham from comment #14) > (In reply to Nik Nikovsky from comment #12) > > I see, what about the kinfo error? > This is unrelated and needs its own bug report. I've created it here: https://bugs.kde.org/show_bug.cgi?id=503267
Git commit 49463366e488642c7a2368f964605595de94cca5 by Nate Graham. Committed on 24/04/2025 at 08:06. Pushed by ngraham into branch 'master'. Require gocryptfs at runtime Now that we removed the multiple backend support and only support gocryptfs, we need to declare it as a required runtime package, or else there's a risk that distros won't include that package and then the software will be broken. Amends ba292cce35907707cab41e651fd86b847117ed73 FIXED-IN: 6.4.0 M +10 -1 CMakeLists.txt A +14 -0 cmake/FindGocryptfs.cmake https://invent.kde.org/plasma/plasma-vault/-/commit/49463366e488642c7a2368f964605595de94cca5