https://bugs.kde.org/show_bug.cgi?id=465763
--- Comment #4 from Julius R. <c3i8zv...@mozmail.com> --- (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. -- You are receiving this mail because: You are watching all bug changes.