When I start Kate from a terminal using root rights I get this:

Code: Select all

kdesudo kate /etc/fstab
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/jan/.config/ibus/bus
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus


I have done a clean install of LinuxMint 13 KDE, but have noticed this behavior also in other distros.
What is wrong with my system that I get all these messages?

Thanks

These messages are all innocuous, and for many of them, changes in the latest version of Qt and KDE have fixed the majority of them.

The IBus related messages are likely because your system is configured to use the IBus IM system (for keyboard layouting I believe) but it is not running. This is relatively harmless and can be ignored however.

The kbuildsycoca4 message is because you have not recently run a KDE application as root.

DeMus wrote:...
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
...
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

bcooksley wrote:These messages are all innocuous.

I find it less than reassuring when I receive multiple messages stating my application may misbehave no matter how innocuous the messages may be!

(I found these messages both in Linux Mint 13 and Fedora 17.)

You can always disable the debug output in the "kdebugdialog" program, in case you want to get rid of it. Most of the messages kate (or actually, most KDE apps) print to the terminal are pretty meaningless to someone using the application.

Greetings

From what I am aware, the QDBusConnection messages are considered warnings from Qt itself, and thus bypass the KDE debugging settings.

Hm, right. Sorry about that.