LeoIannacone/goopg

Not verifying or signing any more

Closed this issue · 3 comments

asgrim commented

A long time ago this used to work for me; but I noticed a while ago it'd broken. Only just got around to reporting it, so sorry; I can't remember anything specific that may've triggered breaking :(

Reproduce

  • I'm using Chrome 49 on Ubuntu Wily.
  • De-authorise Goopg from my Google Account
  • Removed ~/.cache/goopg directory
  • Remove and re-add the extension
  • apt-get purge goopg-chrome then apt-get install goopg-chrome
  • Open Gmail
  • View an email with a signature
  • Try to send an email with "Sign and Send" button

What I expect to happen

  • When viewing an email with a signature, I expect it to show the green verification banner.
  • When trying to send a signed email, I expect it to think for a moment to generate the signature, then send the email

What actually happens

  • When viewing the email, I do not see the banner, even though a signature.asc is present as an attachment.
  • When trying to send a signed email, I click the "Sign and Send" button which changes to say "Sending", but stays that way.

Additional information

Since re-installing both the extension and the goopg-chrome package (and deleting ~/.cache/goopg directory), no logs re-appear. Before deleting this, the tail looked like this:

2016-04-06 18:26:46,086:ERROR:chrome-main:Error while reading stdin: "unpack requires a string argument of length 4" - Exit.
2016-04-06 22:02:33,294:ERROR:chrome-main:Error while reading stdin: "unpack requires a string argument of length 4" - Exit.
2016-04-07 18:44:15,682:ERROR:chrome-main:Error while reading stdin: "unpack requires a string argument of length 4" - Exit.
2016-04-07 20:26:55,636:ERROR:chrome-main:Error while reading stdin: "unpack requires a string argument of length 4" - Exit.
2016-04-08 09:47:54,493:ERROR:chrome-main:Error while reading stdin: "unpack requires a string argument of length 4" - Exit.
2016-04-08 15:33:23,783:ERROR:chrome-main:Error while reading stdin: "unpack requires a string argument of length 4" - Exit.
2016-04-08 19:24:45,230:ERROR:chrome-main:Error while reading stdin: "unpack requires a string argument of length 4" - Exit.
2016-04-11 12:24:24,092:ERROR:chrome-main:Error while reading stdin: "unpack requires a string argument of length 4" - Exit.
2016-04-11 22:50:45,182:ERROR:chrome-main:Error while reading stdin: "unpack requires a string argument of length 4" - Exit.
2016-04-14 10:42:10,335:ERROR:chrome-main:Error while reading stdin: "unpack requires a string argument of length 4" - Exit.

This may well have been the last time I saw it working (April)...

In the JS console in Gmail, when loading I can see:

Connecting to web port... goopg-web-chrome-port.js:11

but no other useful output seems to appear.

LeoIannacone commented

I trying to investigate this issue. Unfortunately I'm no longer on ubuntu Wily, I updated to Xenial which now ships python-oauth2client 2.0.1-1 and breaks goopg host app.

I will fix goopg asap and only for the newer version of Ubuntu.

  • 👍1
LeoIannacone commented

Hi, I just release v0.3.0 (for Ubuntu Xenial) which should fix this.

So, I'm closing this for now, please reopen if you have the same problem.

Thanks for reporting!

asgrim commented

Looks like this is working now, thank you :)