Version: (using Devel) OS: Linux Installed from: Compiled sources Kopete version 0.60.81 Crash where connect to jabber server after enter the password. Server is local, no ssl, login like 'aaaa.ggg@jabb', server changet to ip-address manually. No crash report. Said only: The application Kopete (kopete) crashed and caused the signal 11 (SIGSEGV). (no debugging symbols found)
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
I'm getting the same problem with version 0.60.4 in KDE 4.1.4. I get logged into the jabber server and I see the list of contacts, and then kopete crashes. Here's the backtrace: Application: Kopete (kopete), signal SIGSEGV [Current thread is 0 (LWP 11602)] Thread 2 (Thread 0xb324fb90 (LWP 11606)): #0 0xb600c54a in clock_gettime () from /lib/tls/i686/cmov/librt.so.1 #1 0xb75d50ab in ?? () from /usr/lib/libQtCore.so.4 #2 0xb75d5281 in ?? () from /usr/lib/libQtCore.so.4 #3 0xb75d6e3c in ?? () from /usr/lib/libQtCore.so.4 #4 0xb75d365a in ?? () from /usr/lib/libQtCore.so.4 #5 0xb5f8d602 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #6 0xb5f8da8a in ?? () from /usr/lib/libglib-2.0.so.0 #7 0xb5f8df61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #8 0xb75d3497 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #9 0xb75a752a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #10 0xb75a76ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #11 0xb3554e59 in QCA::SyncThread::run () from /usr/lib/libqca.so.2 #12 0xb74b86ae in ?? () from /usr/lib/libQtCore.so.4 #13 0xb5f3d50f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #14 0xb64e27ee in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb59316c0 (LWP 11602)): [KCrash Handler] #6 0xb6479b71 in memcpy () from /lib/tls/i686/cmov/libc.so.6 #7 0xb77f75c0 in KNetwork::Internal::KSocketBuffer::sendTo (this=0x99a6ca0, dev=0x99a7958, len=-1) at /usr/include/bits/string3.h:52 #8 0xb77e1520 in KNetwork::KBufferedSocket::slotWriteActivity (this=0x99814a0) at /build/buildd/kde4libs-4.1.4/kdecore/network/k3bufferedsocket.cpp:349 #9 0xb77e1350 in KNetwork::KBufferedSocket::qt_metacall (this=0x99814a0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfa7f11c) at /build/buildd/kde4libs-4.1.4/obj-i486-linux-gnu/kdecore/k3bufferedsocket.moc:68 #10 0xb75bda60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb75be7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb75f8633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4 #13 0xb75c3637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4 #14 0xb6a898ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #15 0xb6a9172e in QApplication::notify () from /usr/lib/libQtGui.so.4 #16 0xb7ae8d1d in KApplication::notify (this=0xbfa7f74c, receiver=0x9acccd8, event=0xbfa7f4e0) at /build/buildd/kde4libs-4.1.4/kdeui/kernel/kapplication.cpp:311 #17 0xb75a8e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #18 0xb75d370a in ?? () from /usr/lib/libQtCore.so.4 #19 0xb5f8a6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #20 0xb5f8dda3 in ?? () from /usr/lib/libglib-2.0.so.0 #21 0xb5f8df61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #22 0xb75d3478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #23 0xb6b23ea5 in ?? () from /usr/lib/libQtGui.so.4 #24 0xb75a752a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #25 0xb75a76ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #26 0xb75a9da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #27 0xb6a89767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #28 0x0808aa3f in main (argc=3, argv=0xbfa7fb34) at /build/buildd/kdenetwork-4.1.4/kopete/kopete/main.cpp:102
@Beirne: your crash may be unrelated to the original report one (as we don't have the backtrace). Your crash is probably bug 170376
No useful backtrace was provided for this bug (see comment #1). Closing this bug report.
I have this issue with Kubuntu 8.10 Intrepid Official distribution sources. This normally happens when I shutdown PC without first closing Kopete, or on every reboot or startup (because kopete automatically starts in KDE4) and when I try to log in (jabber server with certs). This start when i try to log in. -------- Application: Kopete (kopete), signal SIGSEGV (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb592f6c0 (LWP 6331)] [New Thread 0xb1db6b90 (LWP 6669)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb6477b71 in memcpy () from /lib/tls/i686/cmov/libc.so.6 #7 0xb7865360 in ?? () from /usr/lib/libkdecore.so.5 #8 0xb784f2c0 in KNetwork::KBufferedSocket::slotWriteActivity () from /usr/lib/libkdecore.so.5 #9 0xb784f0f0 in KNetwork::KBufferedSocket::qt_metacall () from /usr/lib/libkdecore.so.5 #10 0xb75bba60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb75bc7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb75f6633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4 #13 0xb75c1637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4 #14 0xb6a888ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #15 0xb6a9072e in QApplication::notify () from /usr/lib/libQtGui.so.4 #16 0xb7ae672d in KApplication::notify () from /usr/lib/libkdeui.so.5 #17 0xb75a6e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #18 0xb75d170a in ?? () from /usr/lib/libQtCore.so.4 #19 0xb5f886f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #20 0xb5f8bda3 in ?? () from /usr/lib/libglib-2.0.so.0 #21 0xb5f8bf61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #22 0xb75d1478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #23 0xb6b22ea5 in ?? () from /usr/lib/libQtGui.so.4 #24 0xb75a552a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #25 0xb75a56ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #26 0xb75a7da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #27 0xb6a88767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #28 0x0808aa6f in _start () #0 0xb8078430 in __kernel_vsyscall ()
@perish: your crash is another bug, and it's already fixed in KDE4.2.0 :)
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 mark the bug 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!
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!