Version 1 (modified by 7 years ago) (diff) | ,
---|
Logging
Sometimes the problem is so obvious that you will simply get the error directly from the command line or in the server log file.
Otherwise, a good first step is to start xpra from the command line and add "-d CATEGORY
" to it. The list of categories can be found with xpra -d help
.
You can also prefix the CATEGORY
with a dash "-
" to disable debug logging for it. ie:
xpra start :10 -d all,-window
Each category can also be enabled using environment variable, which can be useful if you cannot modify the command line, or if the logging should happen very early on, or if you aren't calling the code from its normal wrappers.
Use: XPRA_CATEGORY_DEBUG=1 xpra ...
to enable debug logging for your chosen CATEGORY
.
It is also possible to enable and disable debug logging at runtime using:
xpra control :DISPLAY debug enable CATEGORY
and
xpra control :DISPLAY debug enable CATEGORY
And you can get the current list of debug loggers which:
xpra control :DISPLAY debug status