Bug 196410 - Kopete crashes after waking up from suspend to RAM and other situations [QMetaObject::activate, XMPP::NameResolver::resultsReady, XMPP::NameManager::provider_resolve_resultsReady]
Summary: Kopete crashes after waking up from suspend to RAM and other situations [QMet...
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (show other bugs)
Version: 0.70.90
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: triaged
: 229278 232188 248411 254211 258755 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-06-13 23:39 UTC by m.wege
Modified: 2018-10-27 02:29 UTC (History)
7 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description m.wege 2009-06-13 23:39:04 UTC 
Application that crashed: kopete
Version of the application: 0.70.90
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-020630rc6-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I was investigating what was eating so much system resources, figured out it was strigi indexing. There I noticed it hangend on a path in kopete folders -> So I stopped indexing. Still nothing better, then I saw a nepomuk stub, which took half of my resources -> reduced the process priority of this -> Shortly after Koptes usal of system ressources goes 75% and crashes. 
I am not sure if that is the exact reason why Kopete was taking so much system ressources. I also see that the Skype plugin is produces a lot of debug messages (no errors) in .xsessionerrors which may be also the reason for Kopete being slower than usal.

 -- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
[Current thread is 0 (LWP 12365)]

Thread 3 (Thread 0xb1926b90 (LWP 12855)):
#0  0xb80b4430 in __kernel_vsyscall ()
#1  0xb5da20e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb61822ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb6d8a5b2 in QWaitCondition::wait (this=0xac66850, mutex=0xac6684c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xb7658ae2 in QHostInfoAgent::run (this=0xac66840) at kernel/qhostinfo.cpp:260
#5  0xb6d8956e in QThreadPrivate::start (arg=0xac66840) at thread/qthread_unix.cpp:189
#6  0xb5d9e4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb617349e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xb03dab90 (LWP 12857)):
#0  0xb5bf6588 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#1  0xb5bf6fdd in ?? () from /usr/lib/libglib-2.0.so.0
#2  0xb5bf7268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0xb6ea91f7 in QEventDispatcherGlib::processEvents (this=0xad15a78, flags={i = -1338137912}) at kernel/qeventdispatcher_glib.cpp:326
#4  0xb6e7bdda in QEventLoop::processEvents (this=0xad15928, flags={i = -1338137848}) at kernel/qeventloop.cpp:149
#5  0xb6e7c21a in QEventLoop::exec (this=0xad15928, flags={i = -1338137800}) at kernel/qeventloop.cpp:200
#6  0xb10ac672 in XMPP::SyncThread::run (this=0xae41528) at /build/buildd/kdenetwork-4.2.90/kopete/protocols/jabber/libiris/iris/irisnet/corelib/netinterface.cpp:151
#7  0xb6d8956e in QThreadPrivate::start (arg=0xae41528) at thread/qthread_unix.cpp:189
#8  0xb5d9e4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#9  0xb617349e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb5701700 (LWP 12365)):
[KCrash Handler]
#6  QMetaObject::activate (sender=0x65006c, m=0xb111fe04, local_signal_index=0, argv=0xbfdb77ac) at kernel/qobject.cpp:3190
#7  0xb0fe5a93 in XMPP::NameResolver::resultsReady (this=0x65006c, _t1=@0xadbb4b8) at /build/buildd/kdenetwork-4.2.90/obj-i486-linux-gnu/kopete/protocols/jabber/libiris/moc_netnames.cpp:82
#8  0xb10a47cd in XMPP::NameManager::qt_metacall (this=0xad3dc20, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xadbf528)
    at /build/buildd/kdenetwork-4.2.90/kopete/protocols/jabber/libiris/iris/irisnet/corelib/netnames.cpp:661
#9  0xb6e8c6ab in QMetaCallEvent::placeMetaCall (this=0xadbb580, object=0xad3dc20) at kernel/qobject.cpp:489
#10 0xb6e8e150 in QObject::event (this=0xad3dc20, e=0xadbb580) at kernel/qobject.cpp:1118
#11 0xb6438bcc in QApplicationPrivate::notify_helper (this=0x8aa1688, receiver=0xad3dc20, e=0xadbb580) at kernel/qapplication.cpp:4057
#12 0xb6440ede in QApplication::notify (this=0xbfdb7f0c, receiver=0xad3dc20, e=0xadbb580) at kernel/qapplication.cpp:3604
#13 0xb73dbc4d in KApplication::notify (this=0xbfdb7f0c, receiver=0xad3dc20, event=0xadbb580) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kapplication.cpp:302
#14 0xb6e7d7ab in QCoreApplication::notifyInternal (this=0xbfdb7f0c, receiver=0xad3dc20, event=0xadbb580) at kernel/qcoreapplication.cpp:610
#15 0xb6e7e405 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8a70580) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#16 0xb6e7e5fd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#17 0xb6ea958f in postEventSourceDispatch (s=0x8a8dda0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#18 0xb5bf3b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb5bf70eb in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb5bf7268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb6ea91d8 in QEventDispatcherGlib::processEvents (this=0x8aa1668, flags={i = -1076134408}) at kernel/qeventdispatcher_glib.cpp:324
#22 0xb64da765 in QGuiEventDispatcherGlib::processEvents (this=0x8aa1668, flags={i = -1076134360}) at kernel/qguieventdispatcher_glib.cpp:202
#23 0xb6e7bdda in QEventLoop::processEvents (this=0xbfdb7ea0, flags={i = -1076134296}) at kernel/qeventloop.cpp:149
#24 0xb6e7c21a in QEventLoop::exec (this=0xbfdb7ea0, flags={i = -1076134232}) at kernel/qeventloop.cpp:200
#25 0xb6e7e6c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0xb6438a47 in QApplication::exec () at kernel/qapplication.cpp:3526
#27 0x08059773 in main (argc=3, argv=0xbfdb8314) at /build/buildd/kdenetwork-4.2.90/kopete/kopete/main.cpp:104

Reported using DrKonqi
Comment 1 Christoph Feck 2010-09-28 23:42:28 UTC 
*** Bug 248411 has been marked as a duplicate of this bug. ***
Comment 2 Christoph Feck 2010-09-28 23:43:11 UTC 
*** Bug 229278 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2010-09-28 23:43:47 UTC 
*** Bug 232188 has been marked as a duplicate of this bug. ***
Comment 4 Dario Andres 2010-11-16 01:02:33 UTC 
[Comment from a bug triager]
From bug 248411:
- What I was doing when the application crashed:
woke from suspend, clicked kopete's systray icon
kde 4.5, reproducible only sometimes

From bug 229278:
-- Information about the crash:
After awake from suspend and unlock kopete is crashed

From bug 232188:
Kopete`s file-transfer crashes kopete after receiving a file.
The Download works well but directly after downloading kopete crashes.
I tried out kopete from kdenetwork-4.4.1 and the latest branch-sources.

From bug 254211:
-- Information about the crash:
- What I was doing when the application crashed:
Had just logged in - Kopete starts on login
- Custom settings of the application:
Have 5 accounts set to sign in when Kopete starts - WLM, AIM, YIM, ICQ and
Jabber.
Comment 5 Dario Andres 2010-11-16 01:02:43 UTC 
*** Bug 254211 has been marked as a duplicate of this bug. ***
Comment 6 Pino Toscano 2010-12-04 11:09:31 UTC 
*** Bug 258755 has been marked as a duplicate of this bug. ***
Comment 7 Pali Rohár 2013-10-23 08:11:21 UTC 
Since KDE 4.11 Kopete has updated xmpp libiris library. Please chceck if these problems still exist.
Comment 8 Andrew Crouthamel 2018-09-25 03:43:30 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 9 Andrew Crouthamel 2018-10-27 02:29:03 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!