* Thomas Koch <tho...@koch.ro> [2015-03-10 08:51:46 +0100]: > Package: kde-runtime > Version: 4:4.14.2-2 > Severity: grave > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > I'm using kwallet with the new gpg backend. > > Since the last aptitude update and reboot kwalletd seems to open around 20 > instances > of the following process every 5 minutes: > > gpg2 --batch --no-sk-comment --status-fd 12 --no-tty --charset utf8 \ > --enable-progress-filter --display :0 --with-colons --fixed-list-mode \ > --with-fingerprint --with-fingerprint --list-keys --
Well, that's bizarre. kwalletd uses libgpgme to handle GPG encryption. I have no idea why gpg2 is launched on your system. Checking on my system (I'm using GPG backend) there's no gpg2 spawned. I can also confirm never having seen this behavior. > > I'm currently running > while true ;do killall gpg2 ; sleep 1;done > to be able to write this bug report. :-) > > When those gpg2 processes get killed, two different kinds of dialog windows > pop up: > > "Error when attempting to open the wallet kdewallet. The wallet was encrypted > using > the GPG Key ID 07FC4891042BA65A but this key was not found on your system." > or > "Error when attempting to decrypt the wallet kdewallet using GPG. If you're > using a > SmartCard, please ensure it's inserted then try again. > GPG error was No data" > > I have a keyring that is way too big and thus amplifies the problem for me. > But that > should not result in an overheated cpu. > > I believe the process asking for wallet access might be kmail via akonadi > since no > other KDE program is running AFAIK. > > Some of the last updates were: > > qt4-x11 (source) 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 -> > 4:4.8.6+git64-g5dc8b2b+dfsg-3 > gnupg:amd64 1.4.18-6 -> 1.4.18-7 I'm using gnupg 2.1.2-1 on my ArchLinux system. Do you have this version under Ubuntu? -- Valentin Rusu IRC: valir -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
