public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: KDE4 applications are spamming stderr to death
Date: Fri, 26 Feb 2010 22:16:20 +0100	[thread overview]
Message-ID: <201002262216.20505.volkerarmin@googlemail.com> (raw)
In-Reply-To: <hm9d96$2l1$1@dough.gmane.org>

On Freitag 26 Februar 2010, Nikos Chantziaras wrote:
> On 02/26/2010 10:32 PM, Volker Armin Hemmann wrote:
> > On Freitag 26 Februar 2010, Nikos Chantziaras wrote:
> >> Is it normal that every KDE (4.4.0) application is generating an awful
> >> lot of debug messages on stderr?  When I start one from the terminal (be
> >> it Dolphin, Konqueror or whatever) the output generated is pretty much
> >> 
> >> gigantic.  It's stuff like this:
> >>     QPainter::setPen: Painter not active
> >>     QPainter::font: Painter not active
> >>     QPainter::font: Painter not active
> >>     QPainter::setFont: Painter not active
> >>     QPainter::setPen: Painter not active
> >>     QPainter::font: Painter not active
> >>     konqueror(12426)/kio (Slave) KIO::Slave::createSlave: createSlave
> >>     "file" for KUrl("file:///usr/share/apps/kdeui/about/box-top-
> >>     middle.png")
> >>     konqueror(12426)/kio (KIOConnection)
> >>     KIO::ConnectionServer::listenForRemote: Listening on  "local:/tmp
> >>     /ksocket-realnc/konquerorb12426.slave-socket"
> >>     kio_file(12429)/kio (kioslave) KIO::SlaveBase::mimeType: "image/png"
> >>     kio_file(12431)/kio (kioslave) KIO::SlaveBase::mimeType: "image/png"
> >>     kio_file(12433)/kio (kioslave) KIO::SlaveBase::mimeType: "image/png"
> >>     kio_file(12435)/kio (kioslave) KIO::SlaveBase::mimeType: "image/png"
> >>     konqueror(12426)/kio (Slave) KIO::Slave::createSlave: createSlave
> >>     "file" for KUrl("file:///usr/share/apps/kdeui/about/box-middle-
> >>     left.png")
> >>     kio_file(12443) kdemain: Starting 12443
> >>     [...]
> >>     [etc, etc, ad infinitum]
> >> 
> >> Currently, after about 2 hours of uptime, my ~/.xsession-errors is about
> >> 12MB big and full with those debug messages.
> >> 
> >> The "debug" USE flag is globally disabled.  What's going on?  I doubt
> >> this is intended behavior.
> > 
> > the debug flag has nothing to do with this.
> > Why don't you open a nice bug at bugs.kde.org?
> 
> I wanted to make sure first that this isn't some sort of configuration
> problem on my end.  Can you confirm that this happens on your system too?

oh yes. It does. If you open a bug, post the link please.

ls -lhtr .xsession-errors
-rw------- 1 energyman users 345M 26. Feb 22:15 .xsession-errors




  reply	other threads:[~2010-02-26 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 20:25 [gentoo-user] KDE4 applications are spamming stderr to death Nikos Chantziaras
2010-02-26 20:32 ` Volker Armin Hemmann
2010-02-26 21:08   ` [gentoo-user] " Nikos Chantziaras
2010-02-26 21:16     ` Volker Armin Hemmann [this message]
2010-02-26 22:15       ` Nikos Chantziaras
2010-02-26 21:23     ` Alan McKinnon
2010-02-26 21:46       ` Kevin O'Gorman
2010-02-26 22:36         ` Dale
2010-02-27 23:55     ` KostyaSha
2010-02-28  0:11       ` Volker Armin Hemmann
2010-02-28 13:16         ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201002262216.20505.volkerarmin@googlemail.com \
    --to=volkerarmin@googlemail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox