| Summary: | enable-progress-filter gpg option break decryption | ||
|---|---|---|---|
| Product: | [Applications] kgpg | Reporter: | rotflol2 |
| Component: | general | Assignee: | Rolf Eike Beer <kde> |
| Status: | ASSIGNED --- | ||
| Severity: | major | ||
| Priority: | NOR | ||
| Version First Reported In: | 2.9.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
rotflol2
2013-05-20 12:40:24 UTC
Please build KGpg from sources and when calling CMake add -DKGPG_DEBUG_TRANSACTIONS=On to the commandline. Then start the built KGpg from a terminal (make sure to quit the other one before). When you decrypt it will give you some extra debug output. Make sure to use a dummy encrypted text, as the text contents are also present in the debug log (or just strip the contents). Then add the log here. Hi Rolf, I followed those instructions, making sure to quit kgpg if it was running and running the copy I just compiled, but go not additional debugging information. the problem remained as it. If I run the gpg2 command manually, with the options as per the original post of mine, piping gpg encrypted data to it, it behaves as expected, asking for the passphrase and decrypting. D. Then you did something wrong.
$ cmake -D KGPG_DEBUG_TRANSACTIONS=On /source/of/kgpg && make && ./kgpg -d
[...]
kgpg(18897) KGpgTransaction::start: KGpgDecrypt(0x1808e00) ("/usr/bin/gpg2", "--no-secmem-warning", "--no-tty", "--no-greeting", "--options", "/home/eike/.gnupg/gpg.conf", "--debug-level", "none", "--status-fd=1", "--decrypt", "--command-fd=0")
kgpg(18897) KGpgTransactionPrivate::slotReadReady: KGpgDecrypt(0x1808e00) "[GNUPG:] ENC_TO 845489F2300CC5F0 16 0"
kgpg(18897) KGpgTransactionPrivate::slotReadReady: KGpgDecrypt(0x1808e00) "[GNUPG:] USERID_HINT 845489F2300CC5F0 Rolf Eike Beer <eike@sf-mail.de>"
kgpg(18897) KGpgTransactionPrivate::slotReadReady: KGpgDecrypt(0x1808e00) "[GNUPG:] NEED_PASSPHRASE 845489F2300CC5F0 5CA4893E69B9FC4E 16 0"
kgpg(18897) KGpgTransactionPrivate::slotReadReady: KGpgDecrypt(0x1808e00) "[GNUPG:] GOOD_PASSPHRASE"
kgpg(18897) KGpgTransactionPrivate::slotReadReady: KGpgDecrypt(0x1808e00) "[GNUPG:] BEGIN_DECRYPTION"
kgpg(18897) KGpgTransactionPrivate::slotReadReady: KGpgDecrypt(0x1808e00) "[GNUPG:] DECRYPTION_INFO 2 9"
kgpg(18897) KGpgTransactionPrivate::slotReadReady: KGpgDecrypt(0x1808e00) "[GNUPG:] PLAINTEXT 62 1369251553 "
kgpg(18897) KGpgTransactionPrivate::slotReadReady: KGpgDecrypt(0x1808e00) "[GNUPG:] PLAINTEXT_LENGTH 3"
kgpg(18897) KGpgTransactionPrivate::slotReadReady: KGpgDecrypt(0x1808e00) "foo[GNUPG:] DECRYPTION_OKAY"
kgpg(18897) KGpgTransactionPrivate::slotReadReady: KGpgDecrypt(0x1808e00) "[GNUPG:] GOODMDC"
kgpg(18897) KGpgTransactionPrivate::slotReadReady: KGpgDecrypt(0x1808e00) "[GNUPG:] END_DECRYPTION"
Didn't provide such output for me. I've found that occasionally when I close the editor window, it THEN asks for the passphrase. I found the source of the problem I had the line enable-progress-filter in my gpg.conf. Removing this fixed the problem. It didn't cause issues with any other version of kgpg. Thanks for the debugging, I will have a look. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! I still need to check. My bad. |