Some considerations before doing anything:
- Search the issues list for similar topics before opening a new one.
- If you know how to fix the problem, consider doing a pull request instead of opening a new issue.
- Only report problems in latest and development version. Reporting issues related to older versions will be rejected.
- Use gist to post logs longer than 1024 characters.
- akvirtualcamera as project, is not affiliated or endorsed to any distribution, report packaging problems in their respective issue tracker.
- Respect the templates, we need as much information as possible.
- Don't open an issue and disappear, we need you at least the first week to clear up missing information.
- Missing information makes useless and unsolvable an issue report.
- You are our debbuger, eyes and hands, if an issue is not reproducible then you will be the only person able to solve it.
- Take a seat and wait for your turn, as many others that has their issues open, or much better try fixing it your self and collaborate with the solution 😄
Choose one of the templates bellow that fit better your issue.
Write here a brief description of the problem.
Describe the problem the best as you can, don't omit information.
How it should have work?
If akvirtualcamera crashed, try to reproduce the crash several times to be sure where is the problem. Write the steps to reproduce the issue bellow:
- Open this
- Click that
- Drag those
- ...
How would you solve the problem?
- akvirtualcamera inormation: (version) (architecture)
- Operating System information: (name) (numeric version and codename if applied) (architecture)
- Any other useful information: (logs, gdb backtrace, valgrind logs, screenshots, hardware, etc.)
Describe your idea the best as you can, include sketches, mockups and diagrams if required.
Be patient, take in mind that there may be other priorities. Your idea will be accepted if fit in project goals.
Go ahead!