Update to include details on gettings logs, normally and when crash

troubleshooting/troubleshooting.rst

@@ -21,36 +21,87 @@ If you have problems using Picard, please first check the following resources:
 :index:`Reporting a Bug <troubleshooting; 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 the `bug tracker <https://tickets.musicbrainz.org/browse/PICARD>`_. If you're not
-sure or don't want to look through the existing tickets, ask on the community forums first.
+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 the `bug tracker <https://tickets.musicbrainz.org/browse/PICARD>`_. If you're not sure or don't want to look through the existing tickets, ask on the community forums first.
 
-If you're still convinced you have found a new bug, open a `new ticket
-<https://tickets.musicbrainz.org/secure/CreateIssue.jspa?pid=10042&issuetype=1>`_ providing the following information:
+If you're still convinced you have found a new bug, open a `new ticket <https://tickets.musicbrainz.org/secure/CreateIssue.jspa?pid=10042&issuetype=1>`_ providing the following information:
 
 * Which version of Picard do you use? ("Affects Version" in the form)
 * Which operating system do you use? ("Environment" in the form)
 * What did you do when the bug occurred?
-* What actually happened and what did you expect to happen?
+* What actually happened, and what did you expect to happen?
 * If you're using plugins, which plugins do you have enabled?
+* The **"Debug"** level log from the Picard session demonstrating the problem.
 
+.. warning::
 
-:index:`Getting Logs <troubleshooting; logs>`
-----------------------------------------------
+   Please remember to first remove any personal and confidential information like user id, passwords or authorization tokens before posting or submitting any log output.
 
-For many bugs, it helps developers to have a log from Picard. You can see the log by going to :menuselection:`"Help --> View Log"`.
-You can also get a full debug log (better because it contains more detailed information) by starting Picard with :option:`-d` as a
-command-line argument. If you're using Windows, you can change your shortcut's Target (:menuselection:`right click shortcut -->
-Properties`) to::
 
-    "C:\Program Files\MusicBrainz Picard\picard.exe" -d
+:index:`Getting a Debug Log <troubleshooting; get debug log>`
+-------------------------------------------------------------
 
-Pasting this log into your forum post or bug ticket can help developers and other users to resolve your issue more quickly.
+For many bugs, it helps developers to have a log from Picard. You can see the log by going to :menuselection:`"Help --> View Log"`. You can also get a full debug log, which is better because it contains more detailed information. Pasting this log into your forum post or bug ticket can help developers and other users to resolve your issue more quickly. To retrieve the full debug log:
 
-.. warning::
+1. Start Picard.
+2. Open the log view with :menuselection:`"Help --> View Log"`.
+3. Change the log level :guilabel:`verbosity` to **Debug**.
+4. Close the log viewer.
+5. Close and restart Picard.
+6. Repeat the action that caused the problem being reported.
+7. Open the log viewer and copy the output to paste into the forum post or bug ticket. Alternately, you can save the log to a file to attach to your bug report by using the :guilabel:`Save As...` button.
+8. Close the log viewer, and close Picard.
+
+
+:index:`Getting Logs in Case of Crashes <troubleshooting; getting log for chashes>`
+-----------------------------------------------------------------------------------
+
+In some cases the problem will cause Picard to crash and not allow you to access the resulting log from the log viewer. You can still generate a log output to attach to your report by starting Picard with the ``-d`` command line option from a command / terminal window and copying the information output to the terminal. The steps to follow for each of the supported platforms are:
+
+Windows Systems
++++++++++++++++
+
+First open a command window by clicking the search icon on the Windows Taskbar and enter "cmd". Then start Picard by entering the following in the command window:
+
+.. code::
+
+   "C:\Program Files\MusicBrainz Picard\picard.exe" -d
+
+This will display all log information in the command window, and allow you to copy the information to the clipboard to paste into your report.
+
+.. note::
+
+   This method will only work with the installed version of Picard.  It will not work with the portable version.
+
+
+macOS Systems
++++++++++++++
+
+First open a terminal window by doing one of the following:
+
+- Click the Launchpad icon in the Dock, type "Terminal" in the search field, then click :guilabel:`Terminal`.
+
+- In the Finder, open the "/Applications/Utilities" folder, then double-click "Terminal".
+
+Assuming Picard was put into the system wide Applications folder when installed, it can then be started by entering the following in the terminal window:
+
+.. code::
+
+   "/Applications/MusicBrainz Picard.app/Contents/MacOS/picard-run" --debug
+
+This will display all log information in the terminal window, and allow you to copy the information to the clipboard to paste into your report.
+
+
+Linux Systems
++++++++++++++
+
+First open a Terminal window. Then start Picard by entering the following in the terminal window:
+
+.. code::
+
+   picard -d
+
+This will display all log information in the terminal window, and allow you to copy the information to the clipboard to paste into your report.
 
-   Please remember to first remove any personal and confidential information like user id, passwords or authorization tokens
-   before posting or submitting any log output.
 
 .. only:: html and not epub