| Summary: | Kopete crash on startup during Yahoo login (and other situations) [memcpy, KNetwork::Internal::KSocketBuffer::sendTo, KNetwork::KBufferedSocket::slotWriteActivity | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Paul Fee <paul.f.fee> |
| Component: | Yahoo Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | ahartmetz, albbas, alexfera90, andrein_bio, andresbajotierra, apitrone, bravomike67, cmcx.linux, elnetotaca, frank, frederic.coiffier, jon, jonathandodd, jussi01, kde-bugs, kde, kdelibs-bugs, leh, mike+kde, mikko.cal, optiluca, patrick.noffke, pedaum, pghammer21, reubendb, rgonzalez, rhopgood60, sdelfranco, theuteck |
| Priority: | NOR | ||
| Version: | 0.70.90 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
*** Bug 212447 has been marked as a duplicate of this bug. *** *** Bug 212815 has been marked as a duplicate of this bug. *** *** Bug 212429 has been marked as a duplicate of this bug. *** Reporter from bug 226207 is experiencing this with KDE SC 4.4.0. -- Information about the crash: Every time I try to login, using the yahoo protocol, Kopete crashes. Also for a brief second I can see my buddy list. *** Bug 226207 has been marked as a duplicate of this bug. *** I haven't touched this code in 5 years. I'm as good as the next person to debug it. Created attachment 40689 [details]
New crash information added by DrKonqi
I got this behavior after I made some changes in my yahoo list
Created attachment 40741 [details]
New crash information added by DrKonqi
Well, it crashed after I opened it. Another problem that I have on kde 4.4.0 with kopete 1.0 is that I can't send text from yahoo. I mean I can open conversations, receive messages, but none of my messages get received.
From bug 226819: -- Information about the crash: Kopete crashed when i connect to networks. Setted up protocols: XMPP (Jabber.org + gTalk), ICQ, AIM, Yahoo! Enabled plugins: Listening (no audio program running), History, Message indicator, Contact notes, Picture preview From bug 226854: -- Information about the crash: This is a recreation of a bug. I removed the Yahoo account section from my kopeterc. kopete started fine. I added my Yahoo account. kopete crashed during Yahoo login. Others: I am subscribed to JabbeRRS service. Usually i get a large message with many headers and links when i get online. *** Bug 226819 has been marked as a duplicate of this bug. *** *** Bug 226854 has been marked as a duplicate of this bug. *** From bug 228451: -- Information about the crash: Since I upgraded to KDE 4.4 from 4.3.5, Kopete crash almost everytime I start it. After upgrade, kopete crash every time I tried to open it. I set it to automatically connect to all accounts when started. I then decided to start clean by removing all Kopete's configuration files under ~/.kde/share/apps/kopete and ~/.kde/share/config/kopete* After I was able to start kopete, I recreated my accounts. I currently have Yahoo Messenger account, Skype, and Jabber (Google Talk) configured. Now Kopete starting to crash again almost everytime I start it. *** Bug 228451 has been marked as a duplicate of this bug. *** I removed Yahoo Messenger account from Kopete since I cannot use it anyway due to bug #226699, and I haven't had any more crashes. So the problems seem to point to the Yahoo protocol plugin. What I'm wondering is that I don't remember seeing this with earlier KDE (4.3.5) and QT (4.5). *** Bug 228920 has been marked as a duplicate of this bug. *** *** Bug 230579 has been marked as a duplicate of this bug. *** *** Bug 230647 has been marked as a duplicate of this bug. *** From bug 231277: -- Information about the crash: Kopete is not stable enough to tolerate the frequent changes in kdenetworkstatus and eventually gives up and crashes. *** Bug 231277 has been marked as a duplicate of this bug. *** *** Bug 233016 has been marked as a duplicate of this bug. *** *** Bug 233512 has been marked as a duplicate of this bug. *** Created attachment 49445 [details]
New crash information added by DrKonqi
Desktop blocked, no screensaver, kopete away, incoming message produces crash, no interaction needed to reproduce problem
*** Bug 238932 has been marked as a duplicate of this bug. *** *** Bug 246177 has been marked as a duplicate of this bug. *** *** Bug 246802 has been marked as a duplicate of this bug. *** *** Bug 252434 has been marked as a duplicate of this bug. *** *** Bug 247274 has been marked as a duplicate of this bug. *** *** Bug 242883 has been marked as a duplicate of this bug. *** *** Bug 237754 has been marked as a duplicate of this bug. *** *** Bug 273793 has been marked as a duplicate of this bug. *** *** Bug 303691 has been marked as a duplicate of this bug. *** *** Bug 212879 has been marked as a duplicate of this bug. *** *** Bug 299487 has been marked as a duplicate of this bug. *** Hello from the KDE Bugsquad! Unfortunately, Yahoo has discontinued the Yahoo Messenger service, and the code has been removed from Kopete. Thus, I am closing this bug as "UNMAINTAINED" since it will no longer be fixable, or able to operate due to Yahoo. |
Application that crashed: kopete Version of the application: 0.70.90 KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) Qt Version: 4.5.0 Operating System: Linux 2.6.28-13-generic x86_64 Distribution: Ubuntu 9.04 What I was doing when the application crashed: After logging in, KDE desktop session starts up. Kopete starts automatically and tries to login into a couple of Yahoo IM accounts. Popup appeared from KDE Wallet manager stating that kopete required access. Shortly after that kopete crashed, possibly when interacting with the Yahoo server. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault [Current thread is 0 (LWP 8065)] Thread 2 (Thread 0x7f98e0e1e950 (LWP 8132)): #0 0x00007f98f347ac57 in sched_yield () from /lib/libc.so.6 #1 0x00007f98f4dc9871 in QMutex::lock (this=0x1e369c0) at thread/qmutex.cpp:219 #2 0x00007f98f4dcfa02 in QWaitCondition::wait (this=<value optimized out>, mutex=0x1e369c0, time=30000) at thread/qwaitcondition_unix.cpp:161 #3 0x00007f98f4dc5409 in QThreadPoolThread::run (this=0x1c37bc0) at concurrent/qthreadpool.cpp:140 #4 0x00007f98f4dce952 in QThreadPrivate::start (arg=0x1c37bc0) at thread/qthread_unix.cpp:189 #5 0x00007f98f12733ba in start_thread (arg=<value optimized out>) at pthread_create.c:297 #6 0x00007f98f3494fcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f98f8eab750 (LWP 8065)): [KCrash Handler] #5 memcpy () at ../sysdeps/x86_64/memcpy.S:427 #6 0x00007f98f55938b6 in KNetwork::Internal::KSocketBuffer::sendTo (this=0x1b94f50, dev=0x1bfbdc0, len=-1) at /usr/include/bits/string3.h:52 #7 0x00007f98f5580fae in KNetwork::KBufferedSocket::slotWriteActivity (this=0x1b7ed30) at /build/buildd/kde4libs-4.2.96/kdecore/network/k3bufferedsocket.cpp:349 #8 0x00007f98f5580e57 in KNetwork::KBufferedSocket::qt_metacall (this=0x1b7ed30, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=<value optimized out>) at /build/buildd/kde4libs-4.2.96/obj-x86_64-linux-gnu/kdecore/k3bufferedsocket.moc:69 #9 0x00007f98f4ecd1f2 in QMetaObject::activate (sender=0x1c37580, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1f10) at kernel/qobject.cpp:3069 #10 0x00007f98f4f0444e in QSocketNotifier::activated (this=0x1d2994b, _t1=18) at .moc/release-shared/moc_qsocketnotifier.cpp:83 #11 0x00007f98f4ed1e53 in QSocketNotifier::event (this=0x1c37580, e=0x7fff00ee7cd0) at kernel/qsocketnotifier.cpp:316 #12 0x00007f98f40a178d in QApplicationPrivate::notify_helper (this=0x17dc490, receiver=0x1c37580, e=0x7fff00ee7cd0) at kernel/qapplication.cpp:4084 #13 0x00007f98f40a997a in QApplication::notify (this=0x7fff00ee8ad0, receiver=0x1c37580, e=0x7fff00ee7cd0) at kernel/qapplication.cpp:4049 #14 0x00007f98f5aa563b in KApplication::notify (this=0x7fff00ee8ad0, receiver=0x1c37580, event=0x7fff00ee7cd0) at /build/buildd/kde4libs-4.2.96/kdeui/kernel/kapplication.cpp:302 #15 0x00007f98f4eb775c in QCoreApplication::notifyInternal (this=0x7fff00ee8ad0, receiver=0x1c37580, event=0x7fff00ee7cd0) at kernel/qcoreapplication.cpp:602 #16 0x00007f98f4ee10e9 in socketNotifierSourceDispatch (source=0x17e73b0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #17 0x00007f98ef2b720a in IA__g_main_context_dispatch (context=0x17e6520) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814 #18 0x00007f98ef2ba8e0 in g_main_context_iterate (context=0x17e6520, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448 #19 0x00007f98ef2baa7c in IA__g_main_context_iteration (context=0x17e6520, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511 #20 0x00007f98f4ee0e6f in QEventDispatcherGlib::processEvents (this=0x17aef70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323 #21 0x00007f98f4139bef in QGuiEventDispatcherGlib::processEvents (this=0x1d2994b, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #22 0x00007f98f4eb6002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 15630064}) at kernel/qeventloop.cpp:149 #23 0x00007f98f4eb63cd in QEventLoop::exec (this=0x7fff00ee7f30, flags={i = 15630160}) at kernel/qeventloop.cpp:200 #24 0x00007f98f455f10e in QDialog::exec (this=0x1c6b400) at dialogs/qdialog.cpp:498 #25 0x00007f98f5a1838f in KDialogQueue::Private::slotShowQueuedDialog (this=0x1e66950) at /build/buildd/kde4libs-4.2.96/kdeui/dialogs/kdialog.cpp:1055 #26 0x00007f98f5a1843d in KDialogQueue::qt_metacall (this=0x1e39fa0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=<value optimized out>) at /build/buildd/kde4libs-4.2.96/obj-x86_64-linux-gnu/kdeui/kdialogqueue_p.moc:66 #27 0x00007f98f4ecd1f2 in QMetaObject::activate (sender=0x1e669f0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1f10) at kernel/qobject.cpp:3069 #28 0x00007f98f4ed252f in QSingleShotTimer::timerEvent (this=0x1e669f0) at kernel/qtimer.cpp:298 #29 0x00007f98f4ec74d3 in QObject::event (this=0x1e669f0, e=0x1ed9fc8) at kernel/qobject.cpp:1082 #30 0x00007f98f40a178d in QApplicationPrivate::notify_helper (this=0x17dc490, receiver=0x1e669f0, e=0x7fff00ee8790) at kernel/qapplication.cpp:4084 #31 0x00007f98f40a997a in QApplication::notify (this=0x7fff00ee8ad0, receiver=0x1e669f0, e=0x7fff00ee8790) at kernel/qapplication.cpp:4049 #32 0x00007f98f5aa563b in KApplication::notify (this=0x7fff00ee8ad0, receiver=0x1e669f0, event=0x7fff00ee8790) at /build/buildd/kde4libs-4.2.96/kdeui/kernel/kapplication.cpp:302 #33 0x00007f98f4eb775c in QCoreApplication::notifyInternal (this=0x7fff00ee8ad0, receiver=0x1e669f0, event=0x7fff00ee8790) at kernel/qcoreapplication.cpp:602 #34 0x00007f98f4ee47f6 in QTimerInfoList::activateTimers (this=0x17e7480) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #35 0x00007f98f4ee0f0d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164 #36 0x00007f98ef2b720a in IA__g_main_context_dispatch (context=0x17e6520) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814 #37 0x00007f98ef2ba8e0 in g_main_context_iterate (context=0x17e6520, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448 #38 0x00007f98ef2baa7c in IA__g_main_context_iteration (context=0x17e6520, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511 #39 0x00007f98f4ee0e6f in QEventDispatcherGlib::processEvents (this=0x17aef70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323 #40 0x00007f98f4139bef in QGuiEventDispatcherGlib::processEvents (this=0x1d2994b, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #41 0x00007f98f4eb6002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 15632896}) at kernel/qeventloop.cpp:149 #42 0x00007f98f4eb63cd in QEventLoop::exec (this=0x7fff00ee8a40, flags={i = 15632976}) at kernel/qeventloop.cpp:200 #43 0x00007f98f4eb8694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880 #44 0x0000000000415738 in _start () Reported using DrKonqi