baloo search doesn't work with kdelibs4 in kubuntu vivid by default

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

I guess it affects me.

I have Kubuntu 15.04.

if I install baloo4 and run baloosearch it complains that the database isn't open

if I install libqt4-sql-sqlite this gets fixed and qt4 baloosearch now works

alas this doesn't help kioclient ls baloosearch://?query=foo which continues not to return anything

turning on debugging in kdebugdialog gives me:

>kioclient ls baloosearch://?query=foo
unnamed app(2596) ClientApp::doIt: Creating ClientApp
kioclient(2596)/kio (Scheduler) KIO::SchedulerPrivate::doJob: KIO::SimpleJob(0xa54510)
kioclient(2596)/kio (Scheduler) KIO::SchedulerPrivate::protoQ: creating ProtoQueue instance for "baloosearch"
kioclient(2596)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-jrmHGm2i/ksycoca4"
kioclient(2596)/kio (Scheduler) KIO::ProtoQueue::ProtoQueue: m_maxConnectionsTotal: 20 m_maxConnectionsPerHost: 20
kioclient(2596)/kio (Slave) KIO::Slave::createSlave: createSlave "baloosearch" for KUrl("baloosearch://?query=foo")
kioclient(2596)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on "local:/run/user/1000/ksocket-jr/kioclientZT2596.slave-socket"
kioclient(2596)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished: KIO::ListJob(0xa54510) KIO::Slave(0xa6daf0)
QCoreApplication::postEvent: Unexpected null receiver
kioclient(2596)/kio (Slave) KIO::Slave::kill: killing slave pid 2597 ( "baloosearch://" )

Seems the issue is the syntax in the io slave is different. After installing qtsqlite plugin it works in dolphin

A query like this does work on the command line
kioclient ls "baloosearch://?json=%7B%20%22customOptions%22%20:%20%7B%20%22includeFolder%22%20:%20%22/home/%22%20%7D,%20%22term%22%20:%20%7B%20%22$and%22%20:%20%5B%20%7B%20%22filename%22%20:%20%7B%20%22$ct%22%20:%20%22foo%22%20%7D%20%7D%20%5D%20%7D,%20%22type%22%20:%20%5B%20%22File%22%20%5D%20%7D&title=Query%20Results%20from%20'foo'"

So once the new baloo4 migrates to vivid problem solved. This is only blocked by a random failing test on kde-baseapps
 which I guess I'll patch out.
https://jenkins.qa.ubuntu.com/job/vivid-adt-kde-baseapps/ARCH=amd64,label=adt/53/console

Even after releasing the fix, bug 1432853 is still not fixed.

I have the same bug as well on kubuntu 15.04