| Summary: | Kwin blur effect doesn't blur | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Davide Aversa <thek3nger> |
| Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | anarsoul |
| Priority: | NOR | ||
| Version: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
glxinfo output
CORRECT glxinfo output |
||
|
Description
Davide Aversa
2010-06-06 22:39:59 UTC
see bug #240956 please provide GPU/driver info (or just attach your glxinfo output) Created attachment 47764 [details]
glxinfo output
I saw linked bug. If I understad it SHOULD work and my glxinfo output seems to be ok.
a) you didn't attach glxinfo but some lspci b) judging from that you've sth. between gma915 and gma3100. these gpus only provide software shader implementations, so you might either suffer from a similar problem (gpu promotes feature but it doesn't actually work) or you don't have the required shader/buffer support at all. -> for a usefull answer, please attach glxinfo also try running "kwin --replace &" from a textshell (konsole) and watch the output when attempting to load the effect (In reply to comment #3) > b) judging from that you've sth. between gma915 and gma3100. these gpus only > provide software shader implementations, so you might either suffer from a > similar problem (gpu promotes feature but it doesn't actually work) or you > don't have the required shader/buffer support at all. Please, don't blame gen3 intel GPUs. Win7 and Compiz have blur working on these GPUs. That's KWin's fault that blur doesn't work on this hw. Btw, almost all Atom-based netbooks has gma950-like GPU, isn't it a good reason to add fallbacks in blur plugin for them? :) Created attachment 47785 [details]
CORRECT glxinfo output
Sorry. :| I uploaded the wrong file...
This is "kwin --replace" out:
kwin(1837) KWin::CompositingPrefs::detectDriverAndVersion: GL vendor is "Tungsten Graphics, Inc"
kwin(1837) KWin::CompositingPrefs::detectDriverAndVersion: GL renderer is "Mesa DRI Intel(R) G33 GEM 20100328 2010Q1 x86/MMX/SSE2"
kwin(1837) KWin::CompositingPrefs::detectDriverAndVersion: GL version is "1.4 Mesa 7.8.1"
kwin(1837) KWin::CompositingPrefs::detectDriverAndVersion: Detected driver "intel" , version "2010.Q.1"
kwin(1837): Invalid framebuffer status: 0
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Nessun file o directory
QFileSystemWatcher: failed to add paths: /home/thek3nger/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
WARNING: Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported! This is an application bug!
WARNING: Application calling GLX 1.3 function "glXQueryDrawable" when GLX 1.3 is not supported! This is an application bug!
WARNING: Application calling GLX 1.3 function "glXDestroyPixmap" when GLX 1.3 is not supported! This is an application bug
thanks for the info. @Vasily: i did not blame anything. several intel chips only provide SW shaders, i'm not sure whether there's GL_ARB_fragment_program or pbuffer/bufferobject support at all. the driver maybe broken. maybe kwin makes inappropriate usage of the buffers. therfore and to figure whether this is the same issue as #240956, i asked for detailed information. i did not blame anything. several intel chips only provide SW shaders*, i'm not sure whether there's GL_ARB_fragment_program or pbuffer/bufferobject support at all. therfore and to figure whether this is the same issue as #240956, i asked for detailed information. whether or not kwin blurring needs relaxed GL requirements or fallbacks is not subject of this report (but would be a whish as soon as there's more intel on what's the problem here) *** This bug has been marked as a duplicate of bug 240956 *** |