Support and security

Search this documentation before you report a problem. When you open a report, include enough information for another developer to reproduce the problem.

Technical problems

Include this information in a technical report:

• The source tag:

  $ git -C zephyr-manifest describe --tags --exact-match
  

• The Zephyr repository revision:

  $ git -C zephyr rev-parse HEAD
  

• The output of workshop info:

  $ workshop info zephyr-26-04
  

• The board name and board revision.

• The complete command that failed.

• The complete error output as text.

• A small application that reproduces the problem, when possible.

File public source defects in the Zephyr RTOS Launchpad bug tracker.

Security problems

Do not report a security problem in a public bug. Email security@ubuntu.com.

Include the affected revision, reproduction steps, and known mitigations in the message. Read the Ubuntu security disclosure policy for more information.

See also

Reference:

• Releases

• Security policy