DebuggingTelepathy

Differences between revisions 5 and 7 (spanning 2 versions)
Revision 5 as of 2006-12-06 10:57:41
Size: 984
Editor: i59F71EA5
Comment:
Revision 7 as of 2007-03-06 15:14:43
Size: 1697
Editor: cF5A6BF51
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This page intends to give an overview over how to efficiently debug Telepathy problems. ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''[[BR]][[TableOfContents]]||
Line 3: Line 3:
=== Debugging Connection managers === = Introduction =

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

= Debugging procedure =

== Connection managers ==
Line 14: Line 20:
=== Persistent Connection Managers === == Persistent Connection Managers ==
Line 20: Line 26:
=== Debugging Apps === == Applications ==
Line 30: Line 36:
= Known bugs =

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

'''Open'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||

'''Closed'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||

------
'''Also see:'''

 * DebuggingProcedures

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)