Installation process can't find gpg if it's in a non-standard place
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
When I log in, I get an error
There was an error provisioning
Unknown error: GPG is unavailable on this device.
This is and isn't true. gpg is on the machine, but not in a standard place (I have a couple of different versions installed, and none of them are in /usr/bin). It might be necessary to add a ‘where is gpg located?’ step to the login or first-install process.
my log id: b4895dd17b860cd3c0b01d1c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the login or first-install provisioning path that reports “GPG is unavailable,” using log id b4895dd17b860cd3c0b01d1c as context. Determine how GPG is located on the device and what the process currently considers a standard location. Done means installations with GPG outside /usr/bin can complete provisioning and still report a clear error when it is genuinely unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100