OSX high sierra

[zeuben]

fresh install, app never starts.

my log id: ae52adba90d44b1258fbaa1c

[maxtaco]

It is a permissions problem? Look elsewhere in this issue tracker for LaunchAgents

[zeuben]

tried a bunch of things including re-installing + restarting and also installing MacFuse, nothing worked. App launches and shows loading screen -- forever.

Running OSX High Sierra 10.13 MacBook Pro 15" 2017

[maxtaco]

@zeuben I'm not sure, but I worry your homedir name is too long and that's tripping up Electron's unix socket dial. We'd need some more debugging to figure it out.

Can you try to start keybase by hand and tell me what happens?

keybase service & (keybase id max && keybase log send)

Does that work?

[favoretti]

My log id here as well: 8deca0bb3478d96a20d82c1c

[favoretti]

Ah, read through, for me permission issue is confirmed. After fixing and restarting it works.

[enjine]

Yes, i do in fact have a super-long home directory name:

$ keybase service & (keybase id max && keybase log send)
[1] 19988
▶ WARNING | Changing current working directory because path for dialing is too long
▶ WARNING Unknown service type: ""
▶ WARNING | Changing current working directory because path for dialing is too long

Keybase isn't running. To start, you can run:

    open /Applications/Keybase.app

▶ ERROR There were multiple errors: dial unix keybased.sock: connect: no such file or directory; dial unix /Users/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/Library/Caches/Keybase/keybased.sock: connect: no such file or directory
33m▶ WARNING | Changing current working directory because path for binding is too long
▶ INFO | net.Listen on unix:keybased.sock
1337;RemoteHost=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@enjine.local▶ WARNING PushHandler: unable to create push service client: no UID; probably not logged in

[maxtaco]

@enjine what was your log ID after that attempt?

[maxtaco]

cc: @oconnor663 who just added that warning. that warning probably isn't fatal.

[enjine]

e7d614d47053db9442d3311c

[maxtaco]

oh @enjine probably you didn't give it enough time to start up.

[maxtaco]

run keybase service in one window and keybase id max in another

[enjine]

$ keybase id max
▶ WARNING | Changing current working directory because path for dialing is too long
▶ WARNING | Changing current working directory because path for dialing is too long
▶ INFO Identifying max
✔ public key fingerprint: 8EFB E2E4 DD56 B352 7363 4E8F 6052 B2AD 31A6 631C
✔ public key fingerprint: 4475 2933 0624 3408 FA59 58DC 6384 7B4B 8393 0F0C
฿  bitcoin 1BYzrCvfbn81dfiksmD1Bdgt8pgLi1SD7Z
✔ admin of DNS zone maxk.org: found TXT entry keybase-site-verification=uqzZedLr4yVILSkh6nLfctv5oxrqpp8rFLHsz-0xxy4
✔ admin of DNS zone oneshallpass.com: found TXT entry keybase-site-verification=Dld6FHUIWgetEGY0AN4c18Mh0jSc8kRt4RLi8vUakos
✔ admin of DNS zone nutflex.com: found TXT entry keybase-site-verification=S0xnyDtJlarl1KXd6Rb7NXYlUeZ-NdTU8b6Z4jCSOGA
✔ admin of keybase.io via HTTPS: https://keybase.io/.well-known/keybase.txt
✔ admin of oneshallpass.com via HTTPS: https://oneshallpass.com/.well-known/keybase.txt
✔ "maxtaco" on hackernews: https://news.ycombinator.com/user?id=maxtaco
✔ "maxtaco" on reddit: https://www.reddit.com/r/KeybaseProofs/comments/2clf9c/my_keybase_proof_redditmaxtaco_keybasemax/
✔ "maxtaco" on github: https://gist.github.com/8847250
✔ "maxtaco" on twitter: https://twitter.com/maxtaco/status/433688676975927296

[maxtaco]

yeah, so i think you have some sort of launchd problem that we haven't been able to solve in 100% of cases (most people have permissions problems). we have an upcoming release that will try to workaround it. if you want to do some probing on your own, looks for launchd or launchctl in this GitHub issue tracker