In the mean time, you could put something along the lines of: {CmdCalls ; } 2>&1 | grep -v -e "^gpg: problem with fast path key listing: Forbidden - ignored$" or something, to keep that output out of your stderr stream.
If something else unexpected displays, you'll get more issues, but then you probably want to know if / when / should that happen. If you add --quiet now, even when the change below happens later, your script above won't need to change again. On Fri, Apr 5, 2024 at 5:01 AM Werner Koch via Gnupg-users <gnupg-users_at_gnupg.org_omcuj...@duck.com> wrote: > > Hi! > > > gpg: problem with fast path key listing: Forbidden - ignored > > I'll suppress that message in --quiet mode for the next release. > > ... On Fri, Apr 5, 2024 at 11:24 AM Mike S wrote: > > Hello, > > is there a way to (re-)enable password storage and retrieval via secret > service under KDE? > > The allow_external_password_cache option was disabled in this ticket: > https://dev.gnupg.org/rPefb6de7fb2c15c1e31349b80fa7c8c1d4694c6cf > > But for me it would be useful to override this setting, I'm not using KWallet > as my secret-service (I'm using KeePassXC), and are not affected by the > possible deadlock. > I thought about somehow changing the XDG_SESSION_DESKTOP env variable that > pinentry-gtk-2 sees, but I don't think I can do that (because gpg-agent is > launching pinentry?) > > > Currently I downgraded the pinentry version. > My problem is, that I sign my git commits and now I have to write my > passphrase every time I commit. > (With version 1.2.1-3 it takes the passphrase out of my KeePass database) _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users