Summary: | Kopete crashes after waking up from suspend to RAM and other situations [QMetaObject::activate, XMPP::NameResolver::resultsReady, XMPP::NameManager::provider_resolve_resultsReady] | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | m.wege |
Component: | Jabber Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andresbajotierra, johann-nikolaus, markotahal, pali.rohar, robert.wenner, rvalkass, ToSa65 |
Priority: | NOR | Keywords: | triaged |
Version: | 0.70.90 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
m.wege
2009-06-13 23:39:04 UTC
*** Bug 248411 has been marked as a duplicate of this bug. *** *** Bug 229278 has been marked as a duplicate of this bug. *** *** Bug 232188 has been marked as a duplicate of this bug. *** [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. *** Bug 254211 has been marked as a duplicate of this bug. *** *** Bug 258755 has been marked as a duplicate of this bug. *** Since KDE 4.11 Kopete has updated xmpp libiris library. Please chceck if these problems still exist. 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! 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! |