DebuggingTelepathy

Revision 6 as of 2007-03-06 15:11:08

Clear message

Introduction

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

Debugging procedure

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.

Persistent Connection Managers

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

IDLE_PERSIST=1 telepathy-idle

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

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]