Runtime error trying to login on Ubuntu

mh_nerdwallet

Hello,
I've tried to install the CLI on a Linux Ubuntu machine and when I log in with a username/password (we have duo enabled on our account), it spits out a runtime error:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x804a32c]

goroutine 1 [running]:
runtime/internal/atomic.Xadd64(0xa58049c, 0x1, 0x0, 0x1, 0xa5761b0)
/usr/local/go/src/runtime/internal/atomic/asm_386.s:105 +0xc
go.1password.io/op/b5/model.(Session).NextRequestID(0xa580460, 0xa5761b0, 0x1)
/go/src/go.1password.io/op/b5/model/session.go:52 +0x36
go.1password.io/op/b5/api/request.Init(0xa580460, 0x1, 0xa57e440, 0x33, 0x8400940, 0xa483b40, 0x33, 0x0, 0x0)
/go/src/go.1password.io/op/b5/api/request/request.go:213 +0xf8
go.1password.io/op/b5/api/auth.SRPVerify(0xa4962c0, 0x20, 0xa498600, 0xa66e5a0, 0x20, 0x20, 0xa498540, 0x0, 0x0, 0x2)
/go/src/go.1password.io/op/b5/api/auth/auth.go:112 +0x28f
go.1password.io/op/b5/api.SigninWithCredentials(0x84dfd20, 0xa49a2a0, 0xa4965a0, 0x1a, 0x843b172, 0xd, 0x843727d, 0x7, 0xa494660, 0x8, ...)
/go/src/go.1password.io/op/b5/api/signin.go:144 +0x504
go.1password.io/op/command.(SigninCommand).Run(0xa480810, 0xa48ab00, 0x2, 0x2, 0xa48a260)
/go/src/go.1password.io/op/command/signin.go:66 +0x19a
go.1password.io/op/vendor/github.com/mitchellh/cli.(*CLI).Run(0xa48c140, 0x12, 0x0, 0x1)
/go/src/go.1password.io/op/vendor/github.com/mitchellh/cli/cli.go:255 +0x1ce
main.run(0x0, 0x0, 0x0)
/go/src/go.1password.io/op/main.go:47 +0xa2
main.main()
/go/src/go.1password.io/op/main.go:29 +0x1a

Here's the info from uname:
Linux 4.4.0-145-generic #171-Ubuntu SMP Tue Mar 26 12:43:40 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Anybody seen this before?

---

1Password Version: 0.6.1
Extension Version: Not Provided
OS Version: Linux
Sync Type: Not Provided

felix_1p

Hi @mh_nerdwallet!

We are aware of an issue with the CLI on 386 and ARM platforms (see this post) and are currently working on a fix.

While you seem to be on x86_64, which should work, it also looks like you may be running the 386 build of the CLI. I'd suggest to download the amd64 build and give it a try.

Please let me know if that works.

mh_nerdwallet

Thanks Felix - I'll give the 64 bit build a try and see if it works.

ag_ana

@mh_nerdwallet, on behalf of felix_1p, you are very welcome!

We are looking forward to hearing back from you!

Have a wonderful day :)

cohix

@mh_nerdwallet Version 0.6.2 was just released and should fix this issue!