Unhandled Incoming RPC 137
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Issue Reproduction/Details:
After installing the Keybase application previously, I set out to reset my keys and utilize this a bit more. I uninstalled keybase, and then reinstalled and was presented with the following error:
Unhandled Incoming RPC 137
keybase.1.provisionUi.PromptNewDeviceName
Windows event log provided the following information:
Application 'C:\Users\USERNAMEREMOVED\AppData\Roaming\Keybase\kbfsdokan.exe' (pid 916) cannot be restarted - Application SID does not match Conductor SID..
my log id: 3914ceff04d2b08956d9711c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Windows reinstall or key-reset flow that reports RPC 137 and PromptNewDeviceName, then inspect the related application logs using log ID 3914ceff04d2b08956d9711c. The work is done when this RPC no longer produces an unhandled error and the affected provisioning flow completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100