Keybase Go Library, Client, Service, OS X, iOS, Android, Electron

OS: OS X Keybase Version: keybase version 1.0.15-20160401130013+78dff87

I can't seem to start kbfs, keybase ctl restart hasn't helped.

Output of keybase status:

Username:      jonreem
Logged in:     yes

Device:
    name:      laptop
    ID:        6fcca53180e3f64881ad6ee5d6f34518
    status:    active

Session:       no session
    is valid:  yes
    keys:      locked
    lksec:     not loaded

KBFS:
    status:    not running
    version:   1.0.2-20160401130057+25510ca
    log:       /Users/reem/Library/Logs/keybase.kbfs.log

Service:
    status:    running
    version:   1.0.15-20160401130013+78dff87
    log:       /Users/reem/Library/Logs/keybase.service.log

Platform Information:
    OS:        darwin
    Runtime:   go1.6
    Arch:      amd64

Client:
    version:   1.0.15-20160401130013+78dff87

Desktop app:
    status:    running
    version:   1.0.15-20160401130013+78dff87
    log:       /Users/reem/Library/Logs/Keybase.app.log

Config path:   /Users/reem/Library/Application Support/Keybase/config.json
Default user:  jonreem
Other users:

command-line client:
    keybase status [pid: 15719, version: 1.0.15-20160401130013+78dff87]

desktop:
    /Applications/Keybase.app/Contents/Frameworks/Keybase Helper.app/Contents/MacOS/Keybase Helper --type=renderer --no-sandbox --lang=en-US --node-integration=true --num-raster-threads=4 --enable-zero-copy --enable-gpu-memory-buffer-compositor-resources --content-image-texture-target=3553,3553,3553,3553,3553,34037,3553,3553,3553,3553,34037,3553,34037,34037 --video-image-texture-target=34037 --channel=12348.1.186385196 [pid: 12354, version: 1.0.15-20160401130013+78dff87, description: Menubar]
    /Applications/Keybase.app/Contents/Frameworks/Keybase Helper.app/Contents/MacOS/Keybase Helper --type=renderer --no-sandbox --lang=en-US --node-integration=true --num-raster-threads=4 --enable-zero-copy --enable-gpu-memory-buffer-compositor-resources --content-image-texture-target=3553,3553,3553,3553,3553,34037,3553,3553,3553,3553,34037,3553,34037,34037 --video-image-texture-target=34037 --channel=12348.2.1751919681 [pid: 12355, version: 1.0.15-20160401130013+78dff87, description: Main Renderer]
    /Applications/Keybase.app/Contents/MacOS/Electron -psn_0_25102319 [pid: 12348, version: 1.0.15-20160401130013+78dff87, description: Main Thread]

Output of keybase launchd list:

keybase.service: Running (pid=14800) [Keybase]
keybase.kbfs: Not Running exit=2 [KBFS]

keybase log send id: ec6a9aea3bde5eb2c5ef791c

After upgrading to macOS Big Sur 11.0.1, Keybase client is not working with Finder, and enabling does not work. In main app, select Files tab; "Enable Keybase in Finder?" should show at the top. Click to accept "I understand that closed source...", and push "Yes, enable" button.

Result: After working for a few seconds, nothing changes and "Yes, enable" button is enabled again. Attempting to navigate to any keybase managed files gives permission denied.

Keybase client for macOS 5.5.0-20200526170801+139bb348af (installed via brew). kbfuse version is 10.11 with symlinks for higher versions.

❯ ll /Library/Filesystems/kbfuse.fs/Contents/Extensions/
total 0
drwxr-xr-x@ 3 root  wheel    96B May 26 13:19 10.11/
lrwxr-xr-x  1 root  wheel     5B May 26 13:19 10.12@ -> 10.11
lrwxr-xr-x  1 root  wheel     5B May 26 13:19 10.13@ -> 10.11
lrwxr-xr-x  1 root  wheel     5B May 26 13:19 10.14@ -> 10.11
lrwxr-xr-x  1 root  wheel     5B May 26 13:19 10.15@ -> 10.11

On Arch Linux using GNOME 3, the GUI just displays opaque blobs of color. I suspect one of them is key unlocking, but I can't really tell.

I don't seem to be able to use kbfs either, possibly as a result of this.

Initial dialog:

When I click the icon:

my log id: c13df03ad6cf0703c6c69f1c

I have two personas online, my professional persona and my personal/family personas are kept separate online. In this real-life example, I will never associate my facebook with my github via way of keybase (i wont proof facebook and github on the same keybase account, because that then associates them).

Are my concerns common, is anyone else concerned about the same thing? Can/Will keybase support multiple personas or identities?

I experienced various unstableness on macOS Sierra GM Seed (16A319 ) as:

• Console.app
• Dropbox hangup
• iStat Menus hangup
• OS hangup on shutdown or reboot

After investigation, I found that keybase uninstall resolved the unstableness. I guess KBFS causing this issue But I can't verify that, so I file an issue here.

Cannot login to Keybase Gui on the Mac OS El Cap.

Command line does not work either, and never times out.

Keybase log send does not work either, never sends.

Just tested the new team feature with some colleagues, and an important question arose:

What is the full chat history good for if there's no search?

Is search going to be implemented any time soon?

I have three devices (linux box, mac, and android) connected to my account. I can't access my /keybase/private directory from any of them. On each, I get: ERROR This device does not yet have read access to directory /keybase/private/d1rewolf, log into Keybase from one of your other devices to grant access: <redacted> is not readable by d1rewolf (uid: <redacted>) github.com/keybase/kbfs/libkbfs.isReadableOrError /Users/build/go/src/github.com/keybase/kbfs/libkbfs/md_util.go:74 github.com/keybase/kbfs/libkbfs.(*KBFSOpsStandard).getMaybeCreateRootNode /Users/build/go/src/github.com/keybase/kbfs/libkbfs/kbfs_ops.go:600 github.com/keybase/kbfs/libkbfs.(*KBFSOpsStandard).GetOrCreateRootNode /Users/build/go/src/github.com/keybase/kbfs/libkbfs/kbfs_ops.go:641 github.com/keybase/kbfs/simplefs.(*SimpleFS).getRemoteRootNode /Users/build/go/src/github.com/keybase/kbfs/simplefs/simplefs.go:737 github.com/keybase/kbfs/simplefs.(*SimpleFS).getRemoteNode /Users/build/go/src/github.com/keybase/kbfs/simplefs/simplefs.go:748 github.com/keybase/kbfs/simplefs.(*SimpleFS).SimpleFSStat /Users/build/go/src/github.com/keybase/kbfs/simplefs/simplefs.go:564 github.com/keybase/kbfs/vendor/github.com/keybase/client/go/protocol/keybase1.SimpleFSProtocol.func26 /Users/build/go/src/github.com/keybase/kbfs/vendor/github.com/keybase/client/go/protocol/keybase1/simple_fs.go:957 github.com/keybase/kbfs/vendor/github.com/keybase/go-framed-msgpack-rpc/rpc.(*callRequest).Serve /Users/build/go/src/github.com/keybase/kbfs/vendor/github.com/keybase/go-framed-msgpack-rpc/rpc/request.go:76 github.com/keybase/kbfs/vendor/github.com/keybase/go-framed-msgpack-rpc/rpc.(*receiveHandler).handleReceiveDispatch.func1 /Users/build/go/src/github.com/keybase/kbfs/vendor/github.com/keybase/go-framed-msgpack-rpc/rpc/receiver.go:121 runtime.goexit /usr/local/Cellar/go/1.9/libexec/src/runtime/asm_amd64.s:2337

What can I do to fix this?

my workflow:

• saw Marco set me up on Google Play
• Installed Keybase app onto phone
• logged into my account via keybase login (PGP)
• named my device Galaxy_S8
• device appeared to freeze; set it down for a bit in case it was syncing
• looked at my conversations, I had a new one from user marcopolo; unable to read
• viewed my folders; noticed a "rekey" tag on almost all of them.
• clicked a folder; greeted with message I needed to log in from windows application or risk losing files.
• Stopped work from the phone; started up laptop
• Keybase unable to login on Laptop

my log id: ef91f102cfe877cd9b1ea11c

@maxtaco, This mainly makes sure locally stored tracks get aged out instead of lasting forever, but I'm unsure whether this covers the intent of 2447. Would appreciate at least a first look at this draft.

Hey,

I'm currently trying to login and KB is asking me to provision my current device...trouble is my current device is already provisioned...it's even on the list of devices I can pick from.

I've sent in a log: 8be1f1c6b2d097bde8fee61c

--Brian

I had to use the disable-cert-pinning option because the machine is behind an aggressive firewall which basically MITM-attacks all traffic. The GUI app seems to work, however as soon as I tried to cd more than two levels "deep" in a KBFS team folder, it started throwing "The read operation took too long and failed" errors over and over again.

Log ID: 700ae48f71c75cfd13c49e1c

Running 6.0.3-20221212202006+608e46df72 on macOS 13.1.

The goal of this MR is to make recycling of messages faster. In the old way we had a top level 'generic' component which then split up into various children, all with keys inside. This makes it very hard to save any time when recycling. Instead we

• Make each type their own and split the shared stuff into helpers

• Reduce the plumbing of conversationIDKey / ordinal, and useContext

• Memo children and make them more recyclable (LeftSide RightSide etc)

• Make a new messageTypeMap which just maps ordinals to types so we can not thrash as much

• [ ] fix measure

• [ ] maybe username needs orange line

Ever since Android 13, when someone is typing it the same channel you have currently opened, the app has a good chance of crashing. It will hang and it must be killed to be restarted. This happens very often, maybe every 10 seconds. Multiple users reporting this in the app reviews on the play store. Looking at the issues here, I couldn't identify a related issue. Anyone has an idea about what might be causing this?

Using a stock pixel 5, SwiftKey keyboard

Thanks

output of %localappdata%\Keybase\Gui\Keybase.exe in cmd is Version: 6.0.1-20220609140211+0fc9feea3d requestWindowsStartService: starting keybase.exe Not connected - starting keybase expected path to keybase binaries is C:\Users\sfmor\AppData\Local\Keybase