Summary: | Kopete crashes when it is left on its own | ||
---|---|---|---|
Product: | [Applications] kopete | Reporter: | rnet723 |
Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | k0l0b0k.void, rnet723, tbe |
Priority: | NOR | ||
Version: | 1.0.80 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
rnet723
2011-04-19 12:48:14 UTC
Created attachment 59568 [details]
New crash information added by DrKonqi
kopete (1.0.80) on KDE Platform 4.6.2 (4.6.2) "release 3" using Qt 4.7.2
- What I was doing when the application crashed:
A new crash. Kopete was left running online for 5 hours with jabber conference opened. When I've returned to computer I saw DrKonqi's crash dialog.
- Custom settings of the application:
There were 2 jabber and 1 skype accounts online.
-- Backtrace (Reduced):
#6 indexOfMethodRelative<4> (baseObject=0x7fff9795b298, signal=0x7f27cccef459 "accepted(Kopete::MessageEvent*)", normalizeStringData=false) at kernel/qmetaobject.cpp:498
#7 QMetaObjectPrivate::indexOfSignalRelative (baseObject=0x7fff9795b298, signal=0x7f27cccef459 "accepted(Kopete::MessageEvent*)", normalizeStringData=false) at kernel/qmetaobject.cpp:601
#8 0x00007f27cb0d7a53 in QObject::connect (sender=0x312a0d0, signal=0x7f27cccef459 "accepted(Kopete::MessageEvent*)", receiver=0x1e5b530, method=0x7f27cccef430 "1messageAccepted(Kopete::MessageEvent*)", type=Qt::AutoConnection) at kernel/qobject.cpp:2492
#9 0x00007f27ccca5a03 in Kopete::MessageHandler::handleMessageInternal (this=0x1e5b530, event=0x312a0d0) at /usr/src/debug/kdenetwork-4.6.2/kopete/libkopete/kopetemessagehandler.cpp:59
#10 0x00007f27ccca4bf2 in Kopete::ProcessMessageTask::qt_metacall (this=0x291c630, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=<value optimized out>) at /usr/src/debug/kdenetwork-4.6.2/build/kopete/libkopete/kopetemessagehandlerchain.moc:124
Created attachment 69143 [details]
New crash information added by DrKonqi
kopete (1.2.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.8.0
- What I was doing when the application crashed:
I have just joined the second jabber conference chat. After a while kopete is crashing.
-- Backtrace (Reduced):
#7 0x00007fd7fa215c58 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () from /usr/lib64/qt4/libQtCore.so.4
#8 0x00007fd7fd5f6843 in Kopete::MessageHandler::handleMessageInternal(Kopete::MessageEvent*) () from /usr/lib64/libkopete.so.4
#9 0x00007fd7fa2113b6 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007fd7f90fe324 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#11 0x00007fd7f9102f1f in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
*** Bug 279919 has been marked as a duplicate of this bug. *** Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. 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 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! |