Bug 334563

Summary:	Proposal to reset internal authentication/connection error state when IM accounts are disabled
Product:	[Unmaintained] telepathy	Reporter:	Fabio Correa <facorread>
Component:	auth-handler	Assignee:	Telepathy Bugs <kde-telepathy-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	kde
Priority:	NOR	Keywords:	triaged
Version:	0.8.0
Target Milestone:	Future
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot

Description Fabio Correa 2014-05-09 18:08:11 UTC

I'm using the telepathy-kde suite from Kubuntu-14.04 LTS.

For several reasons, like network congestion, network switching, firewalls, etc, authentication/connection to IM services may fail. Given not all circumstances are covered by telepathy, some accounts are permanently deactivated with an "Unknown Error." This happens almost everyday for me, and the solution I have been using is to restart my computer. Please see the attached image.

A simple solution for this would be to restore the internal error/state of the accounts whenever they are deactivated by the user in the kcm accounts module. A more sophisticated solution would be to implement a timer that resets this state and retries the connections.

Reproducible: Always

Comment 1 David Edmundson 2014-05-09 18:09:49 UTC

You seem to have forgotten to attach the image.

Any chance you can get some logs from ktp-debugger? To find out what's failing?

Comment 2 Fabio Correa 2014-05-09 18:11:18 UTC

Created attachment 86545 [details]
Screenshot

Unknown errors that can't be fixed by disabling and re-enabling accounts. I have to restart my computer to be able to use the accounts again. Or maybe I need to kill one of the telepathy processes, but things shouldn't work that way.

Comment 3 Fabio Correa 2014-05-10 00:11:36 UTC

Unfortunately I was unable to reproduce the unknown errors in the last hours; nobody understands computers that's for sure. Will reopen when I'm able to get a meaningful trace with ktp-debugger.

Comment 4 Andrew Crouthamel 2018-09-25 03:40:58 UTC

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!

Comment 5 Andrew Crouthamel 2018-10-27 03:52:46 UTC

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!