DebuggingTelepathy

Differences between revisions 7 and 8
Revision 7 as of 2007-03-06 15:14:43
Size: 1697
Editor: cF5A6BF51
Comment:
Revision 8 as of 2008-06-23 22:19:15
Size: 1728
Editor: c-24-21-234-111
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Include(Debugging/Header)]]

Include(Debugging/Header)

Introduction

This page gives an overview over how to efficiently debug Telepathy problems.

Debugging procedure

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.

Persistent Connection Managers

To make telepathy-idle not exit, when there's not client connected, use this:

IDLE_PERSIST=1 telepathy-idle

Applications

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

Known bugs

Description of known issues, how to recognise them and stock responses/actions.

Open

Bug#

Description

Action

TBD.

TBD.

TBD.

Closed

Bug#

Description

Action

TBD.

TBD.

TBD.


Also see:


[:CategoryTelepathy]BR [:CategoryBugSquad]

DebuggingTelepathy (last edited 2008-08-06 16:59:57 by localhost)