Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Why desktop effects compositor gets reset to XRender?

  1. #1

    Default Why desktop effects compositor gets reset to XRender?

    Hello,

    I'm using OpenSuse 13.1, and once every two or three reboots, I log in KDE and notice that it has no desktop effects enabled. The fix is always the same, go to the desktop effects->advanced settings, find that the compositor has been reset to XRender, change it to use OpenGL3.1, click apply, confirm and everything is ok again. I'm using a NVidia GeForce 8400 GS with the proprietary NVidia drivers installed from the "nVidia Graphics Drivers" repository.

    Where/Why/How can I investigate this strange behavior?

    Thanks in advance.

  2. #2

    Default Re: Why desktop effects compositor gets reset to XRender?

    Well, kwin only switches to XRender when it detects problems with the OpenGL setup.
    E.g. when the nvidia driver is not working and the system falls back to fbdev.
    Strange though that you can switch back to OpenGL manually, this shouldn't be possible if that was the case.

    As for diagnosing, you could start with running "glxinfo | grep render" (you might need to install the package "Mesa-demo-x" first) when the problem occurs.
    Or maybe there would be clues in ~/.xsession-errors-:0 or /var/log/Xorg.0.log.

    And another thing:
    Try switching to OpenGL 2.0, does it happen then as well?
    AFAIK it is not recommended (by the kwin developers) to set this to anything else unless you want to experiment and/or have problems.
    You won't miss anything AFAIK, but the OpenGL 2.0 code is better tested.

  3. #3

    Default Re: Why desktop effects compositor gets reset to XRender?

    Quote Originally Posted by wolfi323 View Post
    Well, kwin only switches to XRender when it detects problems with the OpenGL setup.
    E.g. when the nvidia driver is not working and the system falls back to fbdev.
    Strange though that you can switch back to OpenGL manually, this shouldn't be possible if that was the case.

    As for diagnosing, you could start with running "glxinfo | grep render" (you might need to install the package "Mesa-demo-x" first) when the problem occurs.
    Or maybe there would be clues in ~/.xsession-errors-:0 or /var/log/Xorg.0.log.

    And another thing:
    Try switching to OpenGL 2.0, does it happen then as well?
    AFAIK it is not recommended (by the kwin developers) to set this to anything else unless you want to experiment and/or have problems.
    You won't miss anything AFAIK, but the OpenGL 2.0 code is better tested.
    Thanks, I'll try those suggestions next time it happens.

  4. #4

    Default Re: Why desktop effects compositor gets reset to XRender?

    Quote Originally Posted by wolfi323 View Post
    Well, kwin only switches to XRender when it detects problems with the OpenGL setup.
    E.g. when the nvidia driver is not working and the system falls back to fbdev.
    Strange though that you can switch back to OpenGL manually, this shouldn't be possible if that was the case.

    As for diagnosing, you could start with running "glxinfo | grep render" (you might need to install the package "Mesa-demo-x" first) when the problem occurs.
    Or maybe there would be clues in ~/.xsession-errors-:0 or /var/log/Xorg.0.log.

    And another thing:
    Try switching to OpenGL 2.0, does it happen then as well?
    AFAIK it is not recommended (by the kwin developers) to set this to anything else unless you want to experiment and/or have problems.
    You won't miss anything AFAIK, but the OpenGL 2.0 code is better tested.
    Happened again today. .xsession-errors is empty, and other than failure to ACPI something and a message saying "Failed to load /usr/lib64/xorg/modules/libglamoregl.so" , I don't see anything remarkable in the Xorg.0.log

    Setting to OpenGL2 to see if that prevents it from happening again. As you said, looks like it works the same as OpenGL3.

  5. #5
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,816

    Default AW: Why desktop effects compositor gets reset to XRender?

    Please post in Code-Tags:
    Code:
    zypper se -si nvidia kernel
    Code:
    uname -a
    Code:
    grep -E 'EE|II|WW' /var/log/Xorg.0.log

  6. #6

    Default Re: Why desktop effects compositor gets reset to XRender?

    Quote Originally Posted by barbolani View Post
    Happened again today. .xsession-errors is empty,
    Yes. Kwin's output goes to .xsession-errors-:0 as I said (for display :0 that is)
    And in particular kwin's output at startup would be interesting as it might contain a clue why it is switching to XRender.
    It should start with something like:
    Code:
    OpenGL vendor string:                   Intel Open Source Technology Center
    OpenGL renderer string:                 Mesa DRI Intel(R) 945G
    OpenGL version string:                  2.1 Mesa 9.2.3
    OpenGL shading language version string: 1.20
    Driver:                                 Intel
    GPU class:                              i915/i945
    OpenGL version:                         2.1
    GLSL version:                           1.20
    Mesa version:                           9.2.3
    X server version:                       1.14.3
    Linux kernel version:                   3.11.10
    Direct rendering:                       yes
    Requires strict binding:                yes
    GLSL shaders:                           limited
    Texture NPOT support:                   yes
    Virtual Machine:                        no
    So maybe open the file, search for "OpenGL" and have a look at the following lines.

    OTOH, it might be necessary to enable additional debug output (with "kdebugdialog") to get more information.

    and other than failure to ACPI something and a message saying "Failed to load /usr/lib64/xorg/modules/libglamoregl.so" , I don't see anything remarkable in the Xorg.0.log
    That's normal when the nvidia driver is installed.
    Did you run "glxinfo | grep render" before you turned on OpenGL again?
    Would have been interesting to see whether direct rendering was working or not, or whether the nvidia driver was not even used maybe. But as I wrote before you shouldn't be able to turn on OpenGL then at all.

    Somehow this sounds like some race condition at boot though.
    If it doesn't get better, please try to set NO_KMS_IN_INITRD="yes" and run "sudo /sbin/mkinitrd", this might help.
    Last edited by wolfi323; 29-Sep-2014 at 14:43.

  7. #7
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,585

    Default Re: Why desktop effects compositor gets reset to XRender?

    Do you have by any chance an Intel or ADM processor that also has a GPU on it???

    If so see if you can deactivate it in the BIOS . Could be confusing things.

  8. #8

    Default Re: AW: Why desktop effects compositor gets reset to XRender?

    Quote Originally Posted by Sauerland View Post
    Please post in Code-Tags:
    Code:
    zypper se -si nvidia kernel
    Code:
    Obteniendo los datos del repositorio...
    Leyendo los paquetes instalados...
    
    E | Nombre                        | Tipo     | Versión               | Arquitectura | Repositorio            
    --+-------------------------------+----------+-----------------------+--------------+------------------------
    i | kernel-default                | paquete  | 3.11.10-21.1          | x86_64       | openSUSE-13.1-Update   
    i | kernel-default                | paquete  | 3.11.10-17.2          | x86_64       | openSUSE-13.1-Update   
    i | kernel-default-devel          | paquete  | 3.11.10-21.1          | x86_64       | openSUSE-13.1-Update   
    i | kernel-default-devel          | paquete  | 3.11.10-17.2          | x86_64       | openSUSE-13.1-Update   
    i | kernel-desktop                | paquete  | 3.11.10-21.1          | x86_64       | openSUSE-13.1-Update   
    i | kernel-desktop                | paquete  | 3.11.10-17.2          | x86_64       | openSUSE-13.1-Update   
    i | kernel-desktop-devel          | paquete  | 3.11.10-21.1          | x86_64       | openSUSE-13.1-Update   
    i | kernel-desktop-devel          | paquete  | 3.11.10-17.2          | x86_64       | openSUSE-13.1-Update   
    i | kernel-devel                  | paquete  | 3.11.10-21.1          | noarch       | openSUSE-13.1-Update   
    i | kernel-devel                  | paquete  | 3.11.10-17.2          | noarch       | openSUSE-13.1-Update   
    i | kernel-firmware               | paquete  | 20130714git-2.21.1    | noarch       | openSUSE-13.1-Update   
    i | kernel-pae-devel              | paquete  | 3.11.10-21.1          | i686         | openSUSE-13.1-Update   
    i | kernel-pae-devel              | paquete  | 3.11.10-17.2          | i686         | openSUSE-13.1-Update   
    i | nvidia-computeG03             | paquete  | 340.32-31.1           | x86_64       | nVidia Graphics Drivers
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 340.32_k3.11.6_4-30.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 331.89_k3.11.6_4-28.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 331.79_k3.11.6_4-27.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 331.79_k3.11.6_4-26.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 331.67_k3.11.6_4-26.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 331.49_k3.11.6_4-29.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 340.32_k3.11.6_4-31.1 | x86_64       | nVidia Graphics Drivers
    i | nvidia-glG03                  | paquete  | 340.32-31.1           | x86_64       | nVidia Graphics Drivers
    i | nvidia-uvm-gfxG03-kmp-desktop | paquete  | 340.32_k3.11.6_4-30.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-uvm-gfxG03-kmp-desktop | paquete  | 331.89_k3.11.6_4-28.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-uvm-gfxG03-kmp-desktop | paquete  | 331.79_k3.11.6_4-27.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-uvm-gfxG03-kmp-desktop | paquete  | 340.32_k3.11.6_4-31.1 | x86_64       | nVidia Graphics Drivers
    i | x11-video-nvidiaG03           | paquete  | 340.32-31.1           | x86_64       | nVidia Graphics Drivers
    Quote Originally Posted by Sauerland View Post
    Code:
    uname -a
    Code:
    Linux barbolani 3.11.10-21-desktop #1 SMP PREEMPT Mon Jul 21 15:28:46 UTC 2014 (9a9565d) x86_64 x86_64 x86_64 GNU/Linux
    Quote Originally Posted by Sauerland View Post
    Code:
    grep -E 'EE|II|WW' /var/log/Xorg.0.log
    Code:
     14.771] Current Operating System: Linux barbolani 3.11.10-21-desktop #1 SMP PREEMPT Mon Jul 21 15:28:46 UTC 2014 (9a9565d) x86_64
            (++) from command line, (!!) notice, (II) informational,
            (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [    15.004] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
    [    15.004] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [    15.004] (WW) Disabling Keyboard0
    [    15.004] (WW) Disabling Mouse0
    [    15.004] (II) Loader magic: 0x803c20
    [    15.004] (II) Module ABI versions:
    [    15.005] (II) xfree86: Adding drm device (/dev/dri/card0)
    [    15.006] Initializing built-in extension MIT-SCREEN-SAVER
    [    15.006] (II) "glx" will be loaded by default.
    [    15.006] (II) LoadModule: "dri2"
    [    15.006] (II) Module "dri2" already built-in
    [    15.006] (II) LoadModule: "glamoregl"
    [    15.026] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
    [    16.473] (EE) Failed to load /usr/lib64/xorg/modules/libglamoregl.so: /usr/lib64/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context
    [    16.474] (II) UnloadModule: "glamoregl"
    [    16.474] (II) Unloading glamoregl
    [    16.474] (EE) Failed to load module "glamoregl" (loader failed, 7)
    [    16.474] (II) LoadModule: "glx"
    [    16.474] (II) Loading /usr/lib64/xorg/modules/updates/extensions/libglx.so
    [    18.039] (II) Module glx: vendor="NVIDIA Corporation"
    [    18.057] (II) NVIDIA GLX Module  340.32  Tue Aug  5 20:32:43 PDT 2014
    [    18.308] (II) LoadModule: "nvidia"
    [    18.308] (II) Loading /usr/lib64/xorg/modules/updates/drivers/nvidia_drv.so
    [    18.308] (II) Module nvidia: vendor="NVIDIA Corporation"
    [    18.308] (II) NVIDIA dlloader X Driver  340.32  Tue Aug  5 20:13:04 PDT 2014
    [    18.308] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [    18.308] (II) Loading sub module "fb"
    [    18.309] (II) LoadModule: "fb"
    [    18.309] (II) Loading /usr/lib64/xorg/modules/libfb.so
    [    18.309] (II) Module fb: vendor="X.Org Foundation"
    [    18.309] (WW) Unresolved symbol: fbGetGCPrivateKey
    [    18.309] (II) Loading sub module "wfb"
    [    18.309] (II) LoadModule: "wfb"
    [    18.341] (II) Loading /usr/lib64/xorg/modules/libwfb.so
    [    18.342] (II) Module wfb: vendor="X.Org Foundation"
    [    18.342] (II) Loading sub module "ramdac"
    [    18.342] (II) LoadModule: "ramdac"
    [    18.342] (II) Module "ramdac" already built-in
    [    19.034] (II) NVIDIA(0): Display (Philips 190V (CRT-1)) does not support NVIDIA 3D
    [    19.034] (II) NVIDIA(0):     Vision stereo.
    [    19.034] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
    [    19.035] (II) NVIDIA(0): NVIDIA GPU GeForce 8400 GS (G98) at PCI:1:0:0 (GPU-0)
    [    19.035] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [    19.040] (II) NVIDIA(0): Validated MetaModes:
    [    19.040] (II) NVIDIA(0):     "CRT-1:nvidia-auto-select"
    [    19.040] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
    [    19.075] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
    [    19.078] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [    19.078] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
    [    19.078] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
    [    19.078] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
    [    19.078] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
    [    19.078] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
    [    19.078] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
    [    19.078] (II) NVIDIA(0):     Config Options in the README.
    [    19.080] (II) NVIDIA(0): Setting mode "CRT-1:nvidia-auto-select"
    [    19.138] (II) Loading sub module "dri2"
    [    19.138] (II) LoadModule: "dri2"
    [    19.138] (II) Module "dri2" already built-in
    [    19.138] (II) NVIDIA(0): [DRI2] Setup complete
    [    19.138] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
    [    19.142] (II) Initializing extension GLX
    [    20.430] (II) config/udev: Adding input device Power Button (/dev/input/event4)
    [    20.430] (II) LoadModule: "evdev"
    [    20.560] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
    [    20.560] (II) Module evdev: vendor="X.Org Foundation"
    [    20.560] (II) Using input driver 'evdev' for 'Power Button'
    [    20.560] (II) evdev: Power Button: Configuring as keyboard
    [    20.560] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [    20.585] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [    20.585] (II) Using input driver 'evdev' for 'Power Button'
    [    20.585] (II) evdev: Power Button: Configuring as keyboard
    [    20.585] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [    20.585] (II) config/udev: Adding drm device (/dev/dri/card0)
    [    20.586] (II) config/udev: Adding input device HDA Intel Line Out (/dev/input/event7)
    [    20.586] (II) No input driver specified, ignoring this device.
    [    20.586] (II) This device may have been added with another device file.
    [    20.586] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event8)
    [    20.586] (II) No input driver specified, ignoring this device.
    [    20.586] (II) This device may have been added with another device file.
    [    20.586] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event9)
    [    20.586] (II) No input driver specified, ignoring this device.
    [    20.586] (II) This device may have been added with another device file.
    [    20.586] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4008 (/dev/input/event0)
    [    20.586] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:4008'
    [    20.587] (II) evdev: Logitech Unifying Device. Wireless PID:4008: Configuring as mouse
    [    20.587] (II) evdev: Logitech Unifying Device. Wireless PID:4008: Adding scrollwheel support
    [    20.587] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:4008" (type: MOUSE, id 8)
    [    20.587] (II) evdev: Logitech Unifying Device. Wireless PID:4008: initialized for relative axes.
    [    20.587] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4008 (/dev/input/mouse0)
    [    20.587] (II) No input driver specified, ignoring this device.
    [    20.587] (II) This device may have been added with another device file.
    [    20.588] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4003 (/dev/input/event1)
    [    20.588] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:4003'
    [    20.588] (II) evdev: Logitech Unifying Device. Wireless PID:4003: Forcing relative x/y axes to exist.
    [    20.588] (II) evdev: Logitech Unifying Device. Wireless PID:4003: Forcing absolute x/y axes to exist.
    [    20.588] (II) evdev: Logitech Unifying Device. Wireless PID:4003: Configuring as mouse
    [    20.588] (II) evdev: Logitech Unifying Device. Wireless PID:4003: Configuring as keyboard
    [    20.588] (II) evdev: Logitech Unifying Device. Wireless PID:4003: Adding scrollwheel support
    [    20.588] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:4003" (type: KEYBOARD, id 9)
    [    20.588] (II) evdev: Logitech Unifying Device. Wireless PID:4003: initialized for relative axes.
    [    20.588] (WW) evdev: Logitech Unifying Device. Wireless PID:4003: ignoring absolute axes.
    [    20.589] (II) config/udev: Adding input device GREAT PLANES InterLink Elite (/dev/input/event2)
    [    20.589] (II) No input driver specified, ignoring this device.
    [    20.589] (II) This device may have been added with another device file.
    [    20.589] (II) config/udev: Adding input device GREAT PLANES InterLink Elite (/dev/input/js0)
    [    20.589] (II) No input driver specified, ignoring this device.
    [    20.589] (II) This device may have been added with another device file.
    [    20.589] (II) config/udev: Adding input device UVC Camera (046d:0802) (/dev/input/event6)
    [    20.589] (II) Using input driver 'evdev' for 'UVC Camera (046d:0802)'
    [    20.589] (II) evdev: UVC Camera (046d:0802): Configuring as keyboard
    [    20.589] (II) XINPUT: Adding extended input device "UVC Camera (046d:0802)" (type: KEYBOARD, id 10)
    [    20.590] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
    [    20.590] (II) No input driver specified, ignoring this device.
    [    20.590] (II) This device may have been added with another device file.
    [    55.032] (II) NVIDIA(GPU-0): Display (Philips 190V (CRT-1)) does not support NVIDIA 3D
    [    55.032] (II) NVIDIA(GPU-0):     Vision stereo.
    [    56.395] (II) NVIDIA(GPU-0): Display (Philips 190V (CRT-1)) does not support NVIDIA 3D
    [    56.395] (II) NVIDIA(GPU-0):     Vision stereo.
    [    60.922] (II) NVIDIA(GPU-0): Display (Philips 190V (CRT-1)) does not support NVIDIA 3D
    [    60.922] (II) NVIDIA(GPU-0):     Vision stereo.

  9. #9

    Default Re: Why desktop effects compositor gets reset to XRender?

    Quote Originally Posted by gogalthorp View Post
    Do you have by any chance an Intel or ADM processor that also has a GPU on it???

    If so see if you can deactivate it in the BIOS . Could be confusing things.
    No on board GPU

  10. #10
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,816

    Default AW: Why desktop effects compositor gets reset to XRender?

    These Packages are obsolet, I would delete them:
    Code:
    i | kernel-default                | paquete  | 3.11.10-21.1          | x86_64       | openSUSE-13.1-Update   
    i | kernel-default                | paquete  | 3.11.10-17.2          | x86_64       | openSUSE-13.1-Update   
    i | kernel-default-devel          | paquete  | 3.11.10-21.1          | x86_64       | openSUSE-13.1-Update   
    i | kernel-default-devel          | paquete  | 3.11.10-17.2          | x86_64       | openSUSE-13.1-Update   
    i | kernel-pae-devel              | paquete  | 3.11.10-21.1          | i686         | openSUSE-13.1-Update   
    i | kernel-pae-devel              | paquete  | 3.11.10-17.2          | i686         | openSUSE-13.1-Update   
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 331.89_k3.11.6_4-28.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 331.79_k3.11.6_4-27.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 331.79_k3.11.6_4-26.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 331.67_k3.11.6_4-26.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-gfxG03-kmp-desktop     | paquete  | 331.49_k3.11.6_4-29.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-uvm-gfxG03-kmp-desktop | paquete  | 340.32_k3.11.6_4-30.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-uvm-gfxG03-kmp-desktop | paquete  | 331.89_k3.11.6_4-28.1 | x86_64       | (Paquetes del sistema) 
    i | nvidia-uvm-gfxG03-kmp-desktop | paquete  | 331.79_k3.11.6_4-27.1 | x86_64       | (Paquetes del sistema)

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •