Re: Almost all gpg2 operations hang after upgrade to stretch/testing
Nicolas George <george@nsup.org> writes:
> Le septidi 17 germinal, an CCXXV, Nathanael Schweers a écrit :
>> connect(6, {sa_family=AF_UNIX,
>> sun_path="/run/user/1000/gnupg/S.gpg-agent"}, 34) = 0
>> read(6,
>>
>> It seems to me that strace shouldn’t just stop in the middle of an
>> argument list, but I might be wrong.
>
> It is perfectly normal. strace will print the contents of the buffer
> that has just been read, but for that, it must wait that the syscall
> finished.
>
> Thus, we know that the problem is the agent not responding at all to the
> client. stracing the agent may give more information.
Ah, thanks a lot for that tip! I went again and looked how the agent is
started, as it immediately respawned whenever I sent SIGTERM to it.
Turns out, I still had a systemd user service, which started the agent
using environment variables and the like. As soon as I had removed that
service and performed a reboot (I’m not sure what exactly would have to
be restarted), everything worked!
At any rate, you really saved my day, thank you so much!
>
>> 5307 pts/4 S+ 0:00 grep --color=auto --exclude-dir=.bzr
>> --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg
>> --exclude-dir=.svn -i gpg
>
> As a side note, you might be interested to know "git grep"; it greps
> tracked files but not the repository, and even works when working out of
> tree.
Those seem to be the default arguments for grep or something. I use
oh-my-zsh, it may come from there. Also, I know about git grep, yet
hardly use it. Maybe I should ;)
Regards,
Nathanael Schweers
Reply to: