jesseduffield / jesseduffield/lazygit
Regression in lazygit behavior for gpg/ssh prompts with pinentry
- Dominant language
- Go
- Stars
- 82.4k
- Forks
- 3k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 19
Description
**Describe the bug**
This is really a reopening of a previously fixed bug #3308 and pr #3478
**To Reproduce**
Steps to reproduce the behavior:
1. Configure your environment for using gpg as an ssh-agent
2. Reset the agent so it needs to prompt for the gpg password. "gpg-connect-agent reloadagent /bye"
3. Run lazygit, watch the screen go crazy
**Screenshots**
Same screen shots as in bug #3308
**Version info:**
Lazygit 0.42 - First fixed with PR#3478
Lazygit 0.44.1 - Still working
Lazygit 0.45.2 - Semi working, the initial prompt looks correct but upon return to the lazygit ui things are messed up
Lazygit 0.46+ - Completely messed up from first launch of lazygit
**Additional context**
It seems as though pinentry and lazygit are fighting over the screen and keyboard inputs. Like keystrokes are being sent to BOTH of them, as BOTH of them are attempting to draw on the screen simultaneously.
Contributor guide
Assessment
This issue has not been assessed yet.