Am 15.01.2015 um 00:13 schrieb Reindl Harald:
Am 14.01.2015 um 23:36 schrieb Alexander Ploumistos:
> On Thu, Jan 15, 2015 at 12:09 AM, Björn Persson wrote:
>
> Alexander Ploumistos wrote:
> >On the other hand, if every message that was not meant for the user
> >were suppressed, it would be very difficult to troubleshoot such a
> >program, should an actual bug come along, because you would need a
> >different build to get useful output in the console or a logging
> >service.
>
> Nah, it takes only a command line parameter to turn on debug
> logging. An
> environment variable could also be used. A different build isn't
> needed.
> It's no harder to make logging conditional at run time than it is to
> make it conditional at build time.
>
> The programs mentioned above do not have a debugging or verbosity flag,
> like e.g. "nmap -dd"
then they are broken and instead that the developer spits full my
terminal started a remote X11 appplication because i touch something in
that window he better would include such a switch defaulting to off
start "kate" (kde app) in a remote SSH session like below
"udisks2" is masked? so what - i know that
hence there is a entry in rsyslog to shut up
that crap appears everytime you successful open a file
and BTW messages like "Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)"
which appears for many years now prove that it is *completly useless*
and even the developers of the application itself don't care
otherwise such warning would go away over time
the same for broken desktop-files and what not reported again and again
in that context and nobody cares about - so why annoy the ordinary user
with that debug informations all day long?