Bug#731562:

2015-03-08 Thread Grzegorz Bajson
Hi, I have similar problem, in my case it's caused by the fact that Kleoparta uses gpg instread of gpg2: gbajson@misio:~/.kde/env$ gpg gpg: /home/gbajson/.gnupg/gpg.conf:10: argument not expected gpg: /home/gbajson/.gnupg/gpg.conf:11: invalid option gbajson@misio:~/.kde/env$ gpg2 gpg: enabled de

Bug#731562: [kleopatra] kwatchgnupg messes up gpg.conf

2014-12-28 Thread Ximo Baldó i Soriano
Package: kleopatra Version: 4:4.14.2-2 --- Please enter the report below this line. --- Same behaviour here. Even configuring log levels to 0/none, kwatchgnupg modifies the file ~/.gnupg/gpg.conf and results in a not-working gpg. Stopping gpg-agent, modifying gpg.conf file and starting again gp

Bug#731562: [kleopatra] kwatchgnupg messes up gpg.conf

2013-12-06 Thread Johannes Zarl
Package: kleopatra Version: 4:4.11.3-1 Severity: normal --- Please enter the report below this line. --- On startup, kwatchgnupg adds the following lines to ~/.gnupg/gpg.conf: ###+++--- GPGConf ---+++### utf8-strings debug-level basic log-file socket:///home/zing/.gnupg/log-socket ###+++--- GPGC