Submitting a bug report

Preface

We have moved our development efforts to the new 5.x branch based on Qt4/Qt5; KVIrc 4.2.x has been deprecated and is no longer officially supported.

Below find outlined some requirements for submitting bug reports.
ℹ️ Ticket validity is enforced at our own discretion on a case by case basis.

Information required when making a bug-report via GitHub issues.

We now provide a default issue template (you should see it when creating an issue), this should make the process of submitting a bug report along with the required information much easier for you.
This contains essential information in order to help us efficiently provide to you the best support possible and find a solution for your issue. So help us to help you. 😄

⚠️ Bug reports that dont satisfy the minimum requirements will be initially tagged as .
You will be asked to provide this information in order to tag and process your ticket properly. We should not have to chase users for providing essential information that may help find the issue easily, its a waste of time.

1. Enter a descriptive title for the bug-report i.e. something it describes the issue your facing.
2. Try to describe your issue in a detailed manner and list the necessary steps to reproduce issue or crash.
3. Type /about.kvircon KVIrc and copy & paste the details from the Executable Information tab into your bug-report.
4. Also Enter any OS information the "Executable Information" tab doesn't contain, e.g. KDE, Gentoo, Linux Mint, etc.

💡 Include any screenshot(s) (see adding a screenshot to your issue) that help us visualize the issue you're facing.

Use this syntax to make the report readable:

```
Executable Information
```

⚠️ When reporting a crash, please attach a backtrace of the crash (if possible). This will speed up our work in solving the bug. If you don't know how to create a backtrace, read the following page: Useful backtrace

```
stack trace goes here
```

Information required when making a bug-report via IRC #KVIrc channel on freenode.

Again the best you can do is provide as much info as possible, but tell us the following:

1. Describe your issue in some detail.
2. Provide operative system Information e.g. Windows XP,7,8 etc. or Linux Ubuntu, Mandriva, Debian etc. or OS X Lion, Yosemite, etc.
3. Type /say /$version followed by Enter.
4. Be patient; wait for a reply from on of our friendly community members or a KVIrc Development Team person.

Ticket validity

🎏 Foreign languages: we accept tickets in English only.

Every bug reported will have to be confirmed or reproduced by other users in an initial period (usually 3/4 weeks). If a ticket is not reproducible by nobody after that time, it will be closed as .

⚠️ If your ticket matches one of these cases below, it will be labeled immediately as , in some cases even closed.

❗ Duplicate report: the bug has already been reported in another ticket; if the ticket was already closed, ask to reopen it.
❗ Old KVIrc version: the bug is reported against an outdated KVIrc version.
❗ Bogus/without information: the ticket is as short as "I can't make it work" and offers no useful information.