...

libc6
libgcc1
libstdc++6
zlib1g
libfreetype6
libfontconfig1
libpng16-16
libgif7
libexpat1
libgl1
libgl1-mesa-dri
libgl1-mesa-glx
libx11-6
libpango-1.0-0
libpangoft2-1.0-0
libpython2.7
libpcre3
libglib2.0-0
libharfbuzz0b
libpcre2-16-0
libuuid1
libxcb1
libthai0
libffi7
libgraphite2-3
libdatrie1
libcurl4
libicu66
ffmpeg
libhpdf-2.3.0
hunspell-en-us
hunspell
hunspell-en-gb
hunspell-en-au
hunspell-de-de
hunspell-es
hunspell-fr-modern
hunspell-pl
hunspell-sv

Run Kudo server

Start the Server:

• Run the provided start/stop script from the command line:

...

• For instructions on opening a drawing file using Kudo, refer to the documentation at: https://graebert.atlassian.net/wiki/x/9QBYRg .

Starting the Kudo Server Manually

If you prefer to start the Kudo server manually from the command line, follow these steps:

...

You can specify parameters for the server according to your requirements. Refer to the documentation at https://graebert.atlassian.net/wiki/x/9QBdRg for a list of available parameters and their usage.

Debugging Logs for the Editor Application

For debugging purposes, the following log files are available for the Editor Application on the server. Additionally, these logs can be configured to be forwarded to a central logging service such as Fluentd, Logentries, Sumo Logic, etc.

...

By referring to these log files, you can diagnose issues, monitor activity, and troubleshoot any errors or unexpected behavior within the Editor Application running on the server. Additionally, integrating these logs with a centralized logging service can facilitate easier management and analysis of log data.

Crash Reporting Configuration

You can manage crash reporting for the Editor Application using the following options:

...