Troubleshooting

How to get debug output?

Read the generic wiki for common debug tips and tricks. Here is some CM specific stuff:

Run from the command line

In order to get debug output from the connection manager, run it from a command line (in the user session). Typical command will be /usr/libexec/telepathy-morse (Gentoo, Sailfish OS) or /usr/lib64/telepathy-morse (Debian, Ubuntu) or /usr/lib/telepathy/telepathy-morse (Arch), depends on your distribution. Please ensure that the Telegram account is offline (in the local telepathy client) and the connection manager is not already run (you'll get Unable to register service error).

journalctl

Sailfish OS

devel-su
journalctl -fa /usr/libexec/telepathy-morse

Login does not work

Sailfish OS

Run jolla-settings from a privileged command line and get the logs:

devel-su -p
jolla-settings

See also: Sailfish OS troubleshooting

Desktop

First of all, check that the account is registered in Telepathy accounts: mc-tool summary

If there is no morse account, then you can try to add it directly to the telepathy account system: mc-tool add morse/telegram MyAccount string:account=123456789 (where MyAccount is a display name of the account and 123456789 is a full international phone number)

The command will print you the account name such as morse/telegram/_31234567890

The added account should be enabled by command mc-tool enable morse/telegram/_31234567890 then you can request online status for the account: mc-tool request morse/telegram/_31234567890 online

Where Telepathy-Morse stores the account data?

Morse stores all data in directory

~/.local/share/telepathy/morse/<server>/<account>/

Where <server> is official (or the IP:port if customized) and <account> is the phone number.

• account.bin contains the authorization key and some other connection data in binary format.
• telegram-state.bin is a JSON file (file extension .bin means that you should not rely on the format) that stores the dialogs state.