Bug 189059 - Painter not active for plasma
Summary: Painter not active for plasma
Status: RESOLVED UPSTREAM
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-07 19:43 UTC by Luiz Angelo De Luca
Modified: 2009-04-25 22:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luiz Angelo De Luca 2009-04-07 19:43:31 UTC
Version:           desconhecido (using 4.2.2 (KDE 4.2.2) "release 111", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.19-3.2-default

Hello,

Since about one week ago, plasma seems to be strage. It start flawless and work for some time. After that, it begins to not paint some elements. Plasmoid, panel, evertythig else becomes unstable. Ex: when I pass the cursor over "tasks bar", which have just some icons, they get black. This is the error I got:

QPainter::end: Painter not active, aborted                                                   
QPainter::begin: Paint device returned engine == 0, type: 3                                  
QPainter::setCompositionMode: Painter not active    

Maybe this is related to the fact that I'm using unstable nouveau nvidia driver. However, I just noticed this problem with plasma and some konsole terminal colors. No other application (gtk, xterm) seems to be affected.
If I restart plasma, everything comes back to normal for some more time
Comment 1 Dario Andres 2009-04-25 21:58:39 UTC
What is your Qt version ?
Thanks
Comment 2 Dario Andres 2009-04-25 22:07:25 UTC
According to the Plasma developers both Plasma and Konsole have something in common: ARGV visuals. So this is probably a graphics driver issue.
Comment 3 Luiz Angelo De Luca 2009-04-25 22:48:29 UTC
OK, I also reported this in nouveau bugzilla.