Bug 241113 - Blur effect does not work
Summary: Blur effect does not work
Status: RESOLVED DUPLICATE of bug 240956
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-08 17:09 UTC by Jonathan Thomas
Modified: 2010-06-08 17:16 UTC (History)
0 users

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 Jonathan Thomas 2010-06-08 17:09:56 UTC
Version:           unspecified (using Devel) 
OS:                Linux

The blur effect isn't working on my machine. This has happened since I first tried it in beta1, and still happens on beta2. When I try to enable it, KWin has this to say:

kwin(2069) KWin::EffectsHandlerImpl::loadEffect: Trying to load  "kwin4_effect_blur"
kwin(2069): Invalid framebuffer status:  0 
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted

...and I get no sweet blur effects. :(


Reproducible: Always




Info about my 64-bit machine:
kwin(2069) KWin::CompositingPrefs::detect: glx version is  1 . 2
kwin(2069) KWin::CompositingPrefs::detectDriverAndVersion: GL vendor is "Tungsten Graphics, Inc" 
kwin(2069) KWin::CompositingPrefs::detectDriverAndVersion: GL renderer is "Mesa DRI Mobile Intel® GM45 Express Chipset GEM 20100328 2010Q1 " 
kwin(2069) KWin::CompositingPrefs::detectDriverAndVersion: GL version is "1.4 (2.1 Mesa 7.8.1)" 
kwin(2069) KWin::CompositingPrefs::detectDriverAndVersion: Detected driver "intel" , version "2010.Q.1"
Comment 1 Thomas Lübking 2010-06-08 17:16:28 UTC

*** This bug has been marked as a duplicate of bug 240956 ***