MusicBrainz Picard/Troubleshooting: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(Add info on getting logs, some tips on logging better tickets)
(manually redirecting anyone naughtily linking to the wiki instead of /doc/)
 
(11 intermediate revisions by 5 users not shown)
Line 1: Line 1:
#REDIRECT [[MusicBrainz Picard]]
<small>[[Products]] > [[Picard Tagger|Picard]] > Picard FAQ </small>

== Getting help ==
If you have problems using Picard, please first check the following resources:

* For general usage information see the [[Picard Documentation|documentation]] and the [[How To Tag Files With Picard|illustrated quick start guide]]
* Read the [[Picard FAQ|FAQ]] for common questions and problems
* Consult the [http://forums.musicbrainz.org/viewforum.php?id=2 forums].
* Check the [[MusicBrainz Picard|download page]] for a newer version of Picard which might solve your problem
* If the problem is to do with a plugin, check the [[Picard Plugins]] for updated plugin versions

== Reporting a bug ==
If you think you have found a bug please check whether you are using the [[MusicBrainz Picard|latest version]] of Picard and whether the bug has already been reported in our [http://bugs.musicbrainz.org/report/5 bug tracker]. If you're not sure or don't want to look through the existing tickets, ask on the [http://forums.musicbrainz.org/viewforum.php?id=2 forums] first.

If you're still convinced you have found a new bug, open a [http://bugs.musicbrainz.org/newticket?component=Picard+Tagger new ticket] providing the following information:

* Which version of Picard do you use? ('''Version''' in the form)
* Which operating system do you use? ('''OS''' in the form)
* What did you do when the bug occurred?
* What actually happened and what did you expect to happen?
* If you're using plugins, which plugins do you have enabled?

Please leave the '''Milestone''' empty, and do not increase the '''Priority''' - usually that is for developers and [http://en.wikipedia.org/wiki/Bug_triage bug triagers] to decide.

=== Getting logs ===
For many bugs, it helps developers to have a log from Picard. You can see the log by going to '''Help''' >> '''View Log'''. You can also get a full debug log (even better) by starting Picard with '''-d''' as a command-line argument. If you're using Windows, you can change your shortcut's ''Target'' (right click shortcut >> '''Properties''') to <pre>"C:\Program Files\MusicBrainz Picard\picard.exe" -d</pre> Pasting this log into your forum post or bug ticket can help developers and other users to resolve your issue more quickly.

[[Category:MusicBrainz Picard]]

Latest revision as of 21:16, 25 November 2014

Redirect to: