Baloo crash after first start on Kubuntu 16.04 (OEM Install)

[Andrea Crescentini]

After installing Kubuntu 16.04 as OEM at the first start up (OEM Configurator Mode) kde_ui.py installer crash.

Details:
Eseguibile: baloo_file PID: 1055 Segnale: Segmentation fault (11)

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1512849

[Mario (ub-mario)]

The crash is always present (02/07/2016). There was no resolution

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[sengerandu (sengerandu)]

I am getting this on the terminal

sushanta@CAE-Setup:~$ balooctl enable
Enabling the File Indexer
sushanta@CAE-Setup:~$ org.kde.baloo: "/home/sushanta"
Power state changed
KCrash: Attempting to start /usr/bin/baloo_file from kdeinit
sock_file=/run/user/1000/kdeinit5__1
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = baloo_file path = /usr/bin pid = 2707
KCrash: Arguments: /usr/bin/baloo_file
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__1
QSocketNotifier: Invalid socket 4 and type 'Read', disabling...
QSocketNotifier: Invalid socket 6 and type 'Read', disabling...
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 5 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 7 and type 'Exception', disabling...