Please review this check list, before you click the Submit button:
- you have installed the latest MiKTeX updates
- the bug report is self-contained: it does not contain links to questions/reports on external sites (e.g., Stack Exchange Network)
- step-by-step reproduction instructions
- configuration report (
initexmf --report) attached - input files attached
- log files attached
Before creating a bug report, please check this list:
- check the MiKTeX FAQ
- write down a one-liner which summarizes the problem
- perform an Internet search with the one-liner as the query
Make sure that others will be able to reproduce the bug by providing:
- step-by-step reproduction instructions: describe the exact steps which reproduce the problem in as many details as possible
- input files which are necessary to reproduce the bug: aka a minimal working example
- your observations: command output, screenshots
Most importantly: include information about your MiKTeX setup:
- installation report: let MiKTeX Console create
an installation report (on the
Diagnosepage) - contents of the MiKTeX log directory: MiKTeX Console tells
you the location of log directory on the
Diagnosepage
A MiKTeX developer will receive a notification. If the bug is reproducible, it will be a attached to a milestone with an estimated fix date.
Unreproducible bugs usually lead to queries. So be prepared to make available additional information.
Please note: sloppy bug reports will be closed (or deleted) without comment.
Please review this check list, before you click the Submit button:
- you have installed the latest MiKTeX updates
- the feature request is self-contained: it does not contain links to questions/reports on external sites (e.g., Stack Exchange Network)
Please note: sloppy feature requests will be closed (or deleted) without comment.
Thanks!