Bugs of KDE PIM applications should be reported at bugs.kde.org. This includes feature requests which should be reported as wishlist items. There is a bug reporting wizard which asks for all relevant information and then creates an entry in the bug tracking system.
To make your bug report as useful as possible you should keep some things in mind:
- Check that the bug hasn't been reported before.
- Tell us how to reproduce the bug
- Include all relevant information about KDE version, operating system, special configurations, etc.
- Keep in mind that we do care about bug reports, but that most of us work on KDE in their spare time and might not be able to address the bug immediately.
Querying bug reports
You can query bug reports on the generic KDE Bugzilla query page. Here are some predefined queries:
- All open kdepim bugs
- All open Kontact bugs
- All open KMail bugs
- All open KOrganizer bugs
- All open KAddressBook bugs
- KDE PIM Junior Jobs
If you use problems with an IMAP or Kolab resource than an IMAP log can be very useful, because a developer can really see that is sent/received from the IMAP server. Please be aware, that the IMAP log shows all content, so there can be very private stuff inside. Have a look into the IMAP log before sending it around.
KIMAP_LOGFILE=/tmp/imap.log akonadictl restart
Afterwards you find for each IMAP connection a file /tmp/imap.log.<PID>.<ID>.
Having problems with Akonadi and/or one resource its often helpful to get log. There are different levels where usfull information can be.
Developers put many debug logs into there code to make it easy to follow, that is going on, when. But by default these information are not displayed. So we should start and activate them:
search for akonadi and select everything that is involved in your problem. Maybe also you should activate something like kssl, kio,... depending on your problem. Afterwards just restart akonadi:
Then you see the log in the console.