can not login in key base

[sohailaftab]

Keybase GUI Version: 2.7.3-20181005122557+83f5d808a7

i can not login in keybase window desktop app. i am just seeing this screen nothing else i have tried to install a newer version but nothing just happened

[maxtaco]

Do a keybase log send and we will investigate

[da-code-a]

Hey there, @maxtaco . Looks like @sohailaftab put his log in #14471 instead of back in here. His log ID is ca7e75a382593efa7cf5571c

I'm his co-worker, and we are working on establishing Keybase as our main method of communication. His is the only install having issues. He tried running upd check and rebooting yesterday as some other reports suggested, but still no luck.

Thank you for looking into this!

[maxtaco]

Took a quick look, there's a legit crasher in there in Windows code that we've never seen before. We'll look deeper shortly. Sorry about the bug!

[zanderz]

@sohailaftab @DonaldKBrown Research suggests that this can be caused by a conflicting driver. Would you happen to have anything installed such as Web Companion from Lavasoft? Could you send the results of the netsh WinSock Show Catalog command? Meanwhile, we will explore possible workarounds.

[zanderz]

We think we have a fix but don't know how to reproduce this - would you like to try? https://prerelease.keybase.io/windows/Keybase_2.10.0-20181030143356%2B2d20c80198.amd64.msi Thanks.

[da-code-a]

I'll have him test first thing tomorrow morning. My Linux and Windows clients are both working, currently, so I'm not sure if my own tests would help.On Oct 30, 2018 4:07 PM, Steve Sanders notifications@github.com wrote:We think we have a fix but don't know how to reproduce this - would you like to try? https://prerelease.keybase.io/windows/Keybase_2.10.0-20181030143356%2B2d20c80198.amd64.msi Thanks.

—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread. {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/keybase/client","title":"keybase/client","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/keybase/client"}},"updates":{"snippets":[{"icon":"PERSON","message":"@zanderz in #14431: We think we have a fix but don't know how to reproduce this - would you like to try? https://prerelease.keybase.io/windows/Keybase_2.10.0-20181030143356%2B2d20c80198.amd64.msi\r\nThanks."}],"action":{"name":"View Issue","url":"https://github.com/keybase/client/issues/14431#issuecomment-434487748"}}} [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/keybase/client/issues/14431#issuecomment-434487748", "url": "https://github.com/keybase/client/issues/14431#issuecomment-434487748", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } }, { "@type": "MessageCard", "@context": "http://schema.org/extensions", "hideOriginalBody": "false", "originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB", "title": "Re: [keybase/client] can not login in key base (#14431)", "sections": [ { "text": "", "activityTitle": "Steve Sanders", "activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png", "activitySubtitle": "@zanderz", "facts": [

] } ], "potentialAction": [ { "name": "Add a comment", "@type": "ActionCard", "inputs": [ { "isMultiLine": true, "@type": "TextInput", "id": "IssueComment", "isRequired": false } ], "actions": [ { "name": "Comment", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"keybase/client\",\n\"issueId\": 14431,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}" } ] }, { "name": "Close issue", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"keybase/client\",\n\"issueId\": 14431\n}" }, { "targets": [ { "os": "default", "uri": "https://github.com/keybase/client/issues/14431#issuecomment-434487748" } ], "@type": "OpenUri", "name": "View on GitHub" }, { "name": "Unsubscribe", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 401564451\n}" } ], "themeColor": "26292E" } ]

[sohailaftab]

Protocol: 17 Service Flags: 0x609 Protocol Chain Length: 2 Protocol Chain: 1012 : 1002

Winsock Catalog Provider Entry

Entry Type: Layered Chain Entry Description: LavasoftLSP over [MSAFD Tcpip [TCP/IPv6]] Provider ID: {C52CDAB2-841F-4051-9A63-7EDE5BFC31C8} Provider Path: C:\Windows\system32\LavasoftTcpService.dll Catalog Entry ID: 1015 Version: 2 Address Family: 23 Max Address Length: 28 Min Address Length: 28 Socket Type: 1 Protocol: 6 Service Flags: 0x66 Protocol Chain Length: 2 Protocol Chain: 1012 : 1004

Winsock Catalog Provider Entry

Entry Type: Layered Chain Entry Description: LavasoftLSP over [MSAFD Tcpip [UDP/IPv6]] Provider ID: {46909166-6992-4E36-B561-20FCD06A6FC8} Provider Path: C:\Windows\system32\LavasoftTcpService.dll Catalog Entry ID: 1016 Version: 2 Address Family: 23 Max Address Length: 28 Min Address Length: 28 Socket Type: 2 Protocol: 17 Service Flags: 0x609 Protocol Chain Length: 2 Protocol Chain: 1012 : 1005

Winsock Catalog Provider Entry

Entry Type: Base Service Provider Description: MSAFD Tcpip [TCP/IP] Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192} Provider Path: %SystemRoot%\system32\mswsock.dll Catalog Entry ID: 1001 Version: 2 Address Family: 2 Max Address Length: 16 Min Address Length: 16 Socket Type: 1 Protocol: 6 Service Flags: 0x20066 Protocol Chain Length: 1

Winsock Catalog Provider Entry

Entry Type: Base Service Provider Description: MSAFD Tcpip [UDP/IP] Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192} Provider Path: %SystemRoot%\system32\mswsock.dll Catalog Entry ID: 1002 Version: 2 Address Family: 2 Max Address Length: 16 Min Address Length: 16 Socket Type: 2 Protocol: 17 Service Flags: 0x20609 Protocol Chain Length: 1

Winsock Catalog Provider Entry

Entry Type: Base Service Provider Description: MSAFD Tcpip [RAW/IP] Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192} Provider Path: %SystemRoot%\system32\mswsock.dll Catalog Entry ID: 1003 Version: 2 Address Family: 2 Max Address Length: 16 Min Address Length: 16 Socket Type: 3 Protocol: 0 Service Flags: 0x20609 Protocol Chain Length: 1

Winsock Catalog Provider Entry

Entry Type: Base Service Provider Description: MSAFD Tcpip [TCP/IPv6] Provider ID: {F9EAB0C0-26D4-11D0-BBBF-00AA006C34E4} Provider Path: %SystemRoot%\system32\mswsock.dll Catalog Entry ID: 1004 Version: 2 Address Family: 23 Max Address Length: 28 Min Address Length: 28 Socket Type: 1 Protocol: 6 Service Flags: 0x20066 Protocol Chain Length: 1

Winsock Catalog Provider Entry

Entry Type: Base Service Provider Description: MSAFD Tcpip [UDP/IPv6] Provider ID: {F9EAB0C0-26D4-11D0-BBBF-00AA006C34E4} Provider Path: %SystemRoot%\system32\mswsock.dll Catalog Entry ID: 1005 Version: 2 Address Family: 23 Max Address Length: 28 Min Address Length: 28 Socket Type: 2 Protocol: 17 Service Flags: 0x20609 Protocol Chain Length: 1

Winsock Catalog Provider Entry

Entry Type: Base Service Provider Description: MSAFD Tcpip [RAW/IPv6] Provider ID: {F9EAB0C0-26D4-11D0-BBBF-00AA006C34E4} Provider Path: %SystemRoot%\system32\mswsock.dll Catalog Entry ID: 1006 Version: 2 Address Family: 23 Max Address Length: 28 Min Address Length: 28 Socket Type: 3 Protocol: 0 Service Flags: 0x20609 Protocol Chain Length: 1

Winsock Catalog Provider Entry

Entry Type: Base Service Provider Description: RSVP TCPv6 Service Provider Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A} Provider Path: %SystemRoot%\system32\mswsock.dll Catalog Entry ID: 1007 Version: 2 Address Family: 23 Max Address Length: 28 Min Address Length: 28 Socket Type: 1 Protocol: 6 Service Flags: 0x22066 Protocol Chain Length: 1

Winsock Catalog Provider Entry

Entry Type: Base Service Provider Description: RSVP TCP Service Provider Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A} Provider Path: %SystemRoot%\system32\mswsock.dll Catalog Entry ID: 1008 Version: 2 Address Family: 2 Max Address Length: 16 Min Address Length: 16 Socket Type: 1 Protocol: 6 Service Flags: 0x22066 Protocol Chain Length: 1

Winsock Catalog Provider Entry

Entry Type: Base Service Provider Description: RSVP UDPv6 Service Provider Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A} Provider Path: %SystemRoot%\system32\mswsock.dll Catalog Entry ID: 1009 Version: 2 Address Family: 23 Max Address Length: 28 Min Address Length: 28 Socket Type: 2 Protocol: 17 Service Flags: 0x22609 Protocol Chain Length: 1

Winsock Catalog Provider Entry

Entry Type: Base Service Provider Description: RSVP UDP Service Provider Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A} Provider Path: %SystemRoot%\system32\mswsock.dll Catalog Entry ID: 1010 Version: 2 Address Family: 2 Max Address Length: 16 Min Address Length: 16 Socket Type: 2 Protocol: 17 Service Flags: 0x22609 Protocol Chain Length: 1

Winsock Catalog Provider Entry

Entry Type: Base Service Provider Description: MSAFD RfComm [Bluetooth] Provider ID: {9FC48064-7298-43E4-B7BD-181F2089792A} Provider Path: %SystemRoot%\system32\mswsock.dll Catalog Entry ID: 1011 Version: 2 Address Family: 32 Max Address Length: 30 Min Address Length: 30 Socket Type: 1 Protocol: 3 Service Flags: 0x20026 Protocol Chain Length: 1

Winsock Catalog Provider Entry

Entry Type: Layered Service Provider Description: LavasoftLSP Provider ID: {2B611370-2190-4059-9AF8-5BC0F58FB742} Provider Path: C:\Windows\system32\LavasoftTcpService.dll Catalog Entry ID: 1012 Version: 2 Address Family: 2 Max Address Length: 16 Min Address Length: 16 Socket Type: 0 Protocol: 0 Service Flags: 0x66 Protocol Chain Length: 0

Name Space Provider Entry

Description: E-mail Naming Shim Provider Provider ID: {964ACBA2-B2BC-40EB-8C6A-A6DB40161CAE} Name Space: 37 Active: 1 Version: 0

Name Space Provider Entry

Description: PNRP Cloud Namespace Provider Provider ID: {03FE89CE-766D-4976-B9C1-BB9BC42C7B4D} Name Space: 39 Active: 1 Version: 0

Name Space Provider Entry

Description: PNRP Name Namespace Provider Provider ID: {03FE89CD-766D-4976-B9C1-BB9BC42C7B4D} Name Space: 38 Active: 1 Version: 0

Name Space Provider Entry

Description: Network Location Awareness Legacy (NLAv1) Namespace Provider ID: {6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83} Name Space: 15 Active: 1 Version: 0

Name Space Provider Entry

Description: Tcpip Provider ID: {22059D40-7E9E-11CF-AE5A-00AA00A7112B} Name Space: 12 Active: 1 Version: 0

Name Space Provider Entry

Description: NTDS Provider ID: {3B2637EE-E580-11CF-A555-00C04FD8D4AC} Name Space: 32 Active: 1 Version: 0

Name Space Provider Entry

Description: Bluetooth Namespace Provider ID: {06AA63E0-7D60-41FF-AFB2-3EE6D2D9392D} Name Space: 16 Active: 1 Version: 0

this is out put for "netsh WinSock Show Catalog"

[zanderz]

Thanks for that list, it shows LavaSoft with service flags lacking 0x2000, just like the Microsoft support article. Very curious whether the test build works on that person's machine - meanwhile I can try installing Lavasoft on a VM.

[sohailaftab]

@zanderz https://prerelease.keybase.io/windows/Keybase_2.10.0-20181030143356%2B2d20c80198.amd64.msi

nothing happened by installing this build too it just stuck on first screen https://www.screencast.com/t/ugmOto8ML8Ui

also i am using web companion i have tried by closing that app too

[zanderz]

that's too bad. Can you do another log send with that test build? Thanks.

[sohailaftab]

here is new id for test build log d442783b8bc1e1ee0628e31c

[zanderz]

I installed adaware web companion, but I don't have any winsock providers matching the description. Which Lavasoft (or adaware I guess it's called now) product do you have exactly, so I can try to reproduce?

[sohailaftab]

it's adware web companion https://www.screencast.com/t/4rwrvk15LV8

[zanderz]

Ah, @sohailaftab @DonaldKBrown, I took another look at your most recent logs and it looks like the crasher is gone after all. It looks like the test version was installed just after 3pm, and no crash in those logs! Can you reboot that machine and see if Keybase comes up after all? And send another log if not? There is something else going on now.

[sohailaftab]

@zanderz no affect of rebooting too. new log id = " 2f6d2f8606a3b6f7fc2ae71c"

[zanderz]

how about, at the command line, keybase -d version ? keybase status? keybase -d status? Though this client has stopped crashing, it is still unclear why the processes don't seem to be talking to each other.

[sohailaftab]

$ keybase -d version

2018-11-01T21:57:00.381722+05:00 - [DEBU keybase globals.go:470] 001 Created Identify2Cache, max age: 5m0s
2018-11-01T21:57:00.382721+05:00 - [DEBU keybase globals.go:473] 002 Created LinkCache, max size: 4000, clean dur: 1m0s
2018-11-01T21:57:00.383722+05:00 - [DEBU keybase globals.go:475] 003 Created CardCache, max age: 5m0s
2018-11-01T21:57:00.383722+05:00 - [DEBU keybase globals.go:493] 004 made a new full self cache
2018-11-01T21:57:00.385724+05:00 - [DEBU keybase globals.go:495] 005 made a new cached UPAK loader (timeout=10m0s)
2018-11-01T21:57:00.385724+05:00 - [DEBU keybase ui.go:616] 006 Can't set GPG_TTY; discover failed
2018-11-01T21:57:00.386724+05:00 - [DEBU keybase secret_store.go:153] 007 NewSecretStoreLocked: using os-specific SecretStore
2018-11-01T21:57:00.386724+05:00 - [DEBU keybase globals.go:406] 008 Keybase CLI 2.10.0-20181030143356+2d20c80198
2018-11-01T21:57:00.387724+05:00 - [DEBU keybase globals.go:406] 009 - Built with go1.10.3
2018-11-01T21:57:00.387724+05:00 - [DEBU keybase globals.go:406] 00a - Visit https://keybase.io for more details
2018-11-01T21:57:00.402771+05:00 - [DEBU keybase main.go:208] 00b + configureProcesses
2018-11-01T21:57:00.403771+05:00 - [DEBU keybase main.go:319] 00c + configureLogging
2018-11-01T21:57:00.403771+05:00 - [DEBU keybase main.go:328] 00d Disabling log forwarding
2018-11-01T21:57:00.404772+05:00 - [DEBU keybase main.go:321] 00e - configureLogging
2018-11-01T21:57:00.404772+05:00 - [DEBU keybase main.go:210] 00f - configureProcesses -> <nil>
Client:  2.10.0-20181030143356+2d20c80198
2018-11-01T21:57:00.421787+05:00 - [DEBU keybase socket.go:65] 010 + GetSocket
2018-11-01T21:57:00.427790+05:00 - [DEBU keybase rpc.go:25] 011 - GetSocket -> ok
2018-11-01T21:57:00.428789+05:00 - [DEBU keybase socket.go:75] 012 | empty socket wrapper; need a new one
2018-11-01T21:57:01.484253+05:00 - [DEBU keybase socket.go:90] 013 | DialSocket -> ERROR: i/o timeout
2018-11-01T21:57:01.484253+05:00 - [DEBU keybase cmd_version.go:81] 014 no service running: i/o timeout
2018-11-01T21:57:01.586708+05:00 - [DEBU keybase globals.go:624] 015 GlobalContext#Shutdown(0xc042331800)
2018-11-01T21:57:01.586708+05:00 - [DEBU keybase globals.go:668] 016 exiting shutdown code=0; err=<nil>

========================================================= $ keybase status

• ERROR i/o timeout

========================================================= keybase -d status

18-11-01T21:58:34.512043+05:00 - [DEBU keybase json.go:54] 001 + loading "config" file: C:\Users\Sohail Aftab\AppData\Local\Keybase\config.json
18-11-01T21:58:34.512043+05:00 - [DEBU keybase json.go:95] 002 - successfully loaded config file
18-11-01T21:58:34.513044+05:00 - [DEBU keybase json.go:54] 003 + loading "updater config" file: C:\Users\Sohail Aftab\AppData\Local\Keybase\updater.json
18-11-01T21:58:34.513044+05:00 - [DEBU keybase json.go:95] 004 - successfully loaded updater config file
18-11-01T21:58:34.514045+05:00 - [DEBU keybase client.go:119] 005 Using special root CA for api-0.core.keybaseapi.com:  -----BEGIN CERTIFICATE----- MIIGmzCCBIOgAwIBAgIJAPzhpcIBaOeNMA0GCSqGSIb3DQEBB
AMIGPMQswCQYD...
18-11-01T21:58:34.514045+05:00 - [DEBU keybase globals.go:470] 006 Created Identify2Cache, max age: 5m0s
18-11-01T21:58:34.515045+05:00 - [DEBU keybase globals.go:473] 007 Created LinkCache, max size: 4000, clean dur: 1m0s
18-11-01T21:58:34.515045+05:00 - [DEBU keybase globals.go:475] 008 Created CardCache, max age: 5m0s
18-11-01T21:58:34.515045+05:00 - [DEBU keybase globals.go:493] 009 made a new full self cache
18-11-01T21:58:34.515045+05:00 - [DEBU keybase globals.go:495] 00a made a new cached UPAK loader (timeout=10m0s)
18-11-01T21:58:34.516046+05:00 - [DEBU keybase ui.go:616] 00b Can't set GPG_TTY; discover failed
18-11-01T21:58:34.516046+05:00 - [DEBU keybase secret_store.go:153] 00c NewSecretStoreLocked: using os-specific SecretStore
18-11-01T21:58:34.517046+05:00 - [DEBU keybase globals.go:406] 00d Keybase CLI 2.10.0-20181030143356+2d20c80198
18-11-01T21:58:34.521061+05:00 - [DEBU keybase globals.go:406] 00e - Built with go1.10.3
18-11-01T21:58:34.525091+05:00 - [DEBU keybase globals.go:406] 00f - Visit https://keybase.io for more details
18-11-01T21:58:34.529843+05:00 - [DEBU keybase main.go:208] 010 + configureProcesses
18-11-01T21:58:34.719432+05:00 - [DEBU keybase fork_server.go:91] 011 Getting flock
18-11-01T21:58:34.719432+05:00 - [DEBU keybase fullcaching.go:99] 012 Avatars.FullCachingSource: monitorAppState: starting up
18-11-01T21:58:34.720432+05:00 - [DEBU keybase fork_server.go:108] 013 The server is still up
18-11-01T21:58:34.727926+05:00 - [DEBU keybase versionfix.go:58] 014 + FixVersionClash
18-11-01T21:58:35.771140+05:00 - [DEBU keybase versionfix.go:72] 015 | Failed to DialSocket, but ignoring error: i/o timeout
18-11-01T21:58:35.786211+05:00 - [DEBU keybase versionfix.go:64] 016 - FixVersionClash -> <nil>
18-11-01T21:58:35.787210+05:00 - [DEBU keybase main.go:299] 017 | After forks; newProc=false
18-11-01T21:58:35.791211+05:00 - [DEBU keybase main.go:319] 018 + configureLogging
18-11-01T21:58:35.795214+05:00 - [DEBU keybase socket.go:65] 019 + GetSocket
18-11-01T21:58:35.798217+05:00 - [DEBU keybase rpc.go:25] 01a - GetSocket -> ok
18-11-01T21:58:35.802219+05:00 - [DEBU keybase socket.go:75] 01b | empty socket wrapper; need a new one
18-11-01T21:58:36.813743+05:00 - [DEBU keybase socket.go:90] 01c | DialSocket -> ERROR: i/o timeout
18-11-01T21:58:36.813743+05:00 - [DEBU keybase main.go:321] 01d - configureLogging
18-11-01T21:58:36.814744+05:00 - [DEBU keybase main.go:210] 01e - configureProcesses -> i/o timeout
18-11-01T21:58:36.921754+05:00 - [DEBU keybase globals.go:624] 01f GlobalContext#Shutdown(0xc042385000)
18-11-01T21:58:36.921754+05:00 - [DEBU keybase globals.go:668] 020 exiting shutdown code=0; err=<nil>
18-11-01T21:58:36.922750+05:00 - [ERRO keybase main.go:86] 021 i/o timeout

[zanderz]

wait, nvm

[sohailaftab]

first 2 commands give me this error https://www.screencast.com/t/WQrD97mAvu

[zanderz]

@sohailaftab Thanks for bearing with us and trying all those commands. I eventually was able to build a version of Keybase that does not call SetFileCompletionNotificationModes, and it hangs as you describe. Unfortunately, it is not clear what to do about this second problem. Possibly a newer version of Web Companion would help. We'll keep you posted.

[zanderz]

@sohailaftab We haven't been able to solve the second problem, I'm afraid we'll just have to remain incompatible with that version of web companion. Would it be possible to upgrade or remove it? I wasn't able to reproduce with recent versions of it.

[da-code-a]

This issue is stale and does not appear to be relevant at all anymore. I suggest a close.