Summary: | Kopete Crash after I Suspend My Laptop | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | Lissandro Sosa <lissandro.sosa> |
Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | eliel.resende2010, trip.florissen, wittemar |
Priority: | NOR | ||
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Lissandro Sosa
2010-04-20 17:09:33 UTC
*** Bug 238432 has been marked as a duplicate of this bug. *** Created attachment 59532 [details]
New crash information added by DrKonqi
kopete (1.0.80) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
receiving a chat message from a WLM contact.
on arival the message is shortly (max 0.5 sec)displayed and then kopete crashes
-- Backtrace (Reduced):
#6 0x00007fc2be633902 in setSharable (sharable=true, this=<optimized out>) at /usr/include/QtCore/qlinkedlist.h:95
#7 ~QMutableLinkedListIterator (this=<optimized out>, __in_chrg=<optimized out>) at /usr/include/QtCore/qlinkedlist.h:514
#8 WlmChatManager::slotGotEmoticonFile (this=0xc23c00, conn=0xc24df0, sessionID=<optimized out>, alias=<optimized out>, file=<optimized out>) at /usr/src/debug/kdenetwork-4.6.2/kopete/protocols/wlm/wlmchatmanager.cpp:621
#9 0x00007fc2be6343cf in WlmChatManager::qt_metacall (this=0xc23c00, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffc1124dc0) at /usr/src/debug/kdenetwork-4.6.2/build/kopete/protocols/wlm/wlmchatmanager.moc:133
[...]
#11 0x00007fc2be62cbe1 in Callbacks::slotGotEmoticonFile (this=<optimized out>, _t1=0xc24df0, _t2=<optimized out>, _t3=<optimized out>, _t4=<optimized out>) at /usr/src/debug/kdenetwork-4.6.2/build/kopete/protocols/wlm/wlmlibmsn.moc:523
*** Bug 301317 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! |