Hello Brian, "brian m. carlson" <sandals@crustytoothpaste.net> > Attached is a patch fixing the problem. It is untested, since I don't > feel like installing all the dependencies to build kde4libs. You could > also just define KDE_NO_DEBUG_OUTPUT, but that might be a bit much. > > Just as a note, this bug has been present in KDE for at least the last > decade. I didn't mean to be so blunt, but as a non-KDE user, it pops up > at the most inconvenient times, and it is rather annoying when it does, > since it forces me to abandon a terminal that I'm working in, usually > with 20000 lines of important scrollback. while I'm not part of the Debian Qt/KDE team anymore, I can tell you this patch shouldn't be included because apparently it just silents the debug output of kbuilsycoca4 which doesn't seem very appropiate. However not everything are bad news for you: to fix your problem, you just can execute "kdebugdialog" and disabled the debug output. Disabling it patching kdelibs like that isn't a good solution because some people needs to inspect the kDebug() output of their programs, besides, as you can see, you can just turn it off. > On Mon, May 27, 2013 at 09:25:10PM +0200, Sune Vuorela wrote: > > On Monday 27 May 2013 01:39:42 brian m. carlson wrote: > > > Please address this issue. > > > > Sorry that we haven't addressed this issue yet, but we are a bit swamped > > in 1300 bug reports and sometimes things fall past the cracks. If this > > is unsatisfactory, you are most welcome to join in or alternatively > > contact your software vendor and ask for a refund. Well, given that not everybody is allowed to be a member of your team and also not everybody is allowed to be a member of the debian project (which is probably one of the most closed free software projects around there, with an unneccesarily large and complicated process to become a member) you shouldn't complain about your lack of manpower, you just asked for it. Cheers.
Attachment:
signature.asc
Description: This is a digitally signed message part.