I deleted it again and tried to re-create it via Keybase GUI -> New private folder, but nothing happened. After that, I recreated my folder via explorer.exe, but in the Keybase GUI my own folder (which I could see under K:\private) was not longer present. That is really a problem with Windows' syntax (correct syntax is with quotes: md "K:\private\nuttyx,otheruser"), but after creating a "shared" folder I tried to remove it and forgot again the quotes and deleted my own folder instead. If that path is k:\private it will raise an error in Keybase since you are not allowed to access the private folder of another user. Will not create a "shared" folder for me and otheruser, but instead will "create" k:\private\nuttyx and another folder in my current path called "otheruser". That isn't a problem in itself (except most documentation is for *NIX), but IT IS a problem when trying to create or delete a "shared" folder: Moving into the bug itself: As I explained I'm using the Windows client, so commands to create and remove folders vary a little (md/rd instead of mkdir/rmdir on top of the different folder structure): Would it be possible to ask for a drive letter upon installation?
Deleted keybase app kept chat images install#
This is the second time a software I install "forces" me a fixed drive letter (both cases I already had that drive in use) and I find it somewhat annoying, since moving the former drive usually requires me more effort (software installation broken, image & music databases broken, etc.). My former drive was usable (it was also a dokan-powered cripto unit) but I coultn't find the private or public folder.Īfter unmounting the former drive and changing the letter, both folders under keybase were accesible without restarting at all. First of all, I already had a "K:" drive in use, but the installation did not show any warning or error.
0 kommentar(er)
