Bug 173804 - Kopete cannot connect to any account if the KDE wallet is not activated [regression]
Summary: Kopete cannot connect to any account if the KDE wallet is not activated [regr...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kopete
Classification: Unmaintained
Component: libkopete (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-29 02:12 UTC by Médéric Boquien
Modified: 2024-09-18 18:27 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Médéric Boquien 2008-10-29 02:12:37 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

In KDE SVN trunk r876593 if the KDE wallet is not activated, kopete cannot connect to any account. When i try to connect Kopete's GUI does not show any action (the icons of the various accounts remain grey instead of blinking) and the output in the terminal is the following:

kopete(23591)/kopete (msn) MSNAccount::setOnlineStatus: "Online"
kopete(23591)/libkopete KopetePasswordRequest::begin:
kopete(23591)/libkopete Kopete::WalletManager::openWalletInner:  about to open wallet async
kopete(23591): The kwalletd service has been disabled
kopete(23591): The kwalletd service has been disabled
kopete(23591): The kwalletd service has been disabled
kopete(23591): The kwalletd service has been disabled
kopete(23591): The kwalletd service has been disabled
kopete(23591): The kwalletd service has been disabled
QObject::connect: Cannot connect (null)::walletOpened(bool) to Kopete::WalletManager::slotWalletChangedStatus()

Note that even if kopete is not given any password when creating the account, it does not even ask for it.

If the KDE wallet is activated everything works as expected.

Steps to reproduce:

1) create a new account
2) when asked if kwallet should handle the password, refuse
3) try to connect, nothing happens.
4) activate kwallet, try to connect, it works.

Note, this regression has been confirmed by Michael Leupold (lemma).

Thanks.
Comment 1 Médéric Boquien 2008-10-29 02:58:28 UTC
To be more clear, it works when kwallet manages the password (asking for the kwallet password at the beginning of the session) and it does not work when kwallet does not manage the password (to connect without being asked a password).

I had that it worked fine with 4.1. It broke when i upgraded to trunk.

Thanks.
Comment 2 Matt Rogers 2009-09-06 04:30:45 UTC
Does this still happen with later releases?
Comment 3 Justin Zobel 2021-03-09 22:41:26 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 4 Christoph Cullmann 2024-09-18 18:27:56 UTC
Dear user, unfortunately Kopete is no longer maintained.

Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.