233
edits
Changes
Jump to navigation
Jump to search
mLine 8:
Line 8: − + − For desktop-wide debugging of Salut and Gabble:+ Line 18:
Line 18: − − For per-activity debug logging: − SUGAR_LOGGER_LEVEL=debug sugar-launch org.laptop.Chat − +
BugSquad/Telepathy Debugging (view source)
Revision as of 14:24, 14 February 2021
, 14:24, 14 February 2021→Fedora 20
When there are certain kinds of problems with collaboration, it is useful to developers to have log files for debugging purposes. Here is how to enable these log files. If you haven't already seen [[BugSquad/Get Logs]], see that page first.
When there are certain kinds of problems with collaboration, it is useful to developers to have log files for debugging purposes. Here is how to enable these log files. If you haven't already seen [[BugSquad/Get Logs]], see that page first.
=== Fedora 20 ===
=== Fedora 20 through Fedora 35/rawhide ===
Starting with Fedora 20, to enable debug logging of Salut and Gabble:
* Edit the /etc/environment file
* Edit the /etc/environment file
G_MESSAGES_DEBUG="all"
G_MESSAGES_DEBUG="all"
GABBLE_LOGFILE=/home/olpc/gabble.log
GABBLE_LOGFILE=/home/olpc/gabble.log
* Reboot
* Reboot
=== Fedora 18 ===
=== Fedora 18 ===
* Edit the ~/.sugar/debug file (default version shown below in the gray box) and uncomment the lines about GABBLE_DEBUG, GABBLE_LOGFILE, SALUT_DEBUG, SALUT_LOGFILE and PRESENCESERVICE_DEBUG by removing the initial '#' character
* Edit the ~/.sugar/debug file (default version shown below in the gray box) and uncomment the lines about GABBLE_DEBUG, GABBLE_LOGFILE, SALUT_DEBUG, SALUT_LOGFILE and PRESENCESERVICE_DEBUG by removing the initial '#' character
* For debugging lower level problems in the Telepathy connection managers, enable LM_DEBUG (for telepathy-gabble) or GIBBER_DEBUG (for telepathy-salut). Note that these will produce much bigger log files.
* For debugging lower level problems in the Telepathy connection managers, enable LM_DEBUG (for telepathy-gabble) or GIBBER_DEBUG (for telepathy-salut). Note that these will produce much bigger log files.
* Reboot
* Reboot (or restart the display manager).
<pre>
<pre>