Kontact often crashes when switching to another tab. How best to create a useful bug report?

[Bas G. Roufs - in English]

Hello Everybody. 

Kontact at Kubuntu 16.04 LTS (Xenial) still has some points of attention. 
Here, I deal with just one of them. The package often crashes when switching 
from the list of e-mails to another tab. Especially a switch to Contacts, 
Calendar or To-Do ends up in a crash. Is there any fix or workaround?

At present, my laptop is running on a 32 bits version of Kubuntu 16.04 LTS 
along with KDE Plasma 5.8.4. My laptop is an old Asus Eee PC 1001 HA, with 2 
processors of 1.6 Ghz each, 2 GiB RAM. It works with a new 500 GB SSD (Samsung 
Evo). 

For debugging purposes, I have started Kontact from the terminal. Below, I 
share with you just a short version of a huge output file:

bas at Viaconsensus-transit:~$ kontact

(.....snip .....)

At this point, the package starts. However, the upper part of the terminal 
report is not any more visible. The first about 1000 lines that are still 
visible, start like this:

(.....snip .....)

log_messagelist: Circular In-Reply-To reference loop detected in the message 
tree
log_messagelist: Circular In-Reply-To reference loop detected in the message 
tree
log_messagelist: Circular In-Reply-To reference loop detected in the message 
tree
log_messagelist: Circular In-Reply-To reference loop detected in the message 
tree
log_messagelist: Circular In-Reply-To reference loop detected in the message 
tree
log_messagelist: Circular In-Reply-To reference loop detected in the message 
tree

(.....snip .....)

org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
*** KMail got signal 11 (Exiting)
*** Dead letters dumped.
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kontact path = /usr/bin pid = 2924
KCrash: Arguments: /usr/bin/kontact 
KCrash: Attempting to start /usr/lib/i386-linux-gnu/libexec/drkonqi from 
kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 48 and type 'Read', disabling...
QSocketNotifier: Invalid socket 81 and type 'Read', disabling...

[1]+  Stopped                 kontact
bas at Viaconsensus-transit:~$ QSocketNotifier: Invalid socket 43 and type 'Read', 
disabling...
QSocketNotifier: Invalid socket 22 and type 'Read', disabling...
QSocketNotifier: Invalid socket 37 and type 'Read', disabling...
QSocketNotifier: Invalid socket 73 and type 'Read', disabling...
QSocketNotifier: Invalid socket 35 and type 'Read', disabling...
QSocketNotifier: Invalid socket 31 and type 'Read', disabling...
QSocketNotifier: Invalid socket 26 and type 'Read', disabling...
QSocketNotifier: Invalid socket 39 and type 'Read', disabling...
QSocketNotifier: Invalid socket 20 and type 'Read', disabling...
QSocketNotifier: Invalid socket 33 and type 'Read', disabling...
QSocketNotifier: Invalid socket 24 and type 'Read', disabling...
QSocketNotifier: Invalid socket 45 and type 'Read', disabling...
QSocketNotifier: Invalid socket 29 and type 'Read', disabling...
QSocketNotifier: Invalid socket 47 and type 'Read', disabling...
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
QSocketNotifier: Invalid socket 71 and type 'Read', disabling...
QSocketNotifier: Invalid socket 83 and type 'Read', disabling...
QSocketNotifier: Invalid socket 77 and type 'Read', disabling...
QSocketNotifier: Invalid socket 75 and type 'Read', disabling...
QSocketNotifier: Invalid socket 79 and type 'Read', disabling...

(Last line of the terminal output report.)

At this point, the process stopped all together. 
Let me know please, whether this info is useful for a bug report. Is there 
anything else I need to look at when creating this report?

Yours.

Bas G. Roufs.