Upon each login I must edit the IM account associated with my Gmail account to set the password or Telepathy won't connect. I only have one IM account configured. Further, if I don't go into the settings and set the password again, when I attempt to set myself to Available I am prompted to enter the password; though, even entering the correct password through this method does not result in a connection being made, but being prompted endlessly for the credentials once again. Reproducible: Always Steps to Reproduce: 1. Setup Gmail IM account 2. Logout 3. Upon next login, attempts to connect fail, see the details for more information. Actual Results: My account credentials are not remembered appropriately; though, the interface shows password characters at the appropriate length. Expected Results: That I should be able to login to my account without setting up the account each time.
Provided is the bug reported at launchpad as well: https://bugs.launchpad.net/ubuntu/+source/ktp-accounts-kcm/+bug/1446371
Same here with v15.04.1
Fully reproducible here with 15.8.1, the password window pops up every time I even change presence. Unfortunately there are no decent error messages at all (also not in ~/.xession-errors), kwallet has two maps with the password stored in them. Gentoo, x86_64, KF 5.14, KDE applications 15.8.1
@Fuchs - can you please run "ktp-auth-handler --persist" from Konsole (somewhere in libexec) and post the output here please? Check for sensitive data being printed.
Sure, what I got was: New job started. 1 jobs currently running Unknown signature value: 795 Unknown signature value: 795 Unknown signature value: 795 Unknown signature value: 794 Unknown signature value: 795 Unknown signature value: 795 Unknown signature value: 795 Unknown signature value: 795 Unknown signature value: 795 Unknown signature value: 795 Unknown signature value: 795 Unknown signature value: 7 Job finished. 0 jobs currently running New job started. 1 jobs currently running 14 ("SCRAM-SHA-1", "DIGEST-MD5", "PLAIN", "X-TELEPATHY-PASSWORD") Starting Password auth Requesting password connection-manager.cpp 106 setupSocketConnection p2p error: QDBusError("org.freedesktop.DBus.Error.FileNotFound", "Failed to connect to socket /run/user/1000/signond/socket: Datei oder Verzeichnis nicht gefunden") 1 connection-manager.cpp 132 init Peer connection unavailable, activating service identityimpl.cpp 96 updateState Updating state: "PendingRegistration" SignOn::IdentityImpl(0x918000) authsessionimpl.cpp 94 initInterface authsessionimpl.cpp 94 initInterface connection-manager.cpp 106 setupSocketConnection p2p error: QDBusError("org.freedesktop.DBus.Error.FileNotFound", "Failed to connect to socket /run/user/1000/signond/socket: Datei oder Verzeichnis nicht gefunden") 1 connection-manager.cpp 150 init Connected to "qt_default_session_bus" identityimpl.cpp 96 updateState Updating state: "Ready" SignOn::IdentityImpl(0x918000) authsessionimpl.cpp 184 errorSlot QDBusError("com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction", "userActionFinished error: 10") "userActionFinished error: 10" Credentials job error: "userActionFinished error: 10" Prompting for password Saving password in SSO identityimpl.cpp 96 updateState Updating state: "PendingRegistration" SignOn::IdentityImpl(0x750c20) identityimpl.cpp 172 storeCredentials Storing credentials identityimpl.cpp 96 updateState Updating state: "Ready" SignOn::IdentityImpl(0x750c20) Authenticating... Authentication handshake Authentication succeeded identityimpl.cpp 96 updateState Updating state: "NeedsUpdate" SignOn::IdentityImpl(0x750c20) identityimpl.cpp 96 updateState Updating state: "PendingUpdate" SignOn::IdentityImpl(0x750c20) identityimpl.cpp 442 infoUpdated SERVER INFO UPDATED. NeedsUpdate " 14 " identityimpl.cpp 96 updateState Updating state: "NeedsUpdate" SignOn::IdentityImpl(0x750c20) identityimpl.cpp 96 updateState Updating state: "PendingUpdate" SignOn::IdentityImpl(0x750c20) identityimpl.cpp 442 infoUpdated SERVER INFO UPDATED. NeedsUpdate " 14 " identityimpl.cpp 345 storeCredentialsReply stored id: 14 old id: 14 account-service.cpp: 169 onChanged account.cpp: 626 account_store_cb Saved accunt ID: 14 Account credentials synchronisation finished identityimpl.cpp 381 getInfoReply QMap(("ACL", QVariant(QStringList, ("*")) ) ( "AuthMethods" , QVariant(QDBusArgument, ) ) ( "Caption" , QVariant(QString, "fuchs@...") ) ( "Id" , QVariant(uint, 14) ) ( "Owner" , QVariant(QStringList, ()) ) ( "Realms" , QVariant(QStringList, ()) ) ( "RefCount" , QVariant(int, 0) ) ( "StoreSecret" , QVariant(bool, true) ) ( "Type" , QVariant(int, 1) ) ( "UserName" , QVariant(QString, "fuchs@...") ) ( "UserNameSecret" , QVariant(bool, false) ) ( "Validated" , QVariant(bool, false) ) ) identityimpl.cpp 96 updateState Updating state: "Ready" SignOn::IdentityImpl(0x750c20) identityimpl.cpp 381 getInfoReply QMap(("ACL", QVariant(QStringList, ("*")) ) ( "AuthMethods" , QVariant(QDBusArgument, ) ) ( "Caption" , QVariant(QString, "fuchs@...") ) ( "Id" , QVariant(uint, 14) ) ( "Owner" , QVariant(QStringList, ()) ) ( "Realms" , QVariant(QStringList, ()) ) ( "RefCount" , QVariant(int, 0) ) ( "StoreSecret" , QVariant(bool, true) ) ( "Type" , QVariant(int, 1) ) ( "UserName" , QVariant(QString, "fuchs@...") ) ( "UserNameSecret" , QVariant(bool, false) ) ( "Validated" , QVariant(bool, false) ) ) identityimpl.cpp 96 updateState Updating state: "Ready" SignOn::IdentityImpl(0x750c20) Job finished. 0 jobs currently running Interestingly enough, after cleaning up the ktp-, telepathy and kaccounts related files and folders in ~/.config and ~/.local in an attempt to solve this, I so far couldn't reproduce it anymore. So maybe people reporting here might want to try that, too (create backups first)
> "userActionFinished error: 10" I think this had something to do with kwallet (upstream error codes..tsk tsk). Can you guys check if you have signon-kwallet-extension package installed _and_ are you using kwallet?
I do use kwallet, yes. If you are talking about the PAM module: I have that installed and configured as optional in PAM, yes. If you are talking about something else: no idea, let me know how to check and I shall.
signon-kwallet-extension package.
Ah, yes, that is installed. Probably was a dependency, as I don't remember installing or configuring that.
I've looked through the signond code and the error "10" means "we don't have password stored for this account and we cannot prompt for it". So. The passwords don't make it to the wallet and/or back from wallet. Can anybody still reproduce this problem reliably?
after running "ktp-auth-handler --persist" and entering all passwords everything seems to work fine, even after a reboot cycle. there were also no errors showing up. However, signon asks for a password after every login even thoug there is no password specified in kwallet kdewallet holds for telepathy-kde only three passwords. but there should be five. I have no idea where the other passwords are stored.
Ok, status update: After a reboot cycle I'm being asked for every account password. I cancel all dialogs. after running ktp-auth-handler --persist manually and trying to go online again, everything works fine. logon-race-condition?
Is this still happening? Please set the bug status.
Hi, it's okay for me, can't speak for the others, though. Thanks :)
Still getting this with gmail - setup an account and save password. Every few minutes I get asked for my password again even though I've set it to save the password.
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!