When running KDE applications from the command line, they often produce a lot of debugging output. For example:

Code: Select all

$ okular foo.pdf
okular(23596)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory!
okular(23596) PageView::mouseReleaseEvent: checking if page 3 has text: false
okular(23596) PageView::mouseReleaseEvent: checking if page 4 has text: false
okular(23596) PageView::mouseReleaseEvent: checking if page 5 has text: false
okular(23596)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x70aa48 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.

Lately I've taken to wrapping these noisy applications in shell scripts which direct their output to the bit bucket:

Code: Select all

#!/bin/bash
/usr/bin/okular $@ >&/dev/null &


Needless to say this isn't particularly convenient. Is there some way of disabling debugging output for KDE applications globally? I already have "Disable all debug output" checked in kdebugdialog so I don't know what else to try.

In this case these messages are likely warning messages, which from what I recall cannot be suppressed. Just in case there is a subtle bug, can you make sure all debug areas are unchecked in kdebugdialog, as well as "Disable all debugging output" being checked?

I'm not sure that all the messages are indeed warnings as opposed to logger output for run-of-the-mill operations. For example, in the Okular output I quoted above, the "PageView::mouseReleaseEvent: checking if page x has text" messages are simply what is displayed whenever one makes a selection with the mouse.

In response to your question, though, yes, all the checkboxes for the individual applications in kdebugdialog are unchecked.

Unfortunately it appears that those messages have been marked as "warnings" in the Okular codebase, so they cannot be suppressed. The other two messages are also warnings as well.

Not much that can be done here i'm afraid.