While testing out the newest master (installed in neon dev) I encountered a crash which was already valid in the current stable release. When the account does not yet have a generated OTR key but the other side starts an OTR session, the "receiving" kopete (the one without key) crashes.
Please attach stack trace with debug symbols.
I used your PPA as suggested in bug #362535 and there it happens, too. Just add a new account without a key and initiate an OTR session from a peer. Unfortunately, even though I installed kopete-dbg, neither on the console nor in the KDE Crash Handler there are any details. So I started kopete in gdb, but "bt" just said "No stack.". How can I get you a useable backtrace from your PPA in Ubuntu? Thanks!
In KDE crash window is button to install missing debug symbols. And yes kopete-dbg package is needed too. When you are going to debug kopete in gdb, start kopete with --nofork, so gdb will have access to kopete process: $ gdb -ex r -ex bt --args kopete --nofork
Created attachment 102470 [details] backtrace of kopete crashing when receiving an OTR message while not having a key on our own The crash handling dialog didn't offer any more symbols to install. But --nofork did the trick :D
Thank you, now I found where is a problem! For now marking as duplicate of bug #349596. *** This bug has been marked as a duplicate of bug 349596 ***