[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: QPainter logs in stdout
From:       Mark Kretschmann <kretschmann () kde ! org>
Date:       2009-11-04 6:06:47
Message-ID: e93871060911032206w426fb5c8t88e87d9b5e33d78b () mail ! gmail ! com
[Download RAW message or body]

On Sat, Oct 17, 2009 at 8:34 AM, Jaime Torres <jtamate@gmail.com> wrote:
> Hi,
>
>  Has someone else seen these logs?
>
> QPainter::begin: Widget painting can only begin as a result of a paintEvent
> QPainter::translate: Painter not active
> QPainter::setClipRect: Painter not active
> QPainter::hasClipping: Painter not active
> QPainter::hasClipping: Painter not active
> QPainter::setPen: Painter not active
> QPainter::setBrush: Painter not active
> QPainter::drawRects: Painter not active
> QPainter::hasClipping: Painter not active
> QPainter::setPen: Painter not active
> QPainter::setBrush: Painter not active
> QPainter::drawRects: Painter not active
>
>  Has someone any idea where the problem could be?
>  Is there any way to know the stack in that QPainter logs to know where to
> search for the problem?

In fact this _could_ also have a completely different reason, that is
a bug in QGraphicsView. Alexis Menard recently fixed it for us (which
we are very thankful for, as it made Amarok crash). The patch should
arrive in the 4.6 Git repository from Nokia soon.

That said, it's perfectly possible that what happens here is simply
misuse of QPainter, as others said. But this Qt bug exposes the same
symptoms.

https://bugs.kde.org/show_bug.cgi?id=207382

-- 
Mark Kretschmann
Amarok Developer
www.kde.org - amarok.kde.org

[prev in list] [next in list] [prev in thread] [next in thread]