On Sun, Jan 26, 2014 at 12:57:17PM +0100, Vincent Lefevre wrote: > This is worse than that: even if no applications are attached to the > terminal (except the shell) and no applications are even running in > foreground or background in the terminal, I still get spam by > kbuildsycoca4 in the terminal (e.g. when doing a package upgrade > from *another* terminal). > > It doesn't output just a few lines, but hundreds of lines! Due to > this bug, I've lost the temporary data that were in this terminal. > According to the Debian severity rules, this should be "grave" > because of data loss.
Ack to that. This behaviour basically means that if I had ever started a kde app on a terminal, days later that terminal could suddently become useless regardless of what I was doing on it. 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. This is hitting so hard on my basic perception of common sense that I start having really really weird reactions when I see the name "kbuildsycoca4" popping up again. Enrico who will now go and close and reopen a terminal. Again. Again. AGAIN. -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
