Bug 187546 - kopete always crash on exit after (re)connecting Gadu-Gadu protocol
Summary: kopete always crash on exit after (re)connecting Gadu-Gadu protocol
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: Gadu-Gadu Plugin (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2009-03-18 20:08 UTC by Michał S.
Modified: 2018-10-27 02:20 UTC (History)
3 users (show)

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 Michał S. 2009-03-18 20:08:51 UTC
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    SuSE RPMs

When I'am exiting Kopete just after reconnecting Gadu-Gadu protocol/plugin (I mean disconnect making me unavailable and then connecting making me available to chat) program crashes with the signal 11 (SIGSEGV). Below is a backtrace:

Program: Kopete (kopete), sygnał SIGSEGV
[Current thread is 0 (LWP 9336)]

Thread 2 (Thread 0xb2727b90 (LWP 9349)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6ddac15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb6e38862 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#3  0xb76951f2 in ?? () from /usr/lib/libQtNetwork.so.4
#4  0xb6e3784e in ?? () from /usr/lib/libQtCore.so.4
#5  0xb6dd7175 in start_thread () from /lib/libpthread.so.0
#6  0xb630bdae in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5888ac0 (LWP 9336)):
[KCrash Handler]
#6  0x00000025 in ?? ()
#7  0xb6f35a7c in qDeleteInEventHandler () from /usr/lib/libQtCore.so.4
#8  0xb6f3747b in QObject::event () from /usr/lib/libQtCore.so.4
#9  0xb65c182c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#10 0xb65c96ce in QApplication::notify () from /usr/lib/libQtGui.so.4
#11 0xb74435fd in KApplication::notify () from /usr/lib/libkdeui.so.5
#12 0xb6f27a71 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#13 0xb6f286e5 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#14 0xb6f288dd in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#15 0xb6f525bf in ?? () from /usr/lib/libQtCore.so.4
#16 0xb5da82d9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0xb5dab85b in ?? () from /usr/lib/libglib-2.0.so.0
#18 0xb5dab9d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0xb6f52208 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#20 0xb665a8c5 in ?? () from /usr/lib/libQtGui.so.4
#21 0xb6f2614a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#22 0xb6f2630a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#23 0xb6f289a5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#24 0xb65c16a7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#25 0x0808987f in _start ()

The SAME problem I've experienced with KDE 4.1 and earlier with 3.5.8-9.
Comment 1 Dario Andres 2009-03-19 13:35:27 UTC
Can you install the "kdenetwork-debuginfo" package and post a new backtrace here?
Thanks
Comment 2 Michał S. 2009-03-21 10:23:52 UTC
Here you are:
----------------------------------------------------------
Program: Kopete (kopete), sygnał SIGSEGV
[?1034h[Thread debugging using libthread_db enabled]
[Current thread is 0 (LWP 3485)]

Thread 3 (Thread 0xb3dcfb90 (LWP 3494)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb61e7ed1 in select () from /lib/libc.so.6
#2  0xb6de9e77 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb6d1a84e in ?? () from /usr/lib/libQtCore.so.4
#4  0xb6cba175 in start_thread () from /lib/libpthread.so.0
#5  0xb61eedae in clone () from /lib/libc.so.6

Thread 2 (Thread 0xb1e04b90 (LWP 3526)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6cbdc15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb6d1b862 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#3  0xb75781f2 in ?? () from /usr/lib/libQtNetwork.so.4
#4  0xb6d1a84e in ?? () from /usr/lib/libQtCore.so.4
#5  0xb6cba175 in start_thread () from /lib/libpthread.so.0
#6  0xb61eedae in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb576bac0 (LWP 3485)):
[KCrash Handler]
#6  0x033becd5 in ?? ()
#7  0xb6e18a7c in qDeleteInEventHandler () from /usr/lib/libQtCore.so.4
#8  0xb6e1a47b in QObject::event () from /usr/lib/libQtCore.so.4
#9  0xb64a482c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#10 0xb64ac6ce in QApplication::notify () from /usr/lib/libQtGui.so.4
#11 0xb73265fd in KApplication::notify () from /usr/lib/libkdeui.so.5
#12 0xb6e0aa71 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#13 0xb6e0b6e5 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#14 0xb6e0b8dd in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#15 0xb6e355bf in ?? () from /usr/lib/libQtCore.so.4
#16 0xb5c8b2d9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0xb5c8e85b in ?? () from /usr/lib/libglib-2.0.so.0
#18 0xb5c8e9d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0xb6e35208 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#20 0xb653d8c5 in ?? () from /usr/lib/libQtGui.so.4
#21 0xb6e0914a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#22 0xb6e0930a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#23 0xb6e0b9a5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#24 0xb64a46a7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#25 0x0808987f in main (argc=3, argv=0xbfa21074) at /usr/src/debug/kdenetwork-4.2.1/kopete/kopete/main.cpp:102(In reply to comment #1)
> Can you install the "kdenetwork-debuginfo" package and post a new backtrace
> here?
> Thanks
Comment 3 Christoph Feck 2013-09-12 21:36:06 UTC
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)
Comment 4 Andrew Crouthamel 2018-09-24 02:17:16 UTC
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!
Comment 5 Andrew Crouthamel 2018-10-27 02:20:15 UTC
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!