| Summary: | AccountManager does not follow telepathy spec while generating Account object paths | ||
|---|---|---|---|
| Product: | [Unmaintained] telepathy | Reporter: | Andre Moreira Magalhaes <andrunko> |
| Component: | general | Assignee: | Telepathy Bugs <kde-telepathy-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | grundleborg |
| Priority: | HI | ||
| Version First Reported In: | git-latest | ||
| Target Milestone: | 0.4.0 | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
T-A-K has been superseded by Mission Control 5.3 |
Version: (using Devel) OS: Linux Installed from: Compiled sources Account object paths generated by AccountManager does not follow the spec. The spec states: The object path of an Account MUST take the form /org/freedesktop/Telepathy/Account/cm/proto/acct, where: * cm is the same Connection_Manager_Name that appears in the connection manager's well-known bus name and object path * proto is the Protocol name as seen in ConnectionManager.ListProtocols, but with "-" replaced with "_" (i.e. the same as in the object-path of a Connection) * acct is an arbitrary string of ASCII letters, digits and underscores, starting with a letter or underscore, which uniquely identifies this account