On Thu, Feb 18, 2016 at 01:50:09PM +0100, Enrico Zini wrote:
> Another possibility to work around this without losing debug output
> could be to append it to ~/.xsession-errors instead.
>
> A workaround for poor sods until things get patched could also be to
> replace /usr/bin/kbuildsycoca4 with a wrapper that redirects
> stdout/stderr to /dev/null.
Another possibility is to have the kdebugdialog "Disable all debug
output" on by default, and only turn it off when things need debugging.
Or to have debug output off by default on all applications, and only
turn it on for the applications that need debugging.
Another workaround for people not using kde but only occasionally using
kde applications like okular is an occasional dose of
"pkill kdeinit4 -f"
Enrico
P.S.
For the records, I have run a quick experiment on an IRC channel of
generally peaceful and level headed friends:
me> if I say "kbuildsycoca4", what is the first thing that comes to
your mind?
A> apt-get purge
B> https://i.imgur.com/g1uxE.gif
C> What is that?
me> C: #643726
C> Ah, wait, THAT is the one that does THAT STUFF?
C> DIE. DIE. DIE.
from which I conclude that there is *at least* something that could be
improved with the default debugging settings with which KDE is shipped
in stable user systems.
--
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
