Bug 197989 - composite failing after kernel upgrade to 2.6.30
Summary: composite failing after kernel upgrade to 2.6.30
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 4.2.4
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-26 20:18 UTC by Broch
Modified: 2009-06-27 05:40 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Broch 2009-06-26 20:18:17 UTC
Version:            (using KDE 4.2.4)
Compiler:          gcc version 4.4.0 20090526 (prerelease) 
OS:                Linux
Installed from:    Unspecified Linux

Hello,
I have small problem with kde 4.2.4.
Thank you for any help. Below is description of my system and the problem that I have.

My system description:
laptop HP Pavillion dv5000 (Intel dualcore T2500)
video card:
nvidia Go 7400
RAM 2GB
OS:
Arch Linux (current)
running kernels:
2.6.29.4
2.6.29.5
2.6.30-Arch
2.6.30-zen2
2.6.31-rc1-zen1
nvidia driver: 185.18.14 (patched to install on 2.6.31-rc1)
all kernels are installed with nvidia modules, so I don't need to reinstall nvidia driver when booting to another kernel.
or
nvidia driver: 180.53 or 180.60

KDE version: 4.2.4


problem:
after booting to any of the 2.6.30 I am loosing desktop effects (e.g. transparency, Expose)
-----------
when I boot to 2.6.29.x effects are restored, without any modification of kde settings.
-----------
Enable desktop effects is checked
Compositing type: OpenGL
OpenGL mode is set to Texture from Pixmap

Desktop effects work when booting to 2.6.29. Desktop effects do not work when booting to 2.6.30 series or 2.6.31-rc1

I tried different options settings in Desktop Settings configuration panel with no effect.
Moreover it seems that after upgrading to 2.6.30 more users have this problem.

I also have this exact problem when I had installed nvidia driver version 180.53 and 180.60 on all kernels (with exception of 2.6.31-rc1 as there are no patches for earlier drivers to be installed on 2.6.31-rc1)

When booting to 2.6.30 and trying to re-enable desktop efects: I am getting the following error:

    Quote:Failed to activate desktop effects using the given configuration options. Settings will be reverted to their previous values.
    Check your X configuration. You may also consider changing advanced options, especially changing the compositing type. 


this is the error appended to
~/.xsessions-error

    kwin(2891) KWin::CompositingPrefs::detectDriverAndVersion: GL vendor is "NVIDIA Corporation"
    kwin(2891) KWin::CompositingPrefs::detectDriverAndVersion: GL renderer is "GeForce Go 7400/PCI/SSE2"
    kwin(2891) KWin::CompositingPrefs::detectDriverAndVersion: GL version is "2.1.2 NVIDIA 185.18.14"
    kwin(2891) KWin::CompositingPrefs::detectDriverAndVersion: XGL: no
    kwin(2891) KWin::CompositingPrefs::detectDriverAndVersion: Detected driver "nvidia" , version "185.18.14"
    kwin(2891) KWin::CompositingPrefs::applyDriverSpecificOptions: nvidia >= 173.14.12, enabling compositing
    kwin(2891) KWin::x11ErrorHandler: kwin: X Error ( "error: GLXBadDrawable[GLX+2], request: X_GLXMakeContextCurrent[GLX+26], resource: 0x3a0a765" )
    kwin(2891) KWin::Extensions::init: Extensions: shape: 0x "11" composite: 0x "4" render: 0x "a" fixes: 0x "40"
    kwin(2891) KWin::Workspace::setupCompositing: OpenGL compositing
    kwin(2891) KWin::SceneOpenGL::initBufferConfigs: Drawable visual (depth 24 ): 0x "59"
    kwin(2891) KWin::SceneOpenGL::initBufferConfigs: Drawable visual (depth 32 ): 0x "80"
    kwin(2891) KWin::SceneOpenGL::initBuffer: Buffer visual (depth 24 ): 0x "57"
    kwin(2891): Compositing self-check failed, disabling compositing.
    kwin(2891): Failed to initialize compositing, compositing disabled
Comment 1 lucas 2009-06-27 04:38:16 UTC
Driver bug. Seems that KWin cannot create an OpenGL context (Meaning no way to display composited windows).
Comment 2 Broch 2009-06-27 05:40:30 UTC
is this mean that I should post this bug on nvidia forum?