It says I don't have to otr plugin.

[Zooko Wilcox-O'Hearn]

Binary package hint: kopete-plugin-otr-kde4

I installed kopete with otr plugin for kde4:

ii kopete-kde4 4:4.0.3-0ubuntu1 instant messenger for KDE 4
ii kopete-plugin-otr-kde4 0.8-0ubuntu1 Off-The-Record encryption for the KDE 4 version of Kopete

When my buddy tries to IM me with OTR, kopete writes this message:

"?OTR?v2? <email address hidden>/_ has requested an Off-the-Record private conversation. However, you do not have a plugin to support that. See http://www.cypherpunks.ca/otr/ for more information."

[Uwe L. Korn (uwelk)]

This site which this link refers to is the common OTR site and just the latest news is concerned with pidgin not the whole site ;-)

I'm not common any more with Kopete in KDE 4 but as in many IM's you might need to turn on the plugin additionally in the settings of the program.

[Zooko Wilcox-O'Hearn (zooko)]

Okay, so the mismatch between user expectations and software behavior here, I guess, is that I thought that apt-get install'ing the plugin would mean that it was "present" within kopete, which is inconsistent with the error message that says "you do not have a plugin".

[Uwe L. Korn (uwelk)]

Is there still a bug using the OTR plugin or could this bug be closed since this was only caused by misunderstanding messages?

[Zooko Wilcox-O'Hearn (zooko)]

The message is misleading. The message says "You do not have a plugin", but I have already apt-get installed the plugin. By the way I heard a report from another user or two that they had the exact same confusion.

To fix the error message, change it to "There is no plugin currently enabled to support that.". Then users will realize that, although they *do* have the plugin, that they need to take another step to "enable" it.

(A better solution might be to make it be enabled by default so that they do not have to take the second step. But if they do, then the error message should point them in the right direction.)

[José Ernesto Dávila Pantoja (josernestodavila)]

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!