kopete-kde4 crashes when reconnecting to Jabber servers

I can't reproduce this one, please install kdenetwork-dbg-kde4 and check wether you get any useful information when starting kopete from konsole.

As for me, it reproduces every time I get disconnected.

The only info I could send is:

Thread 2 (Thread 0xb3818b90 (LWP 7700)):
#0 0xb7f13c03 in ?? () from /usr/lib/libQtCore.so.4
#1 0xb7f13bc0 in ?? () from /usr/lib/libQtCore.so.4
#2 0x0877db28 in ?? ()
#3 0xb3818118 in ?? ()
#4 0xb692c976 in pthread_mutex_unlock () from /lib/tls/i686/cmov/libc.so.6
#5 0xb678662f in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#6 0xb6786de9 in ?? () from /usr/lib/libglib-2.0.so.0
#7 0x087b1de0 in ?? ()
#8 0xb38181b8 in ?? ()
#9 0x08785678 in ?? ()
#10 0x00001e14 in ?? ()
#11 0x00000002 in ?? ()
#12 0xb67fa5f8 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0xb67fa620 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0xb673e8c5 in pthread_getspecific ()
   from /lib/tls/i686/cmov/libpthread.so.0
#15 0xb67876ee in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#16 0xb7f13f42 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#17 0xb7eef062 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#18 0xb7eef16c in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#19 0xb3b7353a in QCA::SyncThread::run () from /usr/lib/libqca.so.2
#20 0xb7e3b037 in ?? () from /usr/lib/libQtCore.so.4
#21 0x087f2198 in ?? ()
#22 0x00000000 in ?? ()

Thread 1 (Thread 0xb5e306c0 (LWP 7699)):
#0 0xb7f80410 in __kernel_vsyscall ()
#1 0xb68deba6 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2 0xb68de9b7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3 0xb7af3ab0 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4 0x00000001 in ?? ()
#5 0x00000000 in ?? ()
#0 0xb7f80410 in __kernel_vsyscall ()

I'll try to run Kopete in debugger when I have some time.

Are you still experiencing this problem with current KDE4 packages?

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!