Reporting ChromeOS bugs in the buganizer public tracker
Thank you for your interest in ChromeOS!
You can help improve ChromeOS by reporting issues and feature requests in the ChromeOS Public Tracker. The ChromeOS Public Tracker contains a list of pending technical tasks across a variety of topics, information relevant to those tasks, and information about progress on those tasks, including which ones might get worked on in the short term.
Note: To learn how to use Issue Tracker, see the Issue Tracker developer documentation. Also, there are no guarantees that any particular bug can be fixed in any particular release.
The ChromeOS Public Tracker isn't a customer support forum. For support information, see the Chromebook help center.
To see what happens to your bug after you report it, read Life of a Bug.
The bug tracker is used by the people who develop ChromeOS to track our work and to collaborate with each other. Bug reports and the conversations within them are highly technical.
Bug reports are NOT a support forum. If you want user-focused ways to let us know about a problem or get an answer to a question, a bug report is probably not the best choice. There are other things you can do that will probably work better.
The Chromebook Central Help Forum is an active, searchable community for user discussion of bugs and feature requests. It is a great place to ask for help, and there’s a good chance that your question has already been asked (and answered, hopefully).
Feedback Reports are the primary mechanism by which ChromeOS users can send feedback about the project. Reports are clustered into categories that are used to identify larger issues, but they are typically not individually reviewed. Submitted reports are not publicly accessible.
To submit a feedback report, type Alt+Shift+i or click Report an issue within the Help submenu while logged in. Feedback reports include selected system logs if the Send system and app information, and metrics checkbox is checked. You can click the links within the checkbox text to see the information that will be attached to the report. See the official feedback documentation for more information.
Before reporting a bug
Search for your bug to see if anyone has already reported it. Don't forget to search for all issues, not just open ones, as your issue might already have been reported and closed. To help you find the most popular results, sort the result by the number of stars.
If you find your issue and it's important to you, [star it] (https://developers.google.com/issue-tracker/guides/subscribe #starring_an_issue)! The number of stars on a bug helps us know which bugs are most important to fix.
Proceed to filing a bug only if no one else has reported your bug.
- Use the right tracker. ChromeOS bugs should be reported in the Chrome OS Public Tracker. If you file issues elsewhere (e.g. crbug.com), there is a good chance we won’t see them.
- Browse for the correct component, such as Cellular or Graphics, and fill out the provided template. Or select the desired bug queue from the tables below.
Tip: Some components contain subcomponents, like Gaming > Steam and Gaming > Stadia.
- Include as much information in the bug as you can, following the instructions for the bug queue that you're targeting. A bug that simply says something isn't working doesn't help much, and will probably be closed without any action. The amount of detail that you provide, such as log files, repro steps, and even a patch set, helps us address your issue.
***promo In particular, a good bug report would be one that contains:
* A concise 1-2 sentence summary. Good: “Video goes black every 5 seconds on some Youtube videos.” Bad: “YouTube is glitching! Fix it!”. * What you were doing when the problem happened. Be as detailed as possible. Good: “I was in class in Google Meet, and the teacher sent us a link to the video at <url>” Bad: “The thing the teacher sent us didn’t work.” * What did you see? Again, be as detailed as possible. Were there any error messages? * Did it just happen once, always or only sometimes? Reproduction steps are the single most valuable thing we need. * Screenshots, videos, or any other info you can think of. Just remember that bugs are public, so don’t include anything you’re not comfortable with being visible to the public.
- Consider also filing a feedback report. Feedback reports contain diagnostic info we can use to investigate. If you file a feedback report as well, please mention it in the bug so we know to look for it and can link the two together.
The ChromeOS Public Tracker is used by developers to track ChromeOS bugs and feature requests. New issues submitted here are periodically triaged and examined by component owners. It has a variety of subcomponents in a number of categories related to ChromeOS. There are subcomponents for Apps, I/O, Connectivity, Services, and System.
If you want to report a security bug, please follow Reporting Security Bugs.
The Security component in the ChromeOS Public Tracker is for issues in Chrome OS userland daemons like cryptohome, chaps, attestation, etc. These are also issues related to hardware-backed security features like user data encryption, keystore and attestation. All other security issues have to be privately and securely opened using the link above, please do not file them here.
If you find an issue that impacts an aspect of ChromeOS connectivity, file your bug in one of these components.
If you find an issue that impacts ChromeOS core services, file a bug in one of these components.
If you find an issue that impacts any ChromeOS media, file a bug in one of these components.
|Other Media||Report Bug|
If you find an issue that impacts ChromeOS peripherals, file a bug in one of these components.
If you find a core ChromeOS System issue, please file it in one of the following components.
|Hardware-backed Security||Report Bug|