Unable to Display System Logs because KDEInit won't launch.

[Denis Meiswinkel]

Using the newest Daily Build at the moment ( Kubuntu Plasma 5 Desktop amd642014-09-30 01:50 ) in a VM made in VirtualBox.

If I try to launch "KSystemLog" the System displays this Error Message:

http://imgur.com/C9IRGja

KDEInit could not launch ":
Could not open library'/usr/lib/x86_64-linux-gnu/libkdeinit5_'.
Cannot load library /usr/lib/x86_64-linux-gnu/libkdeinit5_:(/usr/lib/x86_64-linux-gnu/libkdeinit5_.so: cannot open shared object file: No such file or directory)

Running "ksystemlog" from the Terminal is working fine but prints these errors:

kubuntu-plasma-5@kubuntu-plasma-5:~$ ksystemlog
ksystemlog(6073)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory!
ksystemlog(6073)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory!
ksystemlog(6073)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory!
ksystemlog(6073)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory!
ksystemlog(6073)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory!
ksystemlog(6073) LogManager::isParsingPaused: Log manager is not yet initialized

QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/kubuntu-plasma-5/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon

[Arthur Bogard (arthur-bogard-gmail)]

I receive the same error when trying to run synaptic package manager through kickoff. I believe it has to do with elevated privs, but I don't see this error when launching gparted. I also do not see this error when launching synaptic through kickoff without elevating the privs. When I run it through the terminal, all is well and I receive no errors.

[phil (wrigsster-deactivatedaccount)]

I also receive the same error when trying to run Synaptic Package Manager. No matter how many times I reset, Restart, Shut down there is the same error.

[Juergen Scholz (juergen.scholz)]

I am running vivid on an Phenom X2 (read: real hardware), this also happens to me. I can start all other programs I tested.

[Sergei Krasnov (kartas39)]

I have the same problem with KSystemLog

[Bruno (bruno666-666)]

Possible workaround :

sudo ln -s /usr/bin/kdesudo /usr/bin/kdesu

[Diego-MX (diego-mx)]

I had the same error, and Bruno's workaround did it.

[glepore70 (greg-rhobard)]

Not sure if my bug is related, but when I double click on a text file in Dolphin, I get the message "Sorry - Dolphin. KDEInit could not launch /usr/bin/kate". However, Kate actually launches.

[OvermindDL1 (overminddl1)]

Same with the kate message, the workaround in #5 did not correct it.

[Simon Quigley (tsimonq2)]

Thank you for taking the time to report this bug and helping to make Kubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Kubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Kubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1375619

and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for Kubuntu PPA because there has been no activity for 60 days.]