VLC developers understand that the requested infos can be difficult to gather or provide. If there are more than one bug, then as many separate bug reports should be filed.īugs with insufficient infos may be closed as incomplete (or invalid in the worst cases). Note that a single bug report must describe exactly one bug.
If the problem is a software bug, rather than a support problem, then it is recommended to file a bug report with the listed infos above.
If you are uncomfortable with words, you may also use screenshots. The exact steps to reproduce the problem.Complete logs as those from the messages dialog, verbosity to 2 (GUI mode) or the -vvv switch (CLI mode).
Make sure to name all the audio and video hardware in question that might be related to VLC's usage.įor instance: iMac G4 or Pentium4 with GeForce3, with an external USB dolby surround output device. Your operating system and the precise version (include the Linux distribution, or the version of Windows).Please gather the following information and send it along with your report:
The more sound and concrete details you provide about your issue, the better the chances that we will investigate it fully. We try to answer all your mails, posts and reports, but there are so many that we simply do not have the time to do so for everyone. When you post on the forum, email us, or create a bug report, please provide as much information as possible in your report. Don't forget to enter a valid e-mail address if you want to receive notifications when your bug is handled. You will need to register a user account before you can file a new bug (or comment on an existing one). If you are sure that you found a bug and that you have all information needed, you can enter a bug in our GitLab. You can also describe your problem on the relevant mailing list. Search on this wiki and on the forums and see if someone else has asked a similar question or has seen a similar bug.Īsk about your problem in the relevant forum and make sure to include as much information as possible (see the pointers below). So you still think you found a bug? Great! The page of the issue will say so if it is. If you find your issue, see if it is already closed. Please search the list of known and fixed issues. Sometimes they are already fixed for the next version of VLC, see the nightly builds section. If your suggestion is not on this list, you might want to make a feature request bug on GitLab. We have a list of things we would like to implement in the future. Some things are simply not yet supported by VLC. The bug may already be fixed in those builds. (Uninstalling VLC does not remove its old settings).īefore you file a new bug, please try a preview development build of our next version on our nightly build website.
See VSG:ResetPrefs for details on how to delete your preferences. Old preferences and/or incorrect settings are common causes of problems. Have you tried resetting your preferences and restarting VLC yet? To avoid that, please check the following:Īre you using the latest version of VLC? The latest version is 3.0.12.īug reports on older versions of VLC are likely to be ignored, because changes in newer versions of VLC may have already fixed the issue. It may seem silly, but a large proportion of the submitted bug reports are not really bugs at all, or have been known for months, and/or are already fixed. Please try to follow the bugs policy, so we all save time. Here is some detailed information on how to submit useful bug reports. If you find any bugs, or if you experience any crashes, then we would very much like to hear about the issue.
This page describes how to report a VLC bug.Īndroid users, please see Android Report bugs.