Select a product category to browse:

Build System, Metadata & Runtime: Defects in Bitbake, OE-Core, Toaster and metadata related issues (inc BSPs) or issues in the generated runtime
BSPs: Issues in BSP metadata layers
BitBake: BitBake is a make-alike build tool with the special focus of distributions and packages for embedded Linux cross compilation.
Hob: Hob is the Yocto Project's graphical image creator.
Meta-yocto: All defects related to the meta-yocto layer's metadata.
OE-Core: All defects related to the OE-Core layer's metadata.
Other YP Layers: Issues in other Yocto Project maintained layers
Runtime: Issues with the runtime generated by the buildsystem
Security - Recipe Upgrade: Security issues which can be addressed by updating metadata.
Toaster: Toaster is the Yocto Project's online image creator.
 
Yocto Project Subprojects: Defects in Yocto Project umbrella projects (e.g. CROPS, cross-prelink, kernel-tools, matchbox, pseudo, opkg, sato)
ADT: The ADT includes a platform-independent standalone cross-compiling toolchain, debugging and profiling tools and the QEMU emulation and support scripts. These capabilities allow the developer to start work on a target architecture without needing real hardware.
Anjuta Plugin: The Anjuta IDE Plug-in integrates the functionality of the Yocto SDK Generator and toolchain into the Anjuta IDE. This allows its users direct access to these SDK Generator capabilities: * The cross compiler * Use of the debugging and profiling tools * Use of the emulator http://yoctoproject.org/projects/anjuta
Automated Update Handler: Tool to help automate updating of recipes to current upstream, this will handle basic recipes and patch handling
CROPS: Collection of containers and plugin to leverage cross toolchains running on various host environments.
Cross-prelink: By providing an emulated runtime dynamic linker, the cross-prelink project extends the prelink software's ability to prelink a sysroot environment. Additionally, the cross-prelink software enables the ability to work in sysroot style environments. Refer: https://www.yoctoproject.org/tools-resources/projects/cross-prelink
Eclipse Plugin: The Eclipse IDE Plug-in integrates the functionality of the Yocto SDK Generator and toolchain into the Eclipse IDE. This allows its users direct access to these SDK Generator capabilities: * The cross compiler * Use of the debugging and profiling tools * Use of the emulator https://www.yoctoproject.org/tools-resources/projects/eclipse-ide-plug
Error Reporting tool: Defects related to the error reporting system (http://errors.yoctoproject.org/)
IoT Reference OS Kit: Defects related to the Intel IoT Reference OS Kit. (refkit)
Kernel: Defects against linux-yocto repository and yocto-kernel-tools (not the linux-yocto recipes)
Layer Index: Defects in the layer index codebase or in the data shown by the index (http://layers.openembedded.org)
Matchbox: Matchbox is the window manager used by Sato.
Patchwork/Patchtest: Defects related to patchwork, patchtest and the patchtest testsuite
Pseudo: Pseudo is a program that can either be used directly or as an LD_PRELOAD, which allows these operations to succeed as if the user did have system administrator privileges even though they are an ordinary user. Refer:https://www.yoctoproject.org/tools-resources/projects/pseudo Pseudo has a lot of similarities to fakeroot but is a new implementation that improves on the problems seen using fakeroot. Pseudo is now extensively used by Poky as a replacement to fakeroot but can also be used standalone in many other use cases.
Ptest-runner: Issues with ptest-runner
Recipe Reporting System (RRS): Defects in the RRS, a tool to track upstream recipe status and other recipe metrics.
Sato: Sato is a reference GTK+/Matchbox based environment.
Security Response Tool: Web-based tool to triage and manage security issues.
Swabber: Swabber is a tool for detecting host contamination during a build.
SwatBot: Issues related to SwatBot
Wic: Bugs related to Wic disk image creation tools.
Yocto Project Compatible: Track Yocto Project Compatible Layer requests. Use https://www.yoctoproject.org/compatible-registration/ instead of submitting directly.
eSDK: All bugs related to the extensible SDK
opkg: Issues related to Open PacKaGe Management lightweight package management system
 
Documentation: Yocto documentation/manual issues (e.g. Quick Start, Reference manual, Bitbake Manual)
ADT Manual: Defects within the Yocto Project Application Developer's Guide. ADT and SDK Documentation.
BSP Guide: Defects within the Yocto Project's BSP Documentation.
BitBake User Manual: Issues with the BitBake Users Manual
Demos: Bugs tracking issues with published demos and tutorials.
Development Manual: Defects within the Yocto Project's Development Manual.
General Docs: Problems with documentation in general with no associated manual.
Kernel Development: Defects within the Yocto Project's Kernel Development Manual.
Mega Manual: Issues related to the all in one mega-manual specifically.
Profile and Tracing Manual: Documentation issues relating to the profiling and tracing manual.
Quick Start: Defects within the Yocto Project's Quick Start.
Reference: Defects within the Yocto Project's Reference Manuals.
Variables Glossary: Report flaws in the variables glossary.
 
Infrastructure: Yocto Infrastructure bugs, including building tool, website, bugzilla itself.
AutoBuilder: Defects related to the yocto-autobuilder or it's output.
Bugzilla: Defects related to the Yocto Project's Bugzilla.
Helpdesk: Issues to be serviced by the Yocto Project helpdesk team. For example access requests or services offline
Infrastructure General: Any issue or feature request for the public Yocto Project infra that doesn't fit under another category.
Program Management: Task grouping bugs with dependencies on multiple bugs required to complete a larger program goal.
Release Process: Issues related to the release process, infrastructure and tooling
Testopia: Issues related to test plans or test cases.
Website: Defects related to the Yocto Project's website.
Wiki: Defects related to the Yocto Project's wiki.
 
QA/Testing: Defects related to QA and Test Automation
Build Testing: Bugs/enhancements related to tests run during the build (sanity.bbclass, insane.bbclass and other build time tests)
Functional (self) Testing: Bugs/enhancements related to functional testing (e.g bitbake-selftest, oe-selftest)
IoT Reference OS Kit Testing: QA related to the Intel IoT Reference OS Kit. (refkit)
Manual Testing: Defects related to Manual Testing
Package Testing (ptest): Bugs/enhancements related to package specific tests (ptest)
Runtime Testing: Bugs/enhancements related to tests run against generated images from the build (testimage.bbclass, testsdk.bbclass, oeqa/runtime, oeqa/sdk, oeqa/esdk and other generated runtime tests)
Test Plans/Suite: Defects related to Test Plans and Suites run during QA testing.
Tooling: Tools related to our QA/testing process (e.g. resulttool)
 
Runtime: Defects related to the installation, booting or operation of runtimes.
General Runtime: General Runtime defects which don't fit another product
Installation: Runtime installation/booting/operation bugs
Package Management Issues: Defects related to package management (rpm, deb, ipk) or the ADT repository.
Security: Security issues.
System Startup: Defects related to system startup
 
Hardware Platforms: Defects related the physical hardware platforms, e.g. MinnowBoard MAX.
MinnowBoard MAX: Physical hardware issues with MinnowBoard MAX
MinnowBoard MAX Firmware: Issues with MinnowBoard MAX Firmware