Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#21773 - [gnupg] 10GB /var/log/messages.log with the same message from pcscd
Attached to Project:
Arch Linux
Opened by Alphazo (alphazo) - Sunday, 21 November 2010, 13:00 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 19 January 2011, 20:24 GMT
Opened by Alphazo (alphazo) - Sunday, 21 November 2010, 13:00 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 19 January 2011, 20:24 GMT
|
DetailsYesterday, after signing one message using my CryptoStick (OpenPGP card V2 + USB reader), GnuPG and Thunderbird (enigmail) I got my /var/log/messages.log filled up with 10GB (that's a lot) of the same exact message:
Nov 20 21:15:00 localhost pcscd: ccid_usb.c:613:WriteUSB() write failed (2/3): -9 Success In fact it was only 10GB because I didn't have any more space left on this partition. I also had /var/log/everything.log and /var/log/user.log with the same content. The line just before the one above was: Nov 20 21:13:12 localhost kernel: usb 2-1.2: new full speed USB device using ehci_hcd and address 3 The only thing I remember is that I probably have removed the drive at some point. Has someone seen this behavior before? |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Wednesday, 19 January 2011, 20:24 GMT
Reason for closing: Works for me
Wednesday, 19 January 2011, 20:24 GMT
Reason for closing: Works for me

You should better ask in our forum such a question. People will not read here around. I don't use such a setup like yours and won't be able to help you. And it doesn't sound to be a packaging bug.