Happy New Year all, here's my first bug of the year.

Using Kontact on Mint 18.3 (KDE) it's been fine for ages then yesterday, this:

Kontact opens in Kmail which works fine. Choosing other modulkes from the sidebar I find Contacts (Kaddressbook) or Calendar (Korganizer) cause Kontact to crash. Other modules do not.

Running from a terminal doesn't provide much info except an invalid socket warning.

KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kontact path = /usr/bin pid = 5702
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 51 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 27 and type 'Read', disabling...

[1]+  Stopped                 kontact

Following a crash the app has clearly not exited properly because socket errors keep on coming until I close the terminal.

phil@phil-desktop ~ $ QSocketNotifier: Invalid socket 53 and type 'Read', disabling...
QSocketNotifier: Invalid socket 44 and type 'Read', disabling...
QSocketNotifier: Invalid socket 49 and type 'Read', disabling...
QSocketNotifier: Invalid socket 41 and type 'Read', disabling...
QSocketNotifier: Invalid socket 46 and type 'Read', disabling...

Running Korganizer direct from a terminal is OK. Running Kaddressbook isn't. It opens for a fraction of a second, just long enough to see the window, then crashes. Similar error messages to the above.

As I have little idea what a socket is, I'm stumped!

The KDE reporting tool reports that the log isn't detailed enough to bother with and I can't find any useful advice online. Help?!

--

Phil Thane

www.pthane.co.uk

phil@pthane.co.uk

01767 449759

07582 750607

Twitter @pthane