dokan: path does not exist about kbfs

[strib]

@apobekiaris can you please run keybase log send from a command prompt after you get the error, and post the resulting log ID here?

cc: @taruti @zanderz

[apobekiaris]

this what i get

• WARNING Critical clock skew: Your clock is 7h59m59.571266s off from the server
• ERROR Not confirmed

[strib]

Can you try fixing the clock on your local machine? We don't operate well with clock skew, for security reasons.

[apobekiaris]

did not help much I get the same message but now the keybase log send returns

…

- ERROR Not confirmed On Wed, Nov 21, 2018 at 11:42 PM Jeremy Stribling ***@***.***> wrote: Can you try fixing the clock on your local machine? We don't operate well with clock skew, for security reasons. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1926 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJu6FKkDlOP88wJj-VOAWCmnWzhdjnmks5uxYJdgaJpZM4YtUoB> .

-- Apostolis Bekiaris Frameworks Technical Evangelist @ DevExpress Blog @ http://apobekiaris.blogspot.com Skype/twitter: tolisss

[strib]

Maybe restart Keybase after fixing your clock? Just a guess, I'm not sure.

[apobekiaris]

actually after fixing my clock and execute an exe in keybase (with no restart) windows crashed. after windows restart and with the clock fixed i got the message I report b4

[zanderz]

Maybe you could just copy the result of keybase status on the command line and send it to [email protected] (or zanderz on keybase if it's working well enough) along with %localappdata%\Keybase\keybase.service.log and %localappdata%\Keybase\keybase.kbfs.log`
?