Can't install due to NO_PUBKEY

[sailbird]

Using a supported version?

• I have searched searched open and closed issues for duplicates.
• I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

I followed your instructions exactly but Linux says that your archive is unsigned. This is likely because it was unable to fetch your public key. I'm sure this isn't a local internet problem.

Steps to reproduce

1. cat signal-desktop-keyring.gpg | sudo tee /usr/share/keyrings/signal-desktop-keyring.gpg

(No output.)

2. echo 'deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main' | sudo tee /etc/apt/sources.list.d/signal-xenial.list

Output:

deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main

3. sudo apt update && sudo apt install signal-desktop

Output:
...
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D980A17457F6FB06
...
W: GPG error: https://updates.signal.org/desktop/apt xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D980A17457F6FB06
E: The repository 'https://updates.signal.org/desktop/apt xenial InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Expected result

Obvious

Actual result

As shown above

Screenshots

No response

Signal version

latest

Operating system

Linux

Version of Signal on your phone

No response

Link to debug log

No response

[indutny-signal]

Thank you for reporting this! What distribution of linux are you on and what CPU architecture?

[sailbird]

@indutny-signal I tried it again just now. Seems like the problem was that wget (before step 1 above) was silently failing (twice!) last time. Now it shows the progress bar as it downloads the key file. Everything after that worked as expected. Definitely wasn't my internet problem because it was working fine both times. Maybe adding "--verbose" or something like that would prevent this sort of confusion in the future.