From: vivlim <vivlim@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: proton-bridge: 1.6.3 build from source
Date: Thu, 04 Mar 2021 22:17:56 +0100 [thread overview]
Message-ID: <20210304211756.11zIAtL0pVPgPIMI3UTpXaSSjcaeWOCDgRgUwseD-bQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28839@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3745 bytes --]
New comment by vivlim on void-packages repository
https://github.com/void-linux/void-packages/pull/28839#issuecomment-790949699
Comment:
I tried to build the package but got the below error, clearing hostdir/binpkgs fixed it.
```
=> go-qt5-0.0.20200904_1: removing autodeps, please wait...
=> go-qt5-0.0.20200904_1: cleaning build directory...
=> go-qt5: removing files from destdir...
=> protonmail-bridge-1.6.3_1: installing host dependencies: desktop-file-utils-0.26_1 pkg-config-0.29.2_2 go-1.15.8_1 go-qt5-0.0.20200904_1 ...
=> protonmail-bridge-1.6.3_1: installing target dependencies: qt5-devel-5.15.2_2 qt5-declarative-devel-5.15.2_2 qt5-webview-devel-5.15.2_1 qt5-webengine-devel-5.15.2_2 libsecret-devel-0.20.4_1 qt5-quickcontrols2-devel-5.15.2_2 ...
=> protonmail-bridge-1.6.3_1: removing autodeps, please wait...
=> ERROR: protonmail-bridge-1.6.3_1: failed to install 'qt5-devel-5.15.2_2' dependency! (error 19)
libcrypto46-3.1.4_1 in transaction breaks installed pkg `libressl-3.1.5_2'
libssl48-3.1.4_1 in transaction breaks installed pkg `libressl-3.1.5_2'
libtls20-3.1.4_1 in transaction breaks installed pkg `libressl-3.1.5_2'
Transaction aborted due to unresolved dependencies.
=> ERROR: Please see above for the real error, exiting...
```
When I launched the bridge, I was no longer signed in, during previous upgrades I did not have to sign in again. Then when I tried to sign in, I got this:
I tried clearing the keychain (Settings > Clear Keychain) but that didn't help. I also deleted ~/.cache/protonmail, ~/.cache/ProtonMail Bridge, and .config/protonmail, but it is still broken for me.
I was able to get more detailed errors from my log in ~/.cache/protonmail/bridge/logs/:
```
time="Mar 4 13:11:42.745" level=info msg="No active accounts" pkg=frontend-qt
time="Mar 4 13:11:42.769" level=info msg="No active accounts" pkg=frontend-qt
time="Mar 4 13:11:57.565" level=info msg="Updating token" userID=anonymous-4
time="Mar 4 13:11:57.565" level=info msg="User not available for auth update" pkg=users userID=anonymous-4
time="Mar 4 13:12:07.078" level=info msg="Got API user" pkg=users
time="Mar 4 13:12:07.078" level=info msg="Setting token because it is currently unset" userID="(redacted)"
time="Mar 4 13:12:07.421" level=info msg="Updating token" userID="(redacted)"
time="Mar 4 13:12:07.422" level=info msg="User not available for auth update" pkg=users userID="(redacted)"
time="Mar 4 13:12:08.656" level=error msg="Could not get credentials from native keychain" error="no usernames for protonmail/bridge/users/(redacted)" pkg=credentials user="(redacted)"
time="Mar 4 13:12:08.656" level=info msg="Generating credentials for new user" pkg=credentials
time="Mar 4 13:12:08.687" level=error msg="Failed to add new user" error="failed to add user to credentials store: exit status 1: gpg: (redacted): There is no assurance this key belongs to the named user\ngpg: [stdin]: encryption failed: Unusable public key\nPassword encryption aborted.\n" pkg=users
time="Mar 4 13:12:08.990" level=warning msg="request DELETE /auth NOT OK: 401 Unauthorized" pkg=pmapi userID=anonymous-4
time="Mar 4 13:12:08.990" level=error msg="Failed to clear login session after unlock" error="Invalid access token" pkg=users
time="Mar 4 13:12:08.990" level=error msg="Login was unsuccessful" error="failed to add user to credentials store: exit status 1: gpg: (redacted): There is no assurance this key belongs to the named user\ngpg: [stdin]: encryption failed: Unusable public key\nPassword encryption aborted.\n" pkg=frontend-qt
```
Any ideas how I can fix this?
next prev parent reply other threads:[~2021-03-04 21:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 14:53 [PR PATCH] " sgn
2021-02-18 14:57 ` sgn
2021-02-19 16:34 ` [PR PATCH] [Updated] " sgn
2021-02-19 17:21 ` sgn
2021-02-19 18:26 ` sgn
2021-02-19 18:30 ` sgn
2021-02-19 23:50 ` [PR PATCH] [Updated] " sgn
2021-02-19 23:58 ` sgn
2021-02-21 23:20 ` ericonr
2021-02-21 23:52 ` jbenden
2021-02-22 0:05 ` ericonr
2021-02-22 0:53 ` sgn
2021-02-22 6:56 ` jbenden
2021-02-23 0:59 ` cinerea0
2021-03-04 21:17 ` vivlim [this message]
2021-03-07 20:52 ` jbenden
2021-03-07 23:10 ` vivlim
2021-03-08 0:28 ` sgn
2021-03-08 7:39 ` vivlim
2021-05-11 21:02 ` cinerea0
2021-05-11 23:21 ` sgn
2022-05-04 2:15 ` github-actions
2022-05-19 2:15 ` [PR PATCH] [Closed]: " github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210304211756.11zIAtL0pVPgPIMI3UTpXaSSjcaeWOCDgRgUwseD-bQ@z \
--to=vivlim@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).