The easiest way to contribute is to spread the word about digiKam. We also encourage you to test digiKam, report bugs, and submit feature requests. You might also want to subscribe to the digikam-users mailing list and help other digiKam users with their questions and problems.
Reporting Bugs and Submitting Feature Requests
Use the bug tracking system for all bug reports and new feature requests. Take a look at the support page for further information.
Dealing with Crashes in digiKam
In case digiKam crashes, you can provide a backtrace using GDB debugger. digiKam needs to be compiled with all debug info; otherwise the backtrace will be useless. If you installed digiKam using the packages provided by your distribution, make sure to install the corresponding debug package. The debugging guide provides further information on debugging.
Instructions how to get into GDB on various platforms are below. When you are in GDB and digiKam crashes, you will get to the GDB command prompt. If digiKam “just” freezes, press ctrl-c to get to the GDB prompt. Once you are at the prompt, use the bt command, copy the backtrace and exit GDB as shown here:
(gdb) bt (gdb) _the backtrace is here_ (gdb) quit
On Linux if you use a regular binary, i.e. no AppImage, use the following command to get into GDB and start digiKam:
$ gdb digikam (gdb) catch throw (gdb) run
If you use an AppImage, replace the name of the AppImage with the one you have and run:
$ digikam-5.7.0-01-x86-64.appimage debug
On Windows, the binary installer comes with a DrMinGw crash course handler, which will generated a file backtrace in you home directory as below:
Under MacOS, users can run lldb debugger as follows:
Checking for Memory Leaks
To check for memory leaks in digiKam, use the valgrind tool. Run the command below, and report the trace to developers:
valgrind --tool=memcheck --leak-check=full --error-limit=no digikam
Freezes and Other Issues
On Linux, run digiKam from the command line to get the output generated by the application. On macOS, digiKam executable is installed in /opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam, and you can use it to start the application from the command line to view debug traces. On Windows, trace is not sent to the console. You need to install DebugView tool to capture debug traces generated by digiKam.
Before you submit patches, please read the HACKING section from online API documentation. Send patches against the current version of the code (latest git/master revision) and not the stable release or an old beta version. Patches can be created using the following command:
git diff HEAD > mydiff.patch
The patches must be attached to a new entry in Bugzilla. Please do not use mailing lists or private mail.
Help with digiKam documentation is always welcome. For all documentation-related matters, write to digiKam-devel mailing list. Our documentation is based on the docbook format standard. The README file explains in detail how structure the documents, take screenshots, etc.
It’s also possible to submit additions and changes in the ASCII format. To do this, create a new Bugzilla entry with a patch against git/master code, so it can be incorporated in the documentation.
We need raw and JPEG files from different manufacturers (Canon, Nikon, Sony, Olympus, Sigma, etc.). We use these files to analyze embedded metadata to improve camera support in digiKam. We also need sample files produced by different applications (including other platforms and proprietary software like Adobe Photoshop) that include IPTC/XMP metadata. This can help us to improve compatibility with other tools and implement automatic import of this data into the digiKam database.
As a photographer, you can submit your best photos for use as digiKam splash screen. Take a look at this page for further information.