Report bugs - Revision history

Thresh at 10:00, 17 April 2021

2021-04-17T10:00:04Z

← Older revision		Revision as of 10:00, 17 April 2021
Line 48:		Line 48:

	=== Enter the bug in the VLC GitLab ===		=== Enter the bug in the VLC GitLab ===
	If you are sure that you found a bug and that you have all information needed, you can enter a bug in our [https://code.videolan.org/~~vieolan~~/vlc/-/issues/ GitLab].		If you are sure that you found a bug and that you have all information needed, you can enter a bug in our [https://code.videolan.org/videolan/vlc/-/issues/ GitLab].

	You will need to register a user account before you can file a new bug (or comment on an existing one). 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). Don't forget to enter a valid e-mail address if you want to receive notifications when your bug is handled.

Thresh at 20:46, 19 March 2021

2021-03-19T20:46:05Z

← Older revision		Revision as of 20:46, 19 March 2021
Line 30:		Line 30:

	=== New Features ===		=== New Features ===
	Some things are simply not yet supported by VLC. We have a [https://~~trac~~.videolan.org/vlc/~~query~~?~~action=view&type~~=~~enhancement~~&~~amp;order~~=priority list of things] we would like to implement in the future.		Some things are simply not yet supported by VLC. We have a [https://code.videolan.org/videolan/vlc/-/issues?label_name%5B%5D=Type%3A%3Aenhancement&sort=priority list of things] we would like to implement in the future.

	If your suggestion is not on this list, you might want to make a ''feature request'' bug on [https://~~trac~~.videolan.org/vlc/ ~~Trac~~].		If your suggestion is not on this list, you might want to make a ''feature request'' bug on [https://code.videolan.org/videolan/vlc/-/issues/ GitLab].

	=== Closed bugs ===		=== Closed bugs ===
	Many bugs are already known. Sometimes they are already fixed for the next version of VLC, see the nightly builds section.		Many bugs are already known. Sometimes they are already fixed for the next version of VLC, see the nightly builds section.

	Please [https://~~trac~~.videolan.org/vlc/ search] the list of known and fixed issues. If you find your issue, see if it is already closed. The page of the issue will ~~then show something like:~~		Please [https://code.videolan.org/videolan/vlc/-/issues/ search] the list of known and fixed issues. If you find your issue, see if it is already closed. The page of the issue will say so if it is.

	~~''Ticket #87 (Closed: fixed)''~~

	== Still a bug? ==		== Still a bug? ==
Line 49:		Line 47:
	Ask about your problem in the [http://forum.videolan.org/ relevant forum] and make sure to include as much information as possible (see the pointers below). You can also describe your problem on the [http://www.videolan.org/support/lists.html relevant mailing list].		Ask about your problem in the [http://forum.videolan.org/ relevant forum] and make sure to include as much information as possible (see the pointers below). You can also describe your problem on the [http://www.videolan.org/support/lists.html relevant mailing list].

	=== Enter the bug in the VLC ~~Trac~~ ===		=== Enter the bug in the VLC GitLab ===
	If you are sure that you found a bug and that you have all information needed, you can enter a bug in our [https://~~trac~~.videolan.org/vlc/ ~~Trac system~~].		If you are sure that you found a bug and that you have all information needed, you can enter a bug in our [https://code.videolan.org/vieolan/vlc/-/issues/ GitLab].

	You will need to register a user account before you can file a new bug (or comment on an existing one). 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). Don't forget to enter a valid e-mail address if you want to receive notifications when your bug is handled.
Line 73:		Line 71:
	# If the bug is a crash or lock-up/freeze, the '''complete''' threaded '''symbolic''' stack trace of VLC at the time (see also [[debug]]ging).		# If the bug is a crash or lock-up/freeze, the '''complete''' threaded '''symbolic''' stack trace of VLC at the time (see also [[debug]]ging).
	# If possible, the '''video sample''' in question:<br />If the issue is specific to a certain file, that is always very helpful, if not indispensible. In this case, please upload as much of the file as you can to our [http://streams.videolan.org/upload/ samples server].		# If possible, the '''video sample''' in question:<br />If the issue is specific to a certain file, that is always very helpful, if not indispensible. In this case, please upload as much of the file as you can to our [http://streams.videolan.org/upload/ samples server].
	# '''Email''' with a valid reply address, if you are not using ~~trac~~, so we can get back to you with possible additional questions.		# '''Email''' with a valid reply address, if you are not using gitlab, so we can get back to you with possible additional questions.

	= Filing a bug report =		= Filing a bug report =

Courmisch at 10:05, 17 December 2020

2020-12-17T10:05:14Z

← Older revision		Revision as of 10:05, 17 December 2020
Line 71:		Line 71:
	# The reproducibility of the problem: does it occur every time? If not, how often?		# The reproducibility of the problem: does it occur every time? If not, how often?
	# If applicable, the type (movie, music, subtitle) and the '''format''' of the file being played. If known, also the codec(s) in the file.		# If applicable, the type (movie, music, subtitle) and the '''format''' of the file being played. If known, also the codec(s) in the file.
	# If the bug is a crash or lock-up/freeze, the '''complete''' threaded '''symbolic''' stack trace of VLC at the time (see also ~~below~~).		# If the bug is a crash or lock-up/freeze, the '''complete''' threaded '''symbolic''' stack trace of VLC at the time (see also [[debug]]ging).
	# If possible, the '''video sample''' in question:<br />If the issue is specific to a certain file, that is always very helpful, if not indispensible. In this case, please upload as much of the file as you can to our [http://streams.videolan.org/upload/ samples server].		# If possible, the '''video sample''' in question:<br />If the issue is specific to a certain file, that is always very helpful, if not indispensible. In this case, please upload as much of the file as you can to our [http://streams.videolan.org/upload/ samples server].
	# '''Email''' with a valid reply address, if you are not using trac, so we can get back to you with possible additional questions.		# '''Email''' with a valid reply address, if you are not using trac, so we can get back to you with possible additional questions.

DoesItReallyMatter: +:Category:Security

2019-02-11T08:54:26Z

+Category:Security

← Older revision		Revision as of 08:54, 11 February 2019
Line 163:		Line 163:

	Adapted by [[User:J-b\|Jean-Baptiste Kempf]] for this wiki.		Adapted by [[User:J-b\|Jean-Baptiste Kempf]] for this wiki.

			[[Category:Security]]

Courmisch: /* Enter the bug in the VLC Trac */

2018-02-24T07:04:48Z

Enter the bug in the VLC Trac

← Older revision		Revision as of 07:04, 24 February 2018
Line 50:		Line 50:

	=== Enter the bug in the VLC Trac ===		=== Enter the bug in the VLC Trac ===
	If you are sure that you found a bug and that you have all information needed, you can enter a bug in our [https://trac.videolan.org/vlc/~~newticket~~ Trac system].		If you are sure that you found a bug and that you have all information needed, you can enter a bug in our [https://trac.videolan.org/vlc/ Trac system].

	You will need to register a user account before you can file a new bug (or comment on an existing one). 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). Don't forget to enter a valid e-mail address if you want to receive notifications when your bug is handled.

Courmisch: /* New Features */

2018-02-24T07:04:13Z

New Features

← Older revision		Revision as of 07:04, 24 February 2018
Line 32:		Line 32:
	Some things are simply not yet supported by VLC. We have a [https://trac.videolan.org/vlc/query?action=view&type=enhancement&order=priority list of things] we would like to implement in the future.		Some things are simply not yet supported by VLC. We have a [https://trac.videolan.org/vlc/query?action=view&type=enhancement&order=priority list of things] we would like to implement in the future.

	If your suggestion is not on this list, you might want to make a ''feature request'' bug on [https://trac.videolan.org/vlc/~~newticket trac~~].		If your suggestion is not on this list, you might want to make a ''feature request'' bug on [https://trac.videolan.org/vlc/ Trac].

	=== Closed bugs ===		=== Closed bugs ===

Courmisch: /* Bug resolutions */

2017-07-29T13:18:27Z

Bug resolutions

← Older revision		Revision as of 13:18, 29 July 2017
Line 113:		Line 113:

	All bugs are initially filed in the ''new'', and without a ''resolution''. If/when a bug gets closed, the resolution must be filed. The following resolutions are currently used:		All bugs are initially filed in the ''new'', and without a ''resolution''. If/when a bug gets closed, the resolution must be filed. The following resolutions are currently used:
	* '''fixed~~''':~~ The bug has been corrected in a newer version of VLC; the fixed version should be indicated under ''milestone''.
	* '''invalid~~'''':~~ The bug report is confusing, unintelligible, not in English, describes multiple separate issues, ~~or is otherwise impossible for~~ the VLC developers to analyze.		=== fixed ===
	* '''wontfix~~''':~~ The VLC developers believe that the problem should not or ~~cannot~~ be addressed.		The bug has been corrected in a newer version of VLC; the fixed version should be indicated under ''milestone''.
	* '''duplicate~~''':~~ A report for the same problem has already been filed earlier. There is no need to keep multiple reports for a single problem. This does not necessarily mean that the bug is fixed yet.
	* '''worksforme~~''':~~ In the specified circumstances, the VLC developers are not able to reproduce the described problem, or the described "problem" is actually the intended behaviour.		=== invalid ===
	* '''notvlc~~''':~~ The reported problem ~~may~~ be real~~, but~~ its root cause is not within the VLC code base, and therefore the VLC developers cannot fix it. The bug should probably be reported '''somewhere else'''.		The bug report is confusing, unintelligible or is not in English. Or the bug describes multiple separate issues in a single report. Or for any other reasons, the VLC developers are unable to analyze the bug report.
	* '''incomplete~~''':~~ The bug report does not contain enough infos for the VLC developers to analyze the bug. See also above.
			=== wontfix ===
			The VLC developers believe that the problem should not be addressed because it would cause more problems that it would solve, or is otherwise a bad idea. Alternatively, the VLC developers believe that the problem can fundamentally not be addressed, even if the concern is valid.

			=== duplicate ===
			A report for the same problem has already been filed earlier. There is no need to keep multiple reports for a single problem. This does not necessarily mean that the bug is fixed yet.

			=== worksforme ===
			In the specified circumstances, the VLC developers are not able to reproduce the described problem, or the described ''problem'' is actually the intended behaviour.

			=== notvlc ===
			The reported problem seems like it might be real. However its root cause does not lie within the VLC code base, and therefore the VLC developers cannot fix it. The bug should probably be reported '''somewhere else'''.

			=== incomplete ===
			The bug report does not contain enough infos for the VLC developers to analyze the bug. See also above.

	== Additional remarks ==		== Additional remarks ==

Courmisch: /* Bug severities */

2017-07-29T13:14:55Z

Bug severities

← Older revision		Revision as of 13:14, 29 July 2017
Line 85:		Line 85:
	== Bug severities ==		== Bug severities ==

	~~'''~~blocker~~''':~~		=== blocker ===
	Impediment to software development, e.g. build breakage on most platforms, systematic crash at startup or when playing any file input.		Impediment to software development, e.g. build breakage on most platforms, systematic crash at startup or when playing any file input.

	~~'''~~critical~~''':~~		=== critical ===
	Impediment to software release, e.g. security issue, crash in most basic and common use cases (i.e. more than 50% of user base), crash at exit.		Impediment to software release, e.g. security issue, crash in most basic and common use cases (i.e. more than 50% of user base), crash at exit.

	~~'''~~major~~''':~~		=== major ===
	Basic feature not working, e.g. inputs other than file not working, file format or codec not rendered.		Basic feature not working, e.g. inputs other than file not working, file format or codec not rendered.

	~~'''~~normal~~''':~~		=== normal ===
	Expert feature not working, e.g. stream output problem, specific configuration option. Feature requests.		Expert feature not working, e.g. stream output problem, specific configuration option. Feature requests.

	~~'''~~minor~~''':~~		=== minor ===
	Problem that can be worked around easily or is really unimportant.		Problem that can be worked around easily or is really unimportant.

	~~'''~~trivial~~''':~~		=== trivial ===
	Typing error. Self-explanatory bugfixes. Inconsequential compiler warnings.		Typing error. Self-explanatory bugfixes. Inconsequential compiler warnings.

Courmisch: /* Bug resolutions */

2017-07-29T13:13:16Z

Bug resolutions

← Older revision		Revision as of 13:13, 29 July 2017
Line 113:		Line 113:

	All bugs are initially filed in the ''new'', and without a ''resolution''. If/when a bug gets closed, the resolution must be filed. The following resolutions are currently used:		All bugs are initially filed in the ''new'', and without a ''resolution''. If/when a bug gets closed, the resolution must be filed. The following resolutions are currently used:
	* ''fixed'': ~~the~~ bug has been corrected in a newer version of VLC; the fixed version should be indicated under ''milestone''.		* '''fixed''': The bug has been corrected in a newer version of VLC; the fixed version should be indicated under ''milestone''.
	* ''invalid'': ~~the~~ bug report is confusing, unintelligible, not in English, describes multiple separate issues, or is otherwise impossible for the VLC developers to analyze.		* '''invalid'''': The bug report is confusing, unintelligible, not in English, describes multiple separate issues, or is otherwise impossible for the VLC developers to analyze.
	* ''wontfix'': ~~the~~ VLC developers believe that the problem should not or cannot be addressed.		* '''wontfix''': The VLC developers believe that the problem should not or cannot be addressed.
	* ''duplicate'': a report for the same problem has already been filed earlier. There is no need to keep multiple reports for a single problem. This does not necessarily mean that the bug is fixed yet.		* '''duplicate''': A report for the same problem has already been filed earlier. There is no need to keep multiple reports for a single problem. This does not necessarily mean that the bug is fixed yet.
	* ''worksforme'': in the specified circumstances, the VLC developers are not able to reproduce the described problem, or the described "problem" is actually the intended behaviour.		* '''worksforme''': In the specified circumstances, the VLC developers are not able to reproduce the described problem, or the described "problem" is actually the intended behaviour.
	* ''notvlc'': ~~the~~ reported problem may be real, but its root cause is not within the VLC code base, and therefore the VLC developers cannot fix it. The bug should probably be reported '''somewhere else'''.		* '''notvlc''': The reported problem may be real, but its root cause is not within the VLC code base, and therefore the VLC developers cannot fix it. The bug should probably be reported '''somewhere else'''.
	* ''incomplete'': ~~the~~ bug report does not contain enough infos for the VLC developers to analyze the bug. See also above.		* '''incomplete''': The bug report does not contain enough infos for the VLC developers to analyze the bug. See also above.

	== Additional remarks ==		== Additional remarks ==

Courmisch: /* Filing a bug report */

2017-07-29T13:11:15Z

Filing a bug report

← Older revision		Revision as of 13:11, 29 July 2017
Line 79:		Line 79:
	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. Note that a single bug report must describe '''exactly one bug'''. If there are more than one bug, then as many separate bug reports should be filed.		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. Note that a single bug report must describe '''exactly one bug'''. If there are more than one bug, then as many separate bug reports should be filed.

	Bugs with insufficient infos may be closed as incomplete (or invalid in the worst cases). VLC developers understand that the requested infos can be difficult to provide ~~as a whole~~. Indeed, producing a stack trace can be complex and time-consuming. And sharing sample files can pose privacy or piracy issues. However as a bug reporter you have to accept that the VLC developers cannot resolve bugs without sufficient infos for analysis.		Bugs with insufficient infos may be closed as incomplete (or invalid in the worst cases). VLC developers understand that the requested infos can be difficult to gather or provide. Indeed, producing a stack trace can be complex and time-consuming. And sharing sample files can pose confidentiality, privacy or piracy issues. However as a bug reporter you have to accept that the VLC developers cannot resolve bugs without sufficient infos for analysis.

	Also please keep in mind that the VLC developers are not paid to solve your problems. There cannot be any warranty of any kind of timeline ~~for~~ resolution of a bug. On the one hand, some bugs have been fixed within minutes of being filed. On the other hand, some bugs have remained open for over ~~10 years~~. If you need express resolution, you should ~~try~~ to solve the problem yourself or consider hiring a software consultant.		Also please keep in mind that the VLC developers are not paid to solve your problems. There cannot be any warranty for any kind of timeline regarding resolution of a bug. On the one hand, some bugs have been fixed within minutes of being filed. On the other hand, some bugs have remained open for over a decade, with no signs of getting fixed any time soon. If you need express resolution, you should attempt to solve the problem yourself, or consider hiring a software consultant.

	== Bug severities ==		== Bug severities ==