I have a google account configured so I can chat using KTP. I recently disabled that (Well, I unchecked the "Chat" feature for the account in the KCM, I assume that disables it?), set my status to Offline and enabled "Restore last presence on login". Now I changed the password for my google account a while ago, and every time I log in or unlock my screen I get a password prompt from KTP for my google account, even though I'm supposed to be offline and the resource should be disabled, so there should be no reason why it would try to connect. Reproducible: Always Steps to Reproduce: Have a google account set up with an invalid password. 1. Go Offine 2. Enable Restore last presence on login 3. Uncheck "Chat" for the account 4. Lock and Unlock your Screen and the password prompt should appear Actual Results: I get a password prompt. Expected Results: The account is disabled and I'm Offline, so KTP shouldn't be doing anything.
Thanks for the report Can you please post the output of "mc-tool dump" and "accounts-console list", replace any sensitive data.
Sure $ mc-tool dump Account: gabble/jabber/</snip account name> Display Name: </snip email> Normalized: </snip email> Enabled: enabled Icon: im-jabber Connects: automatically Nickname: Philip Muskovac Service: google-talk Presences: Automatic: available (2) "" Current: offline (1) "" Requested: available (2) "" Changing: yes (string) server = talk.google.com (string) fallback-conference-server = conference.jabber.org (uint) port = 5223 (GStrv) fallback-socks5-proxies = [""] (string) resource = kde-telepathy-pq-edge (bool) old-ssl = true (string) account = </snip email> $ account-console list account: id 1, disabled, provider: ktp-generic
Ah, I see what's wrong. Google accounts are a bit pita as they cannot be migrated easily and this is still using the old infrastructure. I would strongly suggest to simply readd the Google account (make sure you have telepathy-accounts-signon), then things will work as expected.
Did comment #3 help resolving the issue? Please set the bug status or add a comment.
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!