| Summary: | kopete asking for passwords after wallet password wasn't provided | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Kristjan Ugrin <kristjan.ugrin> |
| Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | axelmasok, bodom, bugreporting, daniel, eduardhc, frederic.coiffier, joker777vs.666, lemma, Mathias.Homann, miklcct, mss, ossi, peet21, shentey |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Kristjan Ugrin
2010-02-11 10:35:12 UTC
*** Bug 228153 has been marked as a duplicate of this bug. *** *** Bug 229576 has been marked as a duplicate of this bug. *** I solved this here on Kubuntu Lucid by removing all kopete and kwallet config files from .kde/share/config/ and .kde/share/apps/. It's always old config files nowdays that bite me. It was a fresh install not an upgrade but /home was existing. This bug affects also me on kubuntu lucid 10.04 Kopete 1.0.0 on Kde 4.4.2 This is odd. I first thought it was fixed in KDE 4.4.3 because on my recently reinstalled notebook (Kubuntu Lucid) it doesn't happen. Today I upgraded my workstation to 4.4.3 as well (via <http://www.kubuntu.org/news/kde-sc-4.4.3>, it was first installed with Karmic I think) and it still happens. So I guess as Axel pointed out, it is some old config hanging around and confusing Kopete (or the wallet subsystem). Or it might be that my workstation is 64 bit and my notebook 32? Or that I have two Jabber accounts on my workstation and only one on my notebook? Guess I won't find out until I purged the config on my workstation, not something I'm currently in the mood to do. So a workaround for now seem to be an upgrade to 4.4.3 and purging your config data. I just had a look at this bug. The behaviour stems from the timeoutTimer inside Kopete::WalletManager::Private which should be removed altogether. In my opinion no application should put timeouts on calls to KWallet. A timeout means that the user isn't around to answer the KWallet dialog. Cancelling the dialog (which is not actually possible so the dialog stays visible) means that the application will have to reprompt the user for the password (a dialog the user won't be able to answer either if he's not around). What should work is removing timeoutTimer and all calls to it altogether (would of course need proper testing to see if everything still works). *** Bug 243580 has been marked as a duplicate of this bug. *** *** Bug 229366 has been marked as a duplicate of this bug. *** *** Bug 236964 has been marked as a duplicate of this bug. *** *** Bug 238402 has been marked as a duplicate of this bug. *** *** Bug 234418 has been marked as a duplicate of this bug. *** I recently upgraded to 4.5 RC2 and now at least the behaviour is consistent: Both my notebook and my workstation do ask for an account password if I'm not quick enough to open the wallet. Additionally (was also mentioned in some of the bugs I duped) does it forget the password for my Jabber account when this happens. fixed in r1151002 by beschow for kde 4.6 kde 4.6...when is that going to be released? is there a chance to backport this into 4.5 or 4.5.1? already backported to 4.5 in r1151086 ;-) |