Skip to content
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

Update linux.md #5872

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update linux.md #5872

wants to merge 1 commit into from

Conversation

KloolK
Copy link

@KloolK KloolK commented Jul 30, 2024

Add command to set correct permission for /usr/share/keyrings/wezterm-fury.gpg

Following the instructions, the file was created with 640 on my machine. This lead to an error with sudo apt update:

Get:12 https://apt.fury.io/wez * InRelease
Err:12 https://apt.fury.io/wez * InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D7BA31CF90C4B319
[...]
W: GPG error: https://apt.fury.io/wez * InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D7BA31CF90C4B319
E: The repository 'https://apt.fury.io/wez * InRelease' is not signed.

Add command to set correct permission for `/usr/share/keyrings/wezterm-fury.gpg`
@wez
Copy link
Owner

wez commented Jul 30, 2024

Thanks, but I'm pretty sure that you need to run sudo apt update instead.

@KloolK
Copy link
Author

KloolK commented Jul 30, 2024

I did run it as root, I just forgot it in my description above (changed now).

All other *.gpg files in /usr/share/keyrings have 644. Changing it manually back to 640 will make the error occur again.

On my system, the umask for root is 027, causing the file to be created with 640 instead of 644. I don't know if this is the default for Ubuntu, but I'd be surprised if I'm the only one having this configuration.

Maybe a hint is more appropriate then making it part of the default instructions? I just want to spare others the time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants