Bug 207447

Summary:	Kopete crash on startup (Client::setStatus, GroupWiseAccount::setStatusMessage, NowListeningPlugin::slotAdvertCurrentMusic)
Product:	[Unmaintained] kopete	Reporter:	Frode Jemtland <frode>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Frode Jemtland 2009-09-15 13:02:41 UTC

Application that crashed: kopete
Version of the application: 0.70.90
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-1-686 i686
Distribution: Debian GNU/Linux testing (squeeze)

 -- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
[KCrash Handler]
#6  0xb234d08c in Client::setStatus (this=0x0, status=GroupWise::Offline, reason=..., autoReply=...) at ../../../../../kopete/protocols/groupwise/libgroupwise/client.cpp:226
#7  0xb23a73fa in GroupWiseAccount::setStatusMessage (this=0xa736a68, statusMessage=...) at ../../../../kopete/protocols/groupwise/gwaccount.cpp:413
#8  0xb31a2c83 in NowListeningPlugin::slotAdvertCurrentMusic (this=0xa670318) at ../../../../kopete/plugins/nowlistening/nowlisteningplugin.cpp:296
#9  0xb31a38eb in NowListeningPlugin::qt_metacall (this=0xa670318, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf9b1f08) at ./nowlisteningplugin.moc:79
#10 0xb73e7b33 in QMetaObject::activate (sender=0x9fe4868, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#11 0xb73e8782 in QMetaObject::activate (sender=0x9fe4868, m=0xb74c3de4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#12 0xb7423177 in QTimer::timeout (this=0x9fe4868) at .moc/release-shared/moc_qtimer.cpp:128
#13 0xb73ede9e in QTimer::timerEvent (this=0x9fe4868, e=0xbf9b238c) at kernel/qtimer.cpp:261
#14 0xb73e2bcf in QObject::event (this=0x9fe4868, e=0xbf9b238c) at kernel/qobject.cpp:1074
#15 0xb6a12814 in QApplicationPrivate::notify_helper (this=0x9f18758, receiver=0x9fe4868, e=0xbf9b238c) at kernel/qapplication.cpp:4056
#16 0xb6a1a97e in QApplication::notify (this=0xbf9b261c, receiver=0x9fe4868, e=0xbf9b238c) at kernel/qapplication.cpp:3603
#17 0xb79474ad in KApplication::notify (this=0xbf9b261c, receiver=0x9fe4868, event=0xbf9b238c) at ../../kdeui/kernel/kapplication.cpp:302
#18 0xb73d29cb in QCoreApplication::notifyInternal (this=0xbf9b261c, receiver=0x9fe4868, event=0xbf9b238c) at kernel/qcoreapplication.cpp:610
#19 0xb7401361 in QCoreApplication::sendEvent (this=0x9eff434) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 QTimerInfoList::activateTimers (this=0x9eff434) at kernel/qeventdispatcher_unix.cpp:572
#21 0xb73fd900 in timerSourceDispatch (source=0x9eff400) at kernel/qeventdispatcher_glib.cpp:165
#22 0xb5cd34b8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb5cd6a13 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0xb5cd6b98 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0xb73fd877 in QEventDispatcherGlib::processEvents (this=0x9ee1690, flags=...) at kernel/qeventdispatcher_glib.cpp:329
#26 0xb6ab1fd5 in QGuiEventDispatcherGlib::processEvents (this=0x9ee1690, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#27 0xb73d101a in QEventLoop::processEvents (this=0xbf9b25b0, flags=...) at kernel/qeventloop.cpp:149
#28 0xb73d1462 in QEventLoop::exec (this=0xbf9b25b0, flags=...) at kernel/qeventloop.cpp:201
#29 0xb73d38b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#30 0xb6a12697 in QApplication::exec () at kernel/qapplication.cpp:3525
#31 0x08059653 in main (argc=3, argv=0xbf9b2a24) at ../../../kopete/kopete/main.cpp:104

This bug may be a duplicate of or related to bug 207170

Reported using DrKonqi

Comment 1 Dario Andres 2009-09-16 03:24:13 UTC

- Does it happens all the times ? Thanks

Comment 2 Frode Jemtland 2009-09-16 13:49:48 UTC

No, I did manage to start it once yesterday, but stupid enough stopped it half an hour later, to test if the error was gone...... Didn't manage to start it again for the rest of the day (6-7 times). Have tryed 3-4 times today, without success.

Comment 3 Dario Andres 2009-09-16 14:09:18 UTC

Thanks

Comment 4 Frode Jemtland 2009-09-16 15:43:33 UTC

More info on when it happens.

I'm using Amarok all the time, so since it's mentioned in the bug report that the NowListeningPlugin is activated, I tested to close Amarok before starting kopete. Now Kopete is working like it should.

Tried to disable the NowListeningPlugin. Now I can start and stop Kopete both if Amarok is running or not.

Last test. While bothe Amarok and Kopete running at once, tryed to enable NowListeningPlugin. It takes about 5 - 10 seconds, and Kopete crashes.....

So work-a-round for me is to disable the NowListeningPlugin.

So this bug is a duplicate of bug 207170.... (Now I'm not sure how I should correct change status of this bug, but I'm trying to mark it as duplicate.....)

-Frode

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

Comment 5 Nicolas L. 2010-08-19 02:52:51 UTC

*** Bug 248270 has been marked as a duplicate of this bug. ***