Skip to main content
If you come across any bugs in OpenComic — even minor ones — please report them. Your bug reports help us improve the application for everyone.

​
Before reporting

Before submitting a bug report, please:
1

Check existing issues

Search the existing issues to see if your bug has already been reported. This helps avoid duplicates and lets you add information to existing reports.
2

Verify it's reproducible

Try to reproduce the bug to confirm it’s consistent and not a one-time occurrence.
3

Update to latest version

Make sure you’re running the latest version of OpenComic, as the bug may have already been fixed.

​
How to report a bug

We use GitHub Issues to track bugs for OpenComic.

Report a Bug

Create a new issue on GitHub

​
Information to include

When submitting a bug report, please include as much relevant information as possible to help us reproduce and fix the problem quickly:

​
Required information

Provide a clear and concise description of what the bug is and what you expected to happen.
List the exact steps to reproduce the behavior:
  1. Go to ’…’
  2. Click on ’…’
  3. Scroll down to ’…’
  4. See error
Include details about your environment:
  • Operating System: Windows, macOS, or Linux (include version)
  • OpenComic Version: Check in Help > About OpenComic
  • Installation Method: Installer, portable, Snap, Flatpak, AppImage, etc.

​
Optional but helpful

Visual aids can help explain the problem more clearly. Include screenshots or screen recordings if applicable.
If the bug is related to a specific comic file or format, consider providing:
  • The file format (CBZ, CBR, PDF, etc.)
  • File size and structure details
  • A sample file if possible (without copyright concerns)
Include any error messages or console output you see. If available, check:
  • Developer Tools console (if you can access it)
  • Application logs
Mention how often the bug occurs:
  • Always
  • Sometimes
  • Only under specific conditions

​
What happens next

After you submit a bug report:
  1. Maintainers will review - The OpenComic team will review your report
  2. You may be asked for more information - We might ask follow-up questions to better understand the issue
  3. The bug will be prioritized - Based on severity and impact
  4. You’ll be notified - You’ll receive updates on the issue through GitHub
Be patient - the OpenComic team consists of volunteers who work on the project in their free time.

​
Tips for effective bug reports

  • Be specific: Vague descriptions make bugs harder to fix
  • Be concise: Include relevant details but avoid unnecessary information
  • Be respectful: Remember that maintainers are volunteers
  • Follow up: Respond to questions from maintainers promptly
  • One bug per report: Don’t combine multiple unrelated bugs in one issue

​
Other ways to help

If you’re interested in contributing beyond bug reports:

Contributing Guide

Learn how to contribute code to OpenComic

Translations

Help translate OpenComic into your language

Build docs developers (and LLMs) love

Get started for freeTalk to us