New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setup fails: There is no assurance this key belongs to the named user #756

Closed
djc opened this Issue Jul 5, 2014 · 4 comments

Comments

Projects
None yet
3 participants
@djc

djc commented Jul 5, 2014

I removed a left-over .mailpile dir from when I tried alpha 1, and ran mp setup:

gpg: 2F0FDB12: There is no assurance this key belongs to the named user        
gpg: [stdin]: encryption failed: Unusable public key
Traceback (most recent call last):
  File "/home/djc/src/mailpile/mailpile/commands.py", line 430, in _run_sync
    return self._finishing(command, command(self, *args, **kwargs))
  File "/home/djc/src/mailpile/mailpile/commands.py", line 427, in command
    return self.command(*args, **kwargs)
  File "/home/djc/src/mailpile/mailpile/plugins/migrate.py", line 280, in command
    self._background_save(config=True)
  File "/home/djc/src/mailpile/mailpile/commands.py", line 252, in _background_save
    aut(session, 'Save config', cfg.save)
  File "/home/djc/src/mailpile/mailpile/workers.py", line 276, in add_unique_task
    return self.add_task(session, name, task)
  File "/home/djc/src/mailpile/mailpile/workers.py", line 271, in add_task
    return task()
  File "/home/djc/src/mailpile/mailpile/config.py", line 1083, in save
    self._unlocked_save(*args, **kwargs)
  File "/home/djc/src/mailpile/mailpile/config.py", line 1091, in _unlocked_save
    fd.write(self.as_config_bytes(private=True))
  File "/home/djc/src/mailpile/mailpile/util.py", line 393, in write
    self.fd.write(data)
IOError: [Errno 32] Broken pipe
@bnvk

This comment has been minimized.

Show comment
Hide comment
@bnvk

bnvk Aug 8, 2014

Contributor

This is most likely a threads / locks issue. We're aware of this IOError and are working on it this weekend / before beta! Thanks for reporting tho!

Contributor

bnvk commented Aug 8, 2014

This is most likely a threads / locks issue. We're aware of this IOError and are working on it this weekend / before beta! Thanks for reporting tho!

@bnvk

This comment has been minimized.

Show comment
Hide comment
@bnvk

bnvk Aug 8, 2014

Contributor

And @rschulman brought up this related GPG bug, but it should be handled better by us!

Contributor

bnvk commented Aug 8, 2014

And @rschulman brought up this related GPG bug, but it should be handled better by us!

@djc

This comment has been minimized.

Show comment
Hide comment
@djc

djc Aug 8, 2014

Thanks for taking a look. :) I also ran into similar issues with alpha 1, so it's been rather frustrating so far.

djc commented Aug 8, 2014

Thanks for taking a look. :) I also ran into similar issues with alpha 1, so it's been rather frustrating so far.

@BjarniRunar

This comment has been minimized.

Show comment
Hide comment
@BjarniRunar

BjarniRunar Aug 8, 2018

Member

This is obsolete now. Thank you all for the report and discussions.

Member

BjarniRunar commented Aug 8, 2018

This is obsolete now. Thank you all for the report and discussions.

@BjarniRunar BjarniRunar closed this Aug 8, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment