I've found an upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=773009
I've also devised a simple workaround:
martin@dogmeat ~ % cat /etc/rsyslog.d/20-gcr-prompter-discard.conf # gcr-prompter logs debug info to /var/log/auth.log # https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1533267 # https://bugzilla.gnome.org/show_bug.cgi?id=773009 if $programname == 'gcr-prompter' then stop
Run `sudo systemctl restart rsyslog` after creating that file, then gcr-prompter should no longer produce any logs.
I've found an upstream bug report: https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 773009
I've also devised a simple workaround:
martin@dogmeat ~ % cat /etc/rsyslog. d/20-gcr- prompter- discard. conf /bugs.launchpad .net/ubuntu/ +source/ gcr/+bug/ 1533267 /bugzilla. gnome.org/ show_bug. cgi?id= 773009
# gcr-prompter logs debug info to /var/log/auth.log
# https:/
# https:/
if $programname == 'gcr-prompter' then stop
Run `sudo systemctl restart rsyslog` after creating that file, then gcr-prompter should no longer produce any logs.