Bug 140955 - crypto plugin doesn't decrypt
Summary: crypto plugin doesn't decrypt
Status: RESOLVED DUPLICATE of bug 134907
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 141316 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-01-31 15:32 UTC by Ralf Hildebrandt
Modified: 2007-03-22 00:03 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Hildebrandt 2007-01-31 15:32:03 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources

This is KDE 3.5.6, the bug submission website doesn't list 3.5.6 yet, only 3.5.5 :(  -- so feel free to recategorize this bug.

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!
Comment 1 Ralf Hildebrandt 2007-01-31 15:34:52 UTC
Version of kopete: 3.5.6-0ubuntu3
Platform: Ubuntu packages, i386, feisty fawn
Comment 2 Ralf Hildebrandt 2007-01-31 15:44:51 UTC
I manually reverted to kopete 3.5.5+kopete0.12.3-0ubuntu1 and voila, crypto works like a charm again. Make of that what you want :)
Comment 3 Hanns-Martin Kreie 2007-02-01 16:22:28 UTC
I guess the following diff (taken from gentoo work directories) could explain why... 

--- kopete-3.5.5-r2/work/kopete-3.5.5/kopete/plugins/cryptography/cryptographyp$
+++ kopete-3.5.6/work/kopete-3.5.6/kopete/plugins/cryptography/cryptographyplug$
@@ -58,8 +58,9 @@
        if( !pluginStatic_ )
                pluginStatic_=this;

-       m_inboundHandler = new Kopete::SimpleMessageHandlerFactory( Kopete::Mes$
-               Kopete::MessageHandlerFactory::InStageToSent, this, SLOT( slotI$
+       m_inboundHandler = 0;
+/*     m_inboundHandler = new Kopete::SimpleMessageHandlerFactory( Kopete::Mes$
+               Kopete::MessageHandlerFactory::InStageToSent, this, SLOT( slotI$
        connect( Kopete::ChatSessionManager::self(),
                SIGNAL( aboutToSend( Kopete::Message & ) ),
                SLOT( slotOutgoingMessage( Kopete::Message & ) ) );

Is there a special reason for this? Another way of handling messages? Or is this just an erroneous change?
Comment 4 Hanns-Martin Kreie 2007-02-01 17:06:15 UTC
Reversing this (putting the handler line in kopete/plugins/cryptography/cryptographyplugin.cpp back in) makes kopete handle encrypted messages correctly again, without anything blowing up immediately.
Comment 5 Mark Wehner 2007-02-05 09:28:30 UTC
*** This bug has been confirmed by popular vote. ***
Comment 6 Michael Hekel 2007-02-05 20:53:06 UTC
I want to confirm this bug.
Comment 7 Philip Rodrigues 2007-02-07 18:50:04 UTC
*** Bug 141316 has been marked as a duplicate of this bug. ***
Comment 8 Philip Rodrigues 2007-03-01 23:45:47 UTC

*** This bug has been marked as a duplicate of 134907 ***