I have installed KDE on Windows and, since I find Kopete very useful on Linux, I have installed it on Windows as well.
I'm using Windows XP professional 64bit (for Amd64), and I have used the graphical installer (latest version) and selected mingw64 compiled packages. I have selected the "latest" repository, and my KDE software is version 4.8.00.

When I launch Kopete, it starts as it should, with icon in the task bar and contact list window (which is of course empty, since no account is configured yet).
I don't get any "account wizard" window (as usually on Linux), so I try to select "configure" from the menu to add a new account.
When I click on that, though, Kopete starts using up 100% of my CPU, my whole PC starts not responding, no configure window ever shows up (I've waited up to half an hour) and I have to force-quit it. I can't, therefore, enable any account on Kopete, and so it becomes completely useless.
All other menu options work as they should, and open the appropriate window.
I have tried disabling antivirus (avast) and firewall (COMODO), but nothing changed.

All other KDE programs work fine, that's why I have posted here instead of the KDE on Windows section.
TIA for any suggestion

I do not know if KDE on Windows includes it, but could you try using "kdebugdialog" (should be somewhere in the /bin folder in the KDE on Windows installation directory) to enable all debug areas?

Then try running Kopete directly in a terminal, and posting that debug output here.

bcooksley wrote:I do not know if KDE on Windows includes it, but could you try using "kdebugdialog" (should be somewhere in the /bin folder in the KDE on Windows installation directory) to enable all debug areas?

Then try running Kopete directly in a terminal, and posting that debug output here.

I've managed to get some debug (Windows doesn't make things easy for that); I've attached it on pastebin; I had to divide it into two parts:
part 1
part 2

The second column has the time passed from the start of Kopete; there are three sets of data: seconds 1-6 contain launching kopete; seconds 11-12 contain the output when I selected "configure", until everything hanged; second 255 is when I managed to kill kopete.

Unfortunately that doesn't provide much info on why it hangs. Unless you have a debugger available, and can attach it and find out where it is endlessly looping, this will be fairly hard to investigate any further unfortunately.