How to Submit a Bug Report

1. ​Search existing bug reports and don't submit a duplicate report.
2. ​Create a new ticket.
   Note: You must be logged in!

Windows Users

DLL Hell and Win Pidgin

A very common but very unpleasant Windows SNAFU (known as DLL Hell) has been experienced by many Win Pidgin users.

Symptom: Win Pidgin crashes routinely on startup (but not necessarily just on startup).

Cause: Dlls with the same name as those that Pidgin uses are found in the dll search path and are used instead of those installed by Pidgin, likely causing Pidgin to malfunction. This can happen when application developers install their dlls to Windows system directories. The most commonly used dll to cause dll hell is zlib.dll.

What to do if Pidgin crashes

First make sure that you are not affected by 'Dll Hell' as described above. Download and install the debug version of Win Pidgin. The next time you run Pidgin and it crashes, the call stack will be dumped to pidgin.RPT in your Pidgin install dir. When submitting a bug report, give a detailed description on how to produce your bug and attach the most recent crash dump from your pidgin.RPT

Obtaining a Debug Log

If asked to obtain a debug log, the following steps will help you do so.

If Pidgin isn't crashing, you can use the Debug Window (Help->Debug Window) to obtain the debug log output.

If Pidgin is crashing, you can save the debug output to a file by opening a cmd shell and starting Pidgin as follows:
(You should replace C:\Program Files\Pidgin with the path to which you installed Pidgin if it is different)

cd "C:\Program Files\Pidgin"
pidgin.exe -d > debug.log

This will cause the debug output to be saved in a file called debug.log.

All Other Users

See our Getting a Backtrace page.