Hi,

using Kopete (with Kubuntu 11.04) + OTR, Kopete forgets very often my private key.

Maybe this is a bug, maybe this is caused by some strange configuration I did. First of all, I try to describe my configuration, afterwards, I try to explain what happens.

I am using Kopete 1.0.80 with KDE 4.6.2 (Kubuntu 11.04). Together with Kopete, I am using the OTR-plugin (version 0.9). Since I am using a Truecrypt-crypto-container and I want to store all my private keys and fingerprints in this container (and I do not want to modify the some kopete-configuration-file), I just inserted a symbolic link from:

~/.kde/share/apps/kopete --> ~/Crypto/mnt/.kde/share/apps/kopete
~/.kde/share/apps/kopete_otr --> ~/Crypto/mnt/.kde/share/apps/kopete_otr
~/.kde/share/apps/kopete_history --> ~/Crypto/mnt/.kde/share/apps/kopete_history

In the directory kopete_otr, you can find the needed files:
fingerprints
privkeys

It happens now VERY often, that when I start kopete, and start some OTR-chat with a person I already talked to using OTR, he starts to create a new private key! Of course I cancel this (by closing the application) - and If I again look at the kopete_otr directory, the files

privkeys

have the size of 0 bytes (or 10xx bytes if I let him finish the generation of the private key). The only way for me to get my old private key back is to manually copy a backup of my privkeys file to the privkeys.

cp ~/Crypto/mnt/.kde/share/apps/kopete_otr/privkeys_backup ~/Crypto/mnt/.kde/share/apps/kopete_otr/privkeys

Some times I have to re-copy the file, sometimes I don't. It happens with people from the jabber-network, and with people using ICQ. Sadly it does not happen ALL the time, so it is very hard for me to analyze this.

Does anyone see the problem here and why he always wants to create a new key instead of taking the old one? Is this a problem of using symbolic links to this Truecrypt-container-directory? What am I doing wrong?

Thank you in advance,
Dennis

Try enabling all debug areas, then examining the debug content of ~/.xsession-errors to see if any indications are given by Kopete as to why it wants to regenerate the keys.

Hi,

using a "tail -f" on this file, directly after the "creating ney OTR private key" message came, it shows up:

kopete(2802)/kopete (oscar - raw protocol) Xtraz::XtrazNotify::handle: Cannot parse xml document!

(Without recompiling the kopete-package manually with additional debug symbols, I do not know how to debug it more detailled.)

To repeat:
The file "privkeys" was definitely present on the system and filled with my private key. After the key was newly created, I again copied my backup-key-file over the old one, and renewed the OTR session - worked perfectly with my old (original) key.

Regards
Dennis