Re: bug#67978: 29.1; ERC 5.5.0.29.1: Unnecessary .authinfo.gpg decryption causes connection failure to irc.libera.chat
"J.P." <[email protected]> Tue, 21 Oct 2025 18:30:47 -0700
| Newsgroups | gmane.emacs.erc.general |
|---|---|
| Message-ID | <[email protected]> |
"J.P." <[email protected]> writes: > Hi Jake, > > Jake <[email protected]> writes: > >>> And is there anything relevant recorded in the >>> "*Messages*" buffer? >> Decrypting /home/jake/.authinfo.gpg...done >> epa-file-insert-file-contents: Opening input file: Decryption failed, >> , No secret key > > That's helpful, thanks. I believe what's happening in your case is that > your Gnome Keyring's GPG integration needs attention, hopefully only in > the configuration department. If libsecret has been authorized to store > the key you're being prompted to provide a passphrase for, it should > show up when you query the service over DBus. But before messing with > that, make sure to tick the appropriate "remember this" box the next > time you provide your passphrase in a popup dialog. From then on, you > shouldn't be prompted, though you may have to log out and back in for it > to stick [1]. > > In any case, I think ERC users should be allowed to ignore errors > signaled by its default `auth-source' queries, so I've added a prompt > that asks whether to proceed anyway when one occurs. It's preceded by an > annoying warning, which you can customize away in the usual fashion, in > this case by setting the option `warning-suppress-types' or > `warning-suppress-log-types' to include the list (erc auth-source). > > Feel free to try out the changes on HEAD [2] and report back. If that's > too much trouble, you can wait for ERC 5.6, which should be released in > the coming weeks. Closing this because it appears action was taken without any subsequent feedback. If the issue remains, feel free to reopen. Thanks.