On Tue, Jul 13, 2004 at 11:50:17PM +0200, Dominique Devriese wrote:
> Phil Edwards writes:
>
> > The patch only downgrades the severity of the diagnostic.
>
> That is not true. The debugging output is disabled in non-debug
> builds like debian's build, and the patch would thus make the output
> go away.
Okay, I'll take your word for it. (This result isn't obvious from just
the patch; it also depends on knowing debian's setup.)
> > I'd still like to know whst an end-user like me can do to avoid
> > /hundreds/ of these useless messages every time a KDE program is
> > run, especially if there's not going to be another KDE release after
> > the current 3.2.3, which doesn't have the patch.
>
> See adeodato's reply. You could also have edited kdebugrc yourself or
> have changed the theme description file from the hicolor-icon-theme
> stuff...
I've never heard of kdebugrc or kdebugdialog. Is it available via the
control panel or start/K menu?
More to the point: given the observed behavior (flood of messages), how
should a user know to run kdebugdialog? Perhaps this could be mentioned
at the start of the flood?
> > What makes sn icon directory group "not valid"?
>
> For reference, the cause of this bug is that the authors of
> hicolor-icon-theme have taken the liberty to invent group types that
> kde did not expect. See one of the three bugs that have been merged
> with this one, the one I first filed against hicolor-icon-theme, but
> which was later reassigned and merged here.
Cool. (I wish we could do full-text searches against the BTS. I had no
idea even what packages might be responsible for printing the error message,
much less the actual bug.)
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
