Difference between revisions of "KDE PIM/Development/Bug Reports"

Jump to: navigation, search
(howto get usefull logs)
 
Line 24: Line 24:
 
* [http://bugs.kde.org/buglist.cgi?product=korganizer&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED All open KOrganizer bugs]
 
* [http://bugs.kde.org/buglist.cgi?product=korganizer&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED All open KOrganizer bugs]
 
* [http://bugs.kde.org/buglist.cgi?product=kaddressbook&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED All open KAddressBook bugs]
 
* [http://bugs.kde.org/buglist.cgi?product=kaddressbook&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED All open KAddressBook bugs]
* [http://bugs.kde.org/buglist.cgi?product=kpilot&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED All open KPilot bugs]
 
 
* [http://bugs.kde.org/buglist.cgi?short_desc_type=regexp&short_desc=JJ.*&product=akregator&product=kaddressbook&product=kalarm&product=kandy&product=karm&product=kitchensync&product=kmail&product=knode&product=knotes&product=konsolekalendar&product=kontact&product=korganizer&product=kpilot&product=ktnef&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED KDE PIM Junior Jobs]
 
* [http://bugs.kde.org/buglist.cgi?short_desc_type=regexp&short_desc=JJ.*&product=akregator&product=kaddressbook&product=kalarm&product=kandy&product=karm&product=kitchensync&product=kmail&product=knode&product=knotes&product=konsolekalendar&product=kontact&product=korganizer&product=kpilot&product=ktnef&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED KDE PIM Junior Jobs]
  
 
= IMAP log =
 
= IMAP log =
  
If you use problems with an IMAP or kolab resource than an IMAP log can be very usefull, because a developen 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 suff inside. Have a look into the IMAP log before sending it around.
+
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
 
     KIMAP_LOGFILE=/tmp/imap.log akonadictl restart
  
Afterwards you find for each imap connection a file /tmp/imap.log.<PID>.<ID>.
+
Afterwards you find for each IMAP connection a file /tmp/imap.log.<PID>.<ID>.
  
= akonadi log =
+
= Akonadi Log =
  
Having problems with akonadi and/or one resource its often helpfull to get log. There are different levels where usfull information can be.
+
Having problems with Akonadi and/or one resource its often helpful to get log. There are different levels where usfull information can be.
  
== console output ==
+
== Console Output ==
  
Developvers put many debug logs into there code to make it esay to follow, that is going on, when. But by default these informations are not displayed. So we should start and activate them:
+
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:
  
 
   kdebugdialog
 
   kdebugdialog
  
search for akonadi and select everything that is involed in your problem. Maybe also you should activate something like kssl, kio,... depending on your problem. Afterwards just restart akonadi:
+
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:
  
 
   akonadictl restart
 
   akonadictl restart
  
Than you see the log in the console.
+
Then you see the log in the console.
 
 
== using akonadiconsole ==
 
 
 
Akonadiconsole is a very good debug tool.
 
 
 
[[File:akonadiconsole.png]]
 
 
 
start akonaidconsole
 
 
 
1. select the debugger tab
 
 
 
2. activate debugger
 
 
 
do what every you want to debug
 
 
 
3. search for the matching tab
 
 
 
4.  save logs to file
 
  
 
= Statistics =
 
= Statistics =
  
 
* [https://bugs.kde.org/weekly-bug-summary.cgi KDE-wide weekly bug summary]
 
* [https://bugs.kde.org/weekly-bug-summary.cgi KDE-wide weekly bug summary]

Latest revision as of 15:27, 27 July 2017

Reporting Bugs

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:

IMAP log

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>.

Akonadi Log

Having problems with Akonadi and/or one resource its often helpful to get log. There are different levels where usfull information can be.

Console Output

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:

 kdebugdialog

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:

 akonadictl restart

Then you see the log in the console.

Statistics


This page was last edited on 27 July 2017, at 15:27. Content is available under Creative Commons License SA 4.0 unless otherwise noted.