DebuggingTelepathy
Differences between revisions 1 and 4 (spanning 3 versions)
330
Comment:
|
819
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
=== Debugging Connection managers === If problems occur in connection managers, the debug output can help sometimes: * For `telepathy-salut`: {{{ SALUT_DEBUG=all telepathy-salut }}} * For `telepathy-gabble`: {{{ GABBLE_DEBUG=all telepathy-gabble }}} |
|
Line 4: | Line 12: |
`SALUT_DEBUG=all telepathy-salut` `GABBLE_DEBUG=all telepathy-gabble` `GOSSIP_DEBUG=all gossip` `/usr/lib/cohoba/cohoba-applet -w` `/usr/lib/cohoba/cohoba-applet houston` |
Just make sure you stop all instances of those connection-managers beforehand. You can also test connection-managers using the `telepathy-inspector` package. |
Line 10: | Line 14: |
=== Debugging Apps === If problems occur in clients, you can get debug output for them too: * For `gossip`: {{{ GOSSIP_DEBUG=all gossip }}} * For `cohoba`: {{{ /usr/lib/cohoba/cohoba-applet -w /usr/lib/cohoba/cohoba-applet houston }}} |
This page intends to give an overview over how to efficiently debug Telepathy problems.
Debugging Connection managers
If problems occur in connection managers, the debug output can help sometimes:
For telepathy-salut:
SALUT_DEBUG=all telepathy-salut
For telepathy-gabble:
GABBLE_DEBUG=all telepathy-gabble
Just make sure you stop all instances of those connection-managers beforehand. You can also test connection-managers using the telepathy-inspector package.
Debugging Apps
If problems occur in clients, you can get debug output for them too:
For gossip:
GOSSIP_DEBUG=all gossip
For cohoba:
/usr/lib/cohoba/cohoba-applet -w /usr/lib/cohoba/cohoba-applet houston
DebuggingTelepathy (last edited 2008-08-06 16:59:57 by localhost)