Bug 228542 - Kopete 0.12.4 (KDE 3.5.6) breaks crypto plugin
Kopete 0.12.4 (KDE 3.5.6) breaks crypto plugin
Product: Fedora
Classification: Fedora
Component: kdenetwork (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2007-02-13 13:09 EST by Douglas E. Warner
Modified: 2007-11-30 17:11 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-20 11:04:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
KDE Software Compilation 140955 None None None Never

  None (edit)
Description Douglas E. Warner 2007-02-13 13:09:35 EST
Description of problem (from upstream):
kopete's crypto plugin doesn't decrypt messages. I can send properly encrypted 
messages (they're shown as ciphertext, though), but incoming encrypted 
messages are not decrypted. 
Also, kopete (or GPG) never ask for the passphrase, no matter if I enable "ask 
for passphrase" or use the gpg-agent. 
The very same setup used to work with kopete from kde 3.5.5!

Version-Release number of selected component (if applicable):
Kopete 0.12.4/KDE 3.5.6

How reproducible:
Send or receive GPG-encrypted IM in kopete; the output will not be decrypted.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Till Maas 2007-02-14 17:23:26 EST
The bug seems to be easy to fix, just revert the change shown in
Comment 2 Douglas E. Warner 2007-03-02 10:06:39 EST
Changed upstream bug link from http://bugs.kde.org/show_bug.cgi?id=140955 to 
Comment 3 Rex Dieter 2007-06-20 11:04:10 EDT
The referenced patch is included in kde-3.5.7, which is currently in
updates-testing.  So, that should address this issue... closing.

Feel free to reopen if problems persist.

Note You need to log in before you can comment on or make changes to this bug.