Version: (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages To reproduce: 1. set up gadu gadu account. 2. set status to on-line 3. set status to off-line 4. set status to on-line again - Kopete crashes I cannot produce valuable backtrace right now, because Kubuntu doesn't have packages with debuging info for backports repository.
please provide the crashes log
You can also read: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
gdb backtrace: Thread 1 (Thread 0xb58716c0 (LWP 9611)): #0 0xb322a3f7 in ?? () from /usr/lib/kde4/kopete_gadu.so #1 0xb3235301 in ?? () from /usr/lib/kde4/kopete_gadu.so #2 0xb323bc29 in ?? () from /usr/lib/kde4/kopete_gadu.so #3 0xb6edca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #4 0xb6edd7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #5 0xb3223ef7 in ?? () from /usr/lib/kde4/kopete_gadu.so #6 0xb3228b3e in ?? () from /usr/lib/kde4/kopete_gadu.so #7 0xb3229cbc in ?? () from /usr/lib/kde4/kopete_gadu.so #8 0xb6edca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #9 0xb6edd7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #10 0xb6f17633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4 #11 0xb6ee2637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4 #12 0xb656b8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #13 0xb657372e in QApplication::notify () from /usr/lib/libQtGui.so.4 #14 0xb73fdfed in KApplication::notify () from /usr/lib/libkdeui.so.5 #15 0xb6ec7e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #16 0xb6ef270a in ?? () from /usr/lib/libQtCore.so.4 #17 0xb5d336f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #18 0xb5d36da3 in ?? () from /usr/lib/libglib-2.0.so.0 #19 0xb5d36f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #20 0xb6ef2478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #21 0xb6605ea5 in ?? () from /usr/lib/libQtGui.so.4 #22 0xb6ec652a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #23 0xb6ec66ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #24 0xb6ec8da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #25 0xb656b767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #26 0x0808b97f in _start ()
What about this: http://packages.ubuntu.com/intrepid-backports/kdenetwork-dbg ?
Stupid me, I was looking for kopete-dbg. Anyway, I installed kdebase-runtime-dbg kdenetwork-dbg libqt4-dbg and kdelibs5-dbg but kopete still tells me that meaningfull backtrace cannot be created. The only thing I get is: [Thread debugging using libthread_db enabled] [New Thread 0xb58c96c0 (LWP 22118)] 0xb80c1430 in __kernel_vsyscall ()
Ok, ignore my previous comment, I was hit by some strange free space bug, here's the proper bugtrace: Program: Kopete (kopete), sygnał SIGSEGV Thread 1 (Thread 0xb58c26c0 (LWP 22581)): [KCrash Handler] #6 GaduContact::uin (this=0xa14b938) at /build/buildd/kdenetwork-4.2.0/kopete/protocols/gadu/gaducontact.cpp:88 #7 0xb32d1301 in GaduAccount::connectionSucceed (this=0xa14b938) at /build/buildd/kdenetwork-4.2.0/kopete/protocols/gadu/gaduaccount.cpp:826 #8 0xb32d7c29 in GaduAccount::qt_metacall (this=0xa14b938, _c=QMetaObject::InvokeMetaMethod, _id=52, _a=0xbfbb98f8) at /build/buildd/kdenetwork-4.2.0/obj-i486-linux-gnu/kopete/protocols/gadu/gaduaccount.moc:231 #9 0xb6f2da60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #10 0xb6f2e7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb32bfef7 in GaduSession::connectionSucceed (this=0x9c0dcf0) at /build/buildd/kdenetwork-4.2.0/obj-i486-linux-gnu/kopete/protocols/gadu/gadusession.moc:213 #12 0xb32c4b3e in GaduSession::checkDescriptor (this=0x9c0dcf0) at /build/buildd/kdenetwork-4.2.0/kopete/protocols/gadu/gadusession.cpp:774 #13 0xb32c5cbc in GaduSession::qt_metacall (this=0x9c0dcf0, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfbb9b8c) at /build/buildd/kdenetwork-4.2.0/obj-i486-linux-gnu/kopete/protocols/gadu/gadusession.moc:161 #14 0xb6f2da60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #15 0xb6f2e7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb6f68633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4 #17 0xb6f33637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4 #18 0xb65bc8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #19 0xb65c472e in QApplication::notify () from /usr/lib/libQtGui.so.4 #20 0xb744efed in KApplication::notify (this=0xbfbba1bc, receiver=0x9bbc340, event=0xbfbb9f50) at /build/buildd/kde4libs-4.2.0/kdeui/kernel/kapplication.cpp:307 #21 0xb6f18e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #22 0xb6f4370a in ?? () from /usr/lib/libQtCore.so.4 #23 0xb5d846f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0xb5d87da3 in ?? () from /usr/lib/libglib-2.0.so.0 #25 0xb5d87f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0xb6f43478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #27 0xb6656ea5 in ?? () from /usr/lib/libQtGui.so.4 #28 0xb6f1752a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #29 0xb6f176ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #30 0xb6f19da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #31 0xb65bc767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #32 0x0808b97f in main (argc=3, argv=0xbfbba5a4) at /build/buildd/kdenetwork-4.2.0/kopete/kopete/main.cpp:102
Thanks!. This seems to be very related to bug 174513 (crashing on the same line)
I can confirm it happend also in Kopete 0.70.2, KDE 4.2.2 in Fedora 11 beta. My backtrace: Application: Kopete (kopete), signal SIGSEGV [Current thread is 1 (Thread 0xb800d780 (LWP 3109))] Thread 2 (Thread 0xb5acbb70 (LWP 3115)): #0 0x008d4416 in __kernel_vsyscall () #1 0x0032a005 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:122 #2 0x074364a7 in QWaitConditionPrivate::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:87 #3 QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159 #4 0x071bccaa in QHostInfoAgent::run (this=0x903cfc8) at kernel/qhostinfo.cpp:260 #5 0x0743543e in QThreadPrivate::start (arg=0x903cfc8) at thread/qthread_unix.cpp:189 #6 0x00325965 in start_thread (arg=0xb5acbb70) at pthread_create.c:297 #7 0x0044783e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb800d780 (LWP 3109)): [KCrash Handler] #6 GaduContact::uin (this=0x8f3fbf0) at /usr/src/debug/kdenetwork-4.2.2/kopete/protocols/gadu/gaducontact.cpp:89 #7 0x06b234b2 in GaduAccount::connectionSucceed (this=0x8f3fbf0) at /usr/src/debug/kdenetwork-4.2.2/kopete/protocols/gadu/gaduaccount.cpp:826 #8 0x06b2949c in GaduAccount::qt_metacall (this=0x8f3fbf0, _c=QMetaObject::InvokeMetaMethod, _id=52, _a=0xbff351fc) at /usr/src/debug/kdenetwork-4.2.2/i586-redhat-linux-gnu/kopete/protocols/gadu/gaduaccount.moc:232 #9 0x0753db68 in QMetaObject::activate (sender=0x8e04360, from_signal_index=10, to_signal_index=10, argv=0x0) at kernel/qobject.cpp:3069 #10 0x0753e802 in QMetaObject::activate (sender=0x8e04360, m=0x6b4697c, local_signal_index=6, argv=0x0) at kernel/qobject.cpp:3143 #11 0x06b16ce7 in GaduSession::connectionSucceed (this=0x8e04360) at /usr/src/debug/kdenetwork-4.2.2/i586-redhat-linux-gnu/kopete/protocols/gadu/gadusession.moc:215 #12 0x06b18d40 in GaduSession::checkDescriptor (this=0x8e04360) at /usr/src/debug/kdenetwork-4.2.2/kopete/protocols/gadu/gadusession.cpp:774 #13 0x06b1a335 in GaduSession::qt_metacall (this=0x8e04360, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbff353e8) at /usr/src/debug/kdenetwork-4.2.2/i586-redhat-linux-gnu/kopete/protocols/gadu/gadusession.moc:162 #14 0x0753db68 in QMetaObject::activate (sender=0x968df38, from_signal_index=4, to_signal_index=4, argv=0xbff353e8) at kernel/qobject.cpp:3069 #15 0x0753e802 in QMetaObject::activate (sender=0x968df38, m=0x7619b30, local_signal_index=0, argv=0xbff353e8) at kernel/qobject.cpp:3143 #16 0x075789a3 in QSocketNotifier::activated (this=0x968df38, _t1=21) at .moc/release-shared/moc_qsocketnotifier.cpp:83 #17 0x07542607 in QSocketNotifier::event (this=0x968df38, e=0xbff357a4) at kernel/qsocketnotifier.cpp:316 #18 0x021269bc in QApplicationPrivate::notify_helper (this=0x8b01928, receiver=0x968df38, e=0xbff357a4) at kernel/qapplication.cpp:4084 #19 0x0212dde4 in QApplication::notify (this=0xbff35ae4, receiver=0x968df38, e=0xbff357a4) at kernel/qapplication.cpp:4049 #20 0x07db12ca in KApplication::notify (this=0xbff35ae4, receiver=0x968df38, event=0xbff357a4) at /usr/src/debug/kdelibs-4.2.2/kdeui/kernel/kapplication.cpp:307 #21 0x0752793b in QCoreApplication::notifyInternal (this=0xbff35ae4, receiver=0x968df38, event=0xbff357a4) at kernel/qcoreapplication.cpp:602 #22 0x0755304a in QCoreApplication::sendEvent (event=<value optimized out>, receiver=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:213 #23 socketNotifierSourceDispatch (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:109 #24 0x00aca188 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #25 0x00acd798 in ?? () from /lib/libglib-2.0.so.0 #26 0x00acd90a in g_main_context_iteration () from /lib/libglib-2.0.so.0 #27 0x07552dac in QEventDispatcherGlib::processEvents (this=0x8ae3440, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:323 #28 0x021c64f5 in QGuiEventDispatcherGlib::processEvents (this=0x8ae3440, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202 #29 0x07525ec9 in QEventLoop::processEvents (this=0xbff35a44, flags=) at kernel/qeventloop.cpp:149 #30 0x07526312 in QEventLoop::exec (this=0xbff35a44, flags={i = 0}) at kernel/qeventloop.cpp:200 #31 0x0752869f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880 #32 0x02126837 in QApplication::exec () at kernel/qapplication.cpp:3553 #33 0x080882c0 in main (argc=3, argv=0xbff35ef4) at /usr/src/debug/kdenetwork-4.2.2/kopete/kopete/main.cpp:102
I forgot how to trigger the crash I experience. Play the audio stream in amarok, when the connection is dropped, click stop then play. It causes playing to hang, play button is pressed but no progres in timeline, timers and no music. Also I can't switch to any other media (even local). The app itself is still responding, I can add things to playlist browse collection, local resources etc... I have to close amarok, then crash occurs. After the crash I can start the app again and it works. My guess is phonon haven't noticed the connection breakdown, maybe some kind of connction timeout would be a cure?
This crash report is at least 3 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources. If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports (To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!