Bug 179885

Summary:	Kopete crashes when manually disconnecting from a XMPP jabber server
Product:	[Unmaintained] kopete	Reporter:	Kevin Christmas <kachristmas>
Component:	Jabber Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Kevin Christmas 2009-01-07 07:08:17 UTC

Version:           4.2b2 (using Devel)
Compiler:           using packages from http://ppa.launchpad.net/kubuntu-experimental/ubuntu
OS:                Linux
Installed from:    Compiled sources

I can reproduce this bug on two different machines when disconnecting from Google Talk.  I've also experience this issue when disconnecting from other XMPP servers.

I apologize for not having back traces.  KDE tells me they aren't usable.

To recreate, connect to talk.google.com as one normally would.  Then, click the green dot in the lower right corner to show the accounts panel.  Right click on your Google Talk account and select "OffLine."  Wait for Kopete's crash handler to appear.

Comment 1 Dario Andres 2009-01-07 15:04:13 UTC

Try reading http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports to know howto create useful backtraces and post it here later. Thanks :) (there are known bugs about this, so this report may be a duplicate of another one)

Comment 2 Kevin Christmas 2009-01-07 16:40:42 UTC

I looked for a duplicate bug for this issue, and didn't find anything that appeared to be the same thing.

Here's the trace, courtesy of mehturt.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fddea1346f0 (LWP 16546)]
0x0000000000000001 in ?? ()
(gdb) bt
#0 0x0000000000000001 in ?? ()
#1 0x00007fdde50262c5 in QMetaObject::invokeMethod () from /usr/lib/libQtCore.so.4
#2 0x00007fdde62bd424 in QAbstractSocket::disconnectFromHost () from /usr/lib/libQtNetwork.so.4
#3 0x00007fdde62c0a98 in ?? () from /usr/lib/libQtNetwork.so.4
#4 0x00007fdde62b1991 in ?? () from /usr/lib/libQtNetwork.so.4
#5 0x00007fdde42ecc3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#6 0x00007fdde42f49ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#7 0x00007fdde5bf4f0b in KApplication::notify () from /usr/lib/libkdeui.so.5
#8 0x00007fdde501dd61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#9 0x00007fdde50463d9 in ?? () from /usr/lib/libQtCore.so.4
#10 0x00007fdddf98fd3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#11 0x00007fdddf99350d in ?? () from /usr/lib/libglib-2.0.so.0
#12 0x00007fdddf9936cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#13 0x00007fdde504615f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#14 0x00007fdde437ea6f in ?? () from /usr/lib/libQtGui.so.4
#15 0x00007fdde501c682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#16 0x00007fdde501c80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#17 0x00007fdde501ecbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#18 0x0000000000449f8c in main (argc=1, argv=0x7ffff2173328) at /build/buildd/kdenetwork-4.1.85/kopete/kopete/main.cpp:102

Comment 3 Dario Andres 2009-01-07 16:48:24 UTC

This is probably a duplicate of bug 176821
Just to be sure,can you install kdenetwork-dbg and libqt4-dbg, and then reproduce the crash to post a more complete backtrace ?. Thanks

Comment 4 Kevin Christmas 2009-01-07 17:49:28 UTC

(In reply to comment #3)
> This is probably a duplicate of bug 176821
> Just to be sure,can you install kdenetwork-dbg and libqt4-dbg, and then
> reproduce the crash to post a more complete backtrace ?. Thanks
> 

That bug looks like the same issue.  I did not search on 'Offline,' only 'Disconnect' and 'Logout'

I have both kdenetwork-dbg and libqt4-dbg installed.  The crash handler shows up.  I attempt to get the backtrace from the crash handler, and then informs me that the backtrace is not usable.  I'm not sure why.

Comment 5 Dario Andres 2009-01-07 17:53:25 UTC

No problem :)

*** This bug has been marked as a duplicate of bug 176821 ***