Bug 39410

Summary:	Make logs clear about account invalidity
Product:	Telepathy	Reporter:	Jonny Lamb <jonny.lamb>
Component:	mission-control	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	minor
Priority:	medium	Keywords:	love
Version:	git master
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Jonny Lamb 2011-07-20 15:33:52 UTC

I was contacted asking why an automatic Ytstenut account wasn't going online. Mission Control is really sheepish about it not going online and only by reading logs do you find out the account is "not Valid".

Any more than that is left up to you though. In this case the local-ytstenut protocol was not present in the manager file which was present (by design) so a nice line about how the protocol couldn't be found would be nice.

Perhaps this would also be cryptic as then you'd need to know whether the CM had been introspected or whether a manager file was read. I bet TpConnectionManager doesn't have API to tell you that.

What a hand wavy bug report. I hope you like it.

Comment 1 Jonny Lamb 2011-07-20 15:35:29 UTC

Also, this account is an automatic one (obvs) and is hidden so empathy-accounts doesn't show it (so can't show its invalidity).

Perhaps ofdT.Account should have a validity reason property as to why the account is invalid. Interesting.

Comment 2 GitLab Migration User 2019-12-03 20:10:57 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-mission-control/issues/43.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.