Bug 242883 - kopete crashes when connecting to yahoo
Summary: kopete crashes when connecting to yahoo
Status: RESOLVED DUPLICATE of bug 200536
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.0.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-26 16:31 UTC by Robert
Modified: 2010-09-28 23:15 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert 2010-06-26 16:31:26 UTC
Application: kopete (1.0.0)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic i686
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
My system froze, probably do to having a forced shutdown of mozilla thunderbird. Since then kopete will start fine but when I try to connect it crashes. I am only using kopete for yahoo at this time.

The crash can be reproduced some of the time.

 -- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
[KCrash Handler]
#6  0x00bf6fe1 in ?? () from /lib/tls/i686/cmov/libc.so.6
#7  0x00fe9500 in QByteArray::detach (this=0x957f068, dev=0x957e9e8, len=-1) at /usr/include/bits/string3.h:52
#8  QByteArray::data (this=0x957f068, dev=0x957e9e8, len=-1) at /usr/include/qt4/QtCore/qbytearray.h:411
#9  KNetwork::Internal::KSocketBuffer::sendTo (this=0x957f068, dev=0x957e9e8, len=-1) at ../../kdecore/network/k3socketbuffer.cpp:256
#10 0x00fd4274 in KNetwork::KBufferedSocket::slotWriteActivity (this=0x9475d48) at ../../kdecore/network/k3bufferedsocket.cpp:349
#11 0x00fd40db in KNetwork::KBufferedSocket::qt_metacall (this=0x9475d48, _c=QMetaObject::InvokeMetaMethod, _id=24, _a=0xbfa9b878) at ./k3bufferedsocket.moc:75
#12 0x08925c9a in QMetaObject::metacall (object=0x9475d48, cl=1073667384, idx=24, argv=0xbfa9b878) at kernel/qmetaobject.cpp:237
#13 0x089343d5 in QMetaObject::activate (sender=0x91c22d0, m=0x8a34550, local_signal_index=0, argv=0xbfa9b878) at kernel/qobject.cpp:3293
#14 0x08985933 in QSocketNotifier::activated (this=0x91c22d0, _t1=30) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#15 0x0893b8e7 in QSocketNotifier::event (this=0x91c22d0, e=0xbfa9bd04) at kernel/qsocketnotifier.cpp:317
#16 0x01df24dc in QApplicationPrivate::notify_helper (this=0x903cb48, receiver=0x91c22d0, e=0xbfa9bd04) at kernel/qapplication.cpp:4300
#17 0x01df905e in QApplication::notify (this=0xbfa9c044, receiver=0x91c22d0, e=0xbfa9bd04) at kernel/qapplication.cpp:3704
#18 0x006baf2a in KApplication::notify (this=0xbfa9c044, receiver=0x91c22d0, event=0xbfa9bd04) at ../../kdeui/kernel/kapplication.cpp:302
#19 0x08920a3b in QCoreApplication::notifyInternal (this=0xbfa9c044, receiver=0x91c22d0, event=0xbfa9bd04) at kernel/qcoreapplication.cpp:704
#20 0x0894c9aa in QCoreApplication::sendEvent (source=0x903f458) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#21 socketNotifierSourceDispatch (source=0x903f458) at kernel/qeventdispatcher_glib.cpp:110
#22 0x0110d5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#23 0x011112d8 in ?? () from /lib/libglib-2.0.so.0
#24 0x011114b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#25 0x0894c5d5 in QEventDispatcherGlib::processEvents (this=0x9014ea0, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#26 0x01eb2135 in QGuiEventDispatcherGlib::processEvents (this=0x9014ea0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#27 0x0891f059 in QEventLoop::processEvents (this=0xbfa9bfa4, flags=) at kernel/qeventloop.cpp:149
#28 0x0891f4aa in QEventLoop::exec (this=0xbfa9bfa4, flags=...) at kernel/qeventloop.cpp:201
#29 0x0892369f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#30 0x01df2577 in QApplication::exec () at kernel/qapplication.cpp:3579
#31 0x08059a0e in main (argc=3, argv=0xbfa9c484) at ../../../kopete/kopete/main.cpp:105

Possible duplicates by query: bug 238932, bug 233512, bug 228920, bug 226819, bug 213409.

Reported using DrKonqi
Comment 1 Christoph Feck 2010-09-28 23:15:05 UTC

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