Creating a new issue

[GRiker]

Before creating an issue for Marvin XD:

• Confirm that the issue is in fact with Marvin XD, and not with the iOS reader applications plugin. These two plugins are closely related.
• If the issue occurs after clicking the Marvin XD icon, or while the Marvin XD window is open, then create the issue here.
• Otherwise, create the issue at the iOS reader applications issue tracker.

When creating a new issue, please include:

• The version of Marvin you have installed on your iDevice (from the Home screen, tap the gear icon in the upper left, select the General tab, then touch About Marvin. The version is displayed in the window title bar.)
• A description of your iDevice including cellular technology/provider, if applicable.
• The version of calibre you have installed on your computer.
• The version of the Marvin XD plugin you have installed in calibre.
• The version of the iOS reading applications plugin you have installed in calibre.
• Your computer's operating system, and 32- or 64-bit, if applicable. For example:
  • Windows 7, 64-bit
  • OS X 10.8.4
  • Ubuntu 12.04 32-bit
• The version of iTunes installed on your computer (OS X, Windows only).
• The specific steps to recreate the problem.
• A description of the problem - what you expected, what actually happened.

Remember to create a new issue, not a comment to this issue.

I may ask you to provide a debug log. Here's how:

• Open the configuration dialog for the plugin.
• Enable the checkbox Enable debugging for plugin, click OK.
• OS X only: Open Preferences | Advanced | Miscellaneous, click Install command line tools. (You only need to do this once on your system. The command line tools will still be installed after updating calibre.)
• Accept all changes, exit calibre.
• Open a terminal or command window on your computer, then type
  calibre-debug -g > debug_log.txt. The file debug_log.txt will be created in your current directory.
• Repeat the steps necessary to cause the problem, then close calibre.
• Paste the contents of debug_log.txt into a new comment in your issue.