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)
No edit summary
Line 1: Line 1:
<small>[[Products]] > [[Picard Tagger|Picard]] > Picard FAQ </small>
<small>[[Products]] > [[Picard Tagger|Picard]] > Picard Troubleshooting </small>


== Getting help ==
== Getting help ==

Revision as of 16:58, 14 July 2011

Products > Picard > Picard Troubleshooting

Getting help

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

Reporting a bug

If you think you have found a bug please check whether you are using the latest version of Picard and whether the bug has already been reported in our bug tracker. If you're not sure or don't want to look through the existing tickets, ask on the forums first.

If you're still convinced you have found a new bug, open a 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 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

"C:\Program Files\MusicBrainz Picard\picard.exe" -d

Pasting this log into your forum post or bug ticket can help developers and other users to resolve your issue more quickly.