| Summary: | crypto plugin doesn't decrypt | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Ralf Hildebrandt <ralf.hildebrandt> |
| Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | adarovsky, Andreas.Schallenberg, silfreed-kdebugs, sven.burmeister |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Ralf Hildebrandt
2007-01-31 15:32:03 UTC
Version of kopete: 3.5.6-0ubuntu3 Platform: Ubuntu packages, i386, feisty fawn 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 :) 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?
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. *** This bug has been confirmed by popular vote. *** I want to confirm this bug. *** Bug 141316 has been marked as a duplicate of this bug. *** |