| Summary: | Frozen Kopete blocks other applications (via KWallet?) | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Malte S. Stretz <mss> |
| Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | finex, lemma, me, ochominutosdearco |
| Priority: | NOR | Keywords: | triaged |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Malte S. Stretz
2006-10-11 12:19:14 UTC
Do you happen to have kdesvn installed? Nope, don't think so. I had it once installed but removed it again and updated KDE in between so I don't think I've got anything of it left. Ah-ha! This is caused by bug 128845. Ie. Kopete sometimes freezes (reason still unknown), and (I guess) blocks DBus or Konqueror tries to query some info from Kopete or some part of KDE Kopete currently blocks. Whatever, as soon as I kill kopete when it is in its freeze-frenzy, Konqueror works again. It's probably the wallet which is blocking. I'm marking it as a duplicate then. *** This bug has been marked as a duplicate of 128845 *** I reopen this bug an reassign it to Kopete because bug 128845 is actually another bug and this is just a side-effect. This not only affects Kopete but also other applications, like KMail. In bug 128845 I wrote: > I've got both Kopete and KMail automatically started with my session. In > maybe 80% of all logins both don't start up; Kopete adds its icon to the > tray but nothing happens (and the icon isn't refreshed so when the tray was > hidden I've just got an empty space) and KMail doesn't start up. > > If I go and kill kopete, KMail comes up and KWallet asks me for my password. > If I try it the other way round and kill KMail, Kopete doesn't start though. > The same is true if I start Kopete while KMail is busy/blocked (eg. > decrypting a mail). > Judging from the DCOP debug output there might be a deadlock somewhere; the > following I got when I killed KMail the last time: > > DCOP aborting (delayed) call from 'anonymous-10624' to 'kmail' > DCOP aborting while waiting for answer from 'kopete' Now that I "fixed" bug 128845, Kopete still slows down KMail start because the statistics plugin takes some while to load and while it does so, KMail doesn't start either. My guess is that Kopete blocks the KWallet on startup (even though the password dialog doesn't appear until the plugins are loaded) and then loads its plugins, blocking all other apps which try to access the wallet. If the plugins take long to load (or freeze), a bunch of other apps are frozen, too. I'm not sure if this is a Kopete bug or a general KWallet issue, please reassign accordingly. (I'm not even sure KWallet is the culprit but it's my best guess.) *grmf* changing the package doesn't reassign the bug... Please rebuild with debug enabled and post the console logs from Kopete when it hangs the wallet. @Malte: can you follow the suggestion of Will Stephenson? It could be useful. Thanks! Debug logs would be useful if you still see the problem with KDE4. Thanks! I haven't seen this on my KDE4 install yet, but I haven't converted my chat history yet. It still happens in 0.12.7 though if anybody cares :) I haven't upgraded yet but got pissed enough by the hang that I strace'd kopete and found out that the statistics plugin and not the history one goes mad. Now at least I know what data I have to import :) I just have this problem. My kmail was not able to use kwallet and i opened a bug: Bug 319138 Then i rode this bug and tryed to start kde without kopete. And that allowed me to use kmail without problems. Im thinking something related to this bug can be still making problems today. 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! |