Skip to content

Submitting a bug report

un1versal edited this page Nov 28, 2015 · 13 revisions

Preface

We have moved our development efforts to the new 4.3 branch based on Qt4/Qt5; KVIrc 3.4.2 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 need basic information in order for us to efficiently provide you with the necessary support you require and even find a solution for your issue. So help us to help you. :)

  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.configon KVIrc and copy & paste the details from the Executable Information tab into your bug-report.

Use this syntax to make the report readable:

```
Executable Information
```

💡 Include any screenshot(s) (drag and drop to Github issue box) that help us visualize the issue you're facing.

⚠️ 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 "works for me".

If your ticket matches one of these cases below, it will be closed immediately as Invalid

  • 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 outaded KVIrc version.
  • Bogus/without information: the ticket is as short as "I can't make it work" and offers no useful information