DebuggingTelepathy

Differences between revisions 1 and 8 (spanning 7 versions)
⇤ ← Revision 1 as of 2006-11-10 20:13:37 →
Size: 330
Editor: 207
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:
This page intends to give an overview over how to efficiently debug Telepathy problems. [[Include(Debugging/Header)]]
||<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 4:
= Introduction =
Line 4: Line 6:
`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`		 This page gives an overview over how to efficiently debug Telepathy problems.
Line 10: Line 8:
= Debugging procedure =
Line 11: Line 10:
== 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'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||

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

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

 * DebuggingProcedures

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)