We keep track of problems, suggestions and questions about ev3dev using GitHub Issues. This lets us keep everything in one place. (So, please don’t email the developers directly unless you have a personal question.)
First, before submitting an issue, search the existing issues (open and closed) to make sure someone else has not already reported the same problem or asked the same question. Please only comment on an existing open issue if you are fairly sure your problem/question is exactly the same. If the issue is closed or you are not sure your problem is the same, open a new issue instead.
If you don’t find anything helpful by searching, then create a new issue (only one problem, question or suggestion per issue please).
Most importantly for problems, we need to know the exact steps need to reproduce the issue. If you are writing a program, post the code. If you are following a tutorial, which step failed? Be as detailed as possible.
In the description of your issue, make sure to fill in the information from the template. In addition, include as much relevant information as possible:
dmsg | tail.
systemctl status brickman.service -l.
on the EV3 and include the picture in your comments.
We also expect you to clean up after yourself. Please close the issue when you feel that it is resolved.
Some additional things to take into consideration:
If you are copying and pasting information from a terminal, use “code fences” to make the text more readable.
A code fence is three backtick (`) characters before and after the text.
Just like you see here.
Learn more about writing on GitHub.
gitter.im is an online chat service that works in conjunction with GitHub. We monitor our Gitter room and are happy to provide support in live chat.
This is the recommended means of live chat support for ev3dev.
If you have a GitHub, GitLab or Twitter account, come say hello at https://gitter.im/ev3dev/chat.