You are not logged in.

#1 Yesterday 14:29:34

pinx
Member
Registered: Yesterday
Posts: 10

[Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

Problem

The systemd journal fills with an endless stream of these messages (hundreds of these messages per minute):

kwin_wayland[1934]: eglInitialize failed
kwin_wayland[1934]: Error during eglInitialize  "EGL_NOT_INITIALIZED"

I can see the process wrapping Xwayland is running hot constantly:
/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_OrsNRi --xwayland

I have a hunch something goes wrong in xwayland, like it is trying to do something with egl where wayland and xwayland do not agree on the shared stuff? I am out of depth here.  According to the wiki: OpenGL hybrid graphics should not pose a problem with PRIME.

How do I proceed?


Hardware

Laptop with hybrid graphic. The discrete gpu is a NV197 (AD107), Ada Lovelace. (info)

inxi -G

Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: NVIDIA AD107GLM [RTX 2000 Ada Generation Laptop GPU]
    driver: nvidia v: 595.58.03
  Device-3: Syntek Integrated Camera driver: uvcvideo type: USB
  Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.10
    compositor: kwin_wayland driver: X: loaded: modesetting,nvidia dri: iris
    gpu: i915,nv_platform,nvidia,nvidia-nvswitch resolution: 1: 2560x2880~60Hz
    2: 2560x2880~60Hz 3: 2560x1600
  API: EGL v: 1.5 drivers: iris,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 26.0.4-arch1.1
    renderer: Mesa Intel Iris Xe Graphics (RPL-P)
  API: Vulkan v: 1.4.341 drivers: nvidia surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Software

eglinfo -B

Note that nvidia device cannot find a driver, egl for intel integrated graphics look ok:

GBM platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Wayland platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

X11 platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
libEGL warning: pci id for fd 3: 10de:28b8, driver (null)

pci id for fd 4: 10de:28b8, driver (null)
pci id for fd 5: 10de:28b8, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 3: 10de:28b8, driver (null)

pci id for fd 4: 10de:28b8, driver (null)
pci id for fd 5: 10de:28b8, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 3: 10de:28b8, driver (null)

eglinfo: eglInitialize failed

Device #2:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 22.1.2, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 22.1.2, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 22.1.2, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

prime-run eglinfo -B

Forcing egl-info on the nvidia card still throws an error

GBM platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Wayland platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

X11 platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Iris(R) Xe Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
libEGL warning: pci id for fd 3: 10de:28b8, driver (null)

pci id for fd 4: 10de:28b8, driver (null)
pci id for fd 5: 10de:28b8, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 3: 10de:28b8, driver (null)

pci id for fd 4: 10de:28b8, driver (null)
pci id for fd 5: 10de:28b8, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 3: 10de:28b8, driver (null)

eglinfo: eglInitialize failed

Device #2:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 22.1.2, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 26.0.4-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 22.1.2, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 22.1.2, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

env __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json eglinfo -B

What if I set the egl vendor library to nvidia? I see no device anymore, only Surfaceless, whatever that is.

GBM platform:
eglinfo: eglInitialize failed

Wayland platform:
eglinfo: eglInitialize failed

X11 platform:
eglinfo: eglInitialize failed

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 595.58.03
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 595.58.03
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 595.58.03
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

env __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json prime-run eglinfo -B

What if I set the egl vendor library to nvidia, run it on nvidia with prime-run? Again, I see no device anymore.

GBM platform:
eglinfo: eglInitialize failed

Wayland platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 595.58.03
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 595.58.03
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 595.58.03
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

X11 platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 595.58.03
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 595.58.03
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 595.58.03
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 595.58.03
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 595.58.03
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 595.58.03
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

pacman -Qs egl

local/egl-gbm 1.1.3-1
    The GBM EGL external platform library
local/egl-wayland 4:1.1.21-1
    EGLStream-based Wayland external platform
local/egl-wayland2 1.0.1-1
    EGLStream-based Wayland external platform (2)
local/egl-x11 1.0.5-1
    NVIDIA XLib and XCB EGL Platform Library
local/eglexternalplatform 1.2.1-1
    EGL External Platform interface
local/freeglut 3.8.0-1
    Free OpenGL Utility Toolkit
local/libglvnd 1.7.0-3
    The GL Vendor-Neutral Dispatch library
local/mesa-utils 9.0.0-7
    Essential Mesa utilities
local/qemu-ui-egl-headless 10.2.2-4
    QEMU EGL headless UI driver
local/wayland 1.24.0-1
    A computer display server protocol

nvidia packages

pacman -Qs nvidia

local/egl-gbm 1.1.3-1
    The GBM EGL external platform library
local/egl-wayland 4:1.1.21-1
    EGLStream-based Wayland external platform
local/egl-wayland2 1.0.1-1
    EGLStream-based Wayland external platform (2)
local/egl-x11 1.0.5-1
    NVIDIA XLib and XCB EGL Platform Library
local/libvdpau 1.5-4
    Nvidia VDPAU library
local/linux-firmware-nvidia 20260309-1
    Firmware files for Linux - Firmware for NVIDIA GPUs and SoCs
local/nvidia-open 595.58.03-3
    NVIDIA open kernel modules
local/nvidia-open-lts 1:595.58.03-4
    NVIDIA open kernel modules
local/nvidia-prime 1.0-5
    NVIDIA Prime Render Offload configuration and utilities
local/nvidia-utils 595.58.03-2
    NVIDIA drivers utilities
local/nvtop 3.3.2-1
    GPUs process monitoring for AMD, Intel and NVIDIA
# cat /sys/module/nvidia_drm/parameters/modeset
Y

# cat /sys/module/nvidia_drm/parameters/fbdev
Y

Last edited by pinx (Today 15:45:21)

Offline

#2 Yesterday 15:38:31

jasper_e
Member
From: Area 51
Registered: 2026-01-31
Posts: 8
Website

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

that error means either
a) vendor mismatch
b) missing gbm

also why do u have every single possible backend at once? that could be causing the prob

egl-wayland
egl-wayland2
egl-gbm

i will go with what the error says: eglInitialize failed. simply means that egl isnt initting on gbm

and forcing nvidia kinda works means glvnd is tweaking.

try removing a conflicting egl platform from egl-wayland and egl-wayland2, cuz you dont need both of them.

and make sure $GBM_BACKEND is set to nvidia-drm
and __GLX_VENDOR_LIBRARY_NAME is set to nvidia (on ur own risk, it works for me but doesnt work for some ppl, id suggest doing a deep dive)
and __NV_PRIME_RENDER_OFFLOAD is set to 1

try this

__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json eglinfo -B

if this fails that means egl integration is broken.

btw idk about nvidia-open but try switching to the proprietary nvidia and nvidia-utils

otherwise u can always force kwin to use gbm:

KWIN_DRM_USE_EGL_STREAMS=0

My contributions to Arch Linux community:
aur.archlinux.org smile
My contributions to the Linux community:
nexttechcreations.pages.dev

Offline

#3 Yesterday 17:17:39

pinx
Member
Registered: Yesterday
Posts: 10

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

jasper_e wrote:

that error means either
a) vendor mismatch
b) missing gbm

also why do u have every single possible backend at once? that could be causing the prob

egl-wayland
egl-wayland2
egl-gbm


i will go with what the error says: eglInitialize failed. simply means that egl isnt initting on gbm

and forcing nvidia kinda works means glvnd is tweaking.

try removing a conflicting egl platform from egl-wayland and egl-wayland2, cuz you dont need both of them.

nvidia-utils seems to require all of the egl-* dependencies, and it is itself required by nvidia-open, so I did not dare to delete anything from this list.

$ pacman -Qi nvidia-utils 
Name            : nvidia-utils
Version         : 595.58.03-2
Provides        : vulkan-driver  opengl-driver  nvidia-libgl
Depends On      : libglvnd  egl-wayland  egl-wayland2  egl-gbm  egl-x11
Optional Deps   : nvidia-settings: configuration tool
                  xorg-server: Xorg support [installed]
                  xorg-server-devel: nvidia-xconfig
                  opencl-nvidia: OpenCL support
Required By     : libglvnd  nvidia-open  nvidia-open-lts  nvidia-prime
Optional For    : ffmpeg  ffmpeg4.4  libvdpau  sdl3  vulkan-icd-loader
Conflicts With  : nvidia-libgl
Replaces        : nvidia-libgl

and make sure $GBM_BACKEND is set to nvidia-drm
and __GLX_VENDOR_LIBRARY_NAME is set to nvidia (on ur own risk, it works for me but doesnt work for some ppl, id suggest doing a deep dive)
and __NV_PRIME_RENDER_OFFLOAD is set to 1

Putting __GLX_VENDOR_LIBRARY_NAME=nvidia inside  /etc/environment makes the login-screen black (there is still a mouse pointer though).
Having GBM_BACKEND=nvidia-drm in  /etc/environment does not change anything apparently. Did you mean to alter prime-run?

try this

__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json eglinfo -B

if this fails that means egl integration is broken.

See above, I executed that command. I even adjusted prime-run to point __EGL_VENDOR_LIBRARY_FILENAMES to nvidia, but that did not help.

btw idk about nvidia-open but try switching to the proprietary nvidia and nvidia-utils
otherwise u can always force kwin to use gbm:

KWIN_DRM_USE_EGL_STREAMS=0

I will try KWIN_DRM_USE_EGL_STREAMS and see if that helps.

Offline

#4 Yesterday 17:21:58

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 74,642

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

Offline

#5 Yesterday 17:38:19

pinx
Member
Registered: Yesterday
Posts: 10

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

lspci -k | grep -A3 -E "VGA|3D"
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04)
        Subsystem: Lenovo Device 2316
        Kernel driver in use: i915
        Kernel modules: i915, xe
--
01:00.0 VGA compatible controller: NVIDIA Corporation AD107GLM [RTX 2000 Ada Generation Laptop GPU] (rev a1)
        Subsystem: Lenovo Device 2316
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia

ls -l /dev/dri/by-path
lrwxrwxrwx - root 19 apr 19:24  pci-0000:00:02.0-card -> ../card2
lrwxrwxrwx - root 19 apr 19:23  pci-0000:00:02.0-platform-simple-framebuffer.0-card -> ../card0
lrwxrwxrwx - root 19 apr 19:24  pci-0000:00:02.0-render -> ../renderD129
lrwxrwxrwx - root 19 apr 19:24  pci-0000:01:00.0-card -> ../card1
lrwxrwxrwx - root 19 apr 19:24  pci-0000:01:00.0-render -> ../renderD128

If I interpret that correctly, here card2=intel igpu and card1=nvidia-dgpu. I have also card0, renderD129, renderD128 which are quite unclear to me.

I could do the opposite from what gen2arch did by setting

Environment=KWIN_DRM_DEVICES=/dev/dri/card2:/dev/dri/card1

Offline

#6 Yesterday 17:39:39

pinx
Member
Registered: Yesterday
Posts: 10

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

pinx wrote:
jasper_e wrote:

that error means either

btw idk about nvidia-open but try switching to the proprietary nvidia and nvidia-utils
otherwise u can always force kwin to use gbm:

KWIN_DRM_USE_EGL_STREAMS=0

I will try KWIN_DRM_USE_EGL_STREAMS and see if that helps.

That did not help unfortunately.

Offline

#7 Yesterday 18:19:34

pinx
Member
Registered: Yesterday
Posts: 10

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

Strangely, when I hardcode nvdia first, intel second I get rid of that massive hammering on journald:

# ~/.config/systemd/user/plasma-kwin_wayland.service.d/override.conf

Environment=KWIN_DRM_DEVICES=/dev/dri/card1:/dev/dri/card2

I had expect that card1 would have had higher priority than card2 automatically. Maybe it had otherwise selected card0 before card1? But still, I don't know what card0 is.

Now I only get just these warnings (but not as a flood), and there is a general slowness, but at least it doesn't kill my ssd anymore.

konsole[11588]: libEGL warning: failed to get driver name for fd -1
konsole[11588]: libEGL warning: MESA-LOADER: failed to retrieve device information
konsole[11588]: libEGL warning: failed to get driver name for fd -1

Last edited by pinx (Yesterday 18:20:04)

Offline

#8 Yesterday 19:28:26

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 74,642

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

The main point about the other thread is whether the journal is actually spilled w/ those errors rather than the ones you posted.
"QT_LOGGING_RULES=kwin_scene_opengl=false" would disable the warnings.

Then instead of messing around w/ the card order try to add "initcall_blacklist=simpledrm_platform_driver_init" XOR "initcall_blacklist=sysfb_init" to the https://wiki.archlinux.org/title/Kernel_parameters to block the simpledrm device
But because of the GL situation

env __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json prime-run eglinfo -B

actually looks fine, what's the output of

printenv

?

Offline

#9 Yesterday 20:17:53

pinx
Member
Registered: Yesterday
Posts: 10

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

Ah, yeah but my instinct was to deal with the issue instead of ignoring the errors.

With KWIN_DRM_DEVICES=/dev/dri/card1:/dev/dri/card2 as current setting, `printenv` gives:

SHELL=/bin/bash
SESSION_MANAGER=local/pc-dat:@/tmp/.ICE-unix/9766,unix/pc-dat:/tmp/.ICE-unix/9766
WINDOWID=94883561460160
COLORTERM=truecolor
XDG_CONFIG_DIRS=/home/ego/.config/kdedefaults:/etc/xdg
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session7
XDG_MENU_PREFIX=plasma-
__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json
ICEAUTHORITY=/run/user/1000/iceauth_UrhPma
LANGUAGE=
LC_ADDRESS=nl_NL.UTF-8
POWERSHELL_TELEMETRY_OPTOUT=1
LC_NAME=nl_NL.UTF-8
DOTNET_CLI_TELEMETRY_OPTOUT=1
SHELL_SESSION_ID=e21876c6a85e490ea73c8c5eb215cdd0
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
DESKTOP_SESSION=plasma
LC_MONETARY=nl_NL.UTF-8
GTK_RC_FILES=/etc/gtk/gtkrc:/home/ego/.gtkrc:/home/ego/.config/gtkrc
EDITOR=nano
XDG_SEAT=seat0
PWD=/var
XDG_SESSION_DESKTOP=KDE
LOGNAME=ego
XDG_SESSION_TYPE=wayland
SYSTEMD_EXEC_PID=9871
XAUTHORITY=/run/user/1000/xauth_ZEeqBC
MOTD_SHOWN=pam
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/ego/.gtkrc-2.0:/home/ego/.config/gtkrc-2.0
HOME=/home/ego
LC_PAPER=nl_NL.UTF-8
LANG=en_US.UTF-8
_JAVA_AWT_WM_NONREPARENTING=1
XDG_CURRENT_DESKTOP=KDE
KONSOLE_DBUS_SERVICE=:1.59
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service/memory.pressure
WAYLAND_DISPLAY=wayland-0
KONSOLE_DBUS_SESSION=/Sessions/1
PROFILEHOME=
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
INVOCATION_ID=9507cf77a44a4d14bb7aaf93094d0627
KONSOLE_VERSION=260400
MANAGERPID=9544
KDE_SESSION_UID=1000
XKB_DEFAULT_LAYOUT=us
XDG_SESSION_CLASS=user
TERM=konsole-direct
LC_IDENTIFICATION=nl_NL.UTF-8
KONSOLE_DBUS_ACTIVATION_COOKIE=Mj6Y63UOFhLQpm6YdDCez+OY/lKipKJjXMxeWGPqPA8=
USER=ego
COLORFGBG=15;0
QT_WAYLAND_RECONNECT=1
KDE_SESSION_VERSION=6
PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket
DISPLAY=:1
SHLVL=1
LC_TELEPHONE=nl_NL.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_MEASUREMENT=nl_NL.UTF-8
XDG_VTNR=1
XDG_SESSION_ID=10
MANAGERPIDFDID=9545
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
LC_TIME=nl_NL.UTF-8
KDECONNECT_DISABLE_UDP_BROADCAST=1
XKB_DEFAULT_VARIANT=intl
JOURNAL_STREAM=9:131582
XDG_DATA_DIRS=/home/ego/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
KDE_FULL_SESSION=true
BROWSER=firefox
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/ego/.local/bin
GBM_BACKEND=nvidia-drm
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
KDE_APPLICATIONS_AS_SCOPE=1
MAIL=/var/spool/mail/ego
FLATPAK_TTY_PROGRESS=1
LC_NUMERIC=nl_NL.UTF-8
OLDPWD=/home/ego/docs/dev/linux/archpkg
KONSOLE_DBUS_WINDOW=/Windows/1
_=/usr/bin/printenv

Offline

#10 Yesterday 20:28:42

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 74,642

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

Ah, yeah but my instinct was to deal with the issue instead of ignoring the errors.

Again, it is very important what the bulk of the error messages actually are - there's currently no proper solution for the other situation.

However

__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json

Remove that.

Offline

#11 Today 12:19:18

pinx
Member
Registered: Yesterday
Posts: 10

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

seth wrote:

The main point about the other thread is whether the journal is actually spilled w/ those errors rather than the ones you posted.
"QT_LOGGING_RULES=kwin_scene_opengl=false" would disable the warnings.

Ah, at first I thought my config was bad, but your solution is to suppress the errors till upstream fixes their bug(s).

Then instead of messing around w/ the card order try to add "initcall_blacklist=simpledrm_platform_driver_init" XOR "initcall_blacklist=sysfb_init" to the https://wiki.archlinux.org/title/Kernel_parameters to block the simpledrm device

I have tried `initcall_blacklist=simpledrm_platform_driver_init` but that did not make a difference.

Offline

#12 Today 12:26:59

pinx
Member
Registered: Yesterday
Posts: 10

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

seth wrote:

Ah, yeah but my instinct was to deal with the issue instead of ignoring the errors.

Again, it is very important what the bulk of the error messages actually are - there's currently no proper solution for the other situation.

Yes, I now understand this is not my fault but a problem stemming from upstream. I have the messages suppressed, for now this is solved I guess.

seth wrote:
__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json

Remove that.

Oh good catch, I thought this was a default setting, but this is a left over from the time when I tried to make sure the system wouldn't bind nvidia, so I could use it for pass-through in virtualization scenario's. I removed it, it did not have any effect, but at least I am back to default config.

Last edited by pinx (Today 12:28:47)

Offline

#13 Today 13:06:54

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 74,642

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

Remove the QT_LOGGING_RULES again; after also removing the bogus __EGL_VENDOR_LIBRARY_FILENAMES, do you still get
a) "an endless stream of […] messages"?
b) "Error during eglInitialize  "EGL_NOT_INITIALIZED"" or eglinfo errors specifically?

Offline

#14 Today 15:05:34

pinx
Member
Registered: Yesterday
Posts: 10

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

seth wrote:

Remove the QT_LOGGING_RULES again; after also removing the bogus __EGL_VENDOR_LIBRARY_FILENAMES, do you still get
a) "an endless stream of […] messages"?
b) "Error during eglInitialize  "EGL_NOT_INITIALIZED"" or eglinfo errors specifically?

I did that. (In the meantime,  I now have changed i915 to https://github.com/strongtz/i915-sriov-dkms/)

RE a) I do get an endless stream of messages, but
RE b) they changed to this form

kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.

...ad infinitum

To add some more info (0x0.st does not process new uploads for the moment), I include some portions of current boot.


apr 20 15:55:49 pc-peen kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
apr 20 15:55:49 pc-peen kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
apr 20 15:55:49 pc-peen kernel: fbcon: Deferring console take-over
apr 20 15:55:49 pc-peen kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device


apr 20 15:55:49 pc-peen systemd[1]: /usr/lib/systemd/system/systemd-udevd.service:56: System call bpf cannot be resolved as libseccomp is not available, ignoring: Operation not supported
apr 20 15:55:49 pc-peen systemd[1]: /usr/lib/systemd/system/systemd-udevd.service.d/50-rc_keymap.conf:3: System call bpf cannot be resolved as libseccomp is not available, ignoring: Operation not supported

apr 20 15:55:49 pc-peen kernel: nvidia: loading out-of-tree module taints kernel.
apr 20 15:55:49 pc-peen kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel


apr 20 15:55:49 pc-peen kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 239
apr 20 15:55:49 pc-peen kernel: 
apr 20 15:55:49 pc-peen kernel: nvidia 0000:01:00.0: enabling device (0006 -> 0007)
apr 20 15:55:49 pc-peen kernel: nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
apr 20 15:55:49 pc-peen systemd-modules-load[300]: Inserted module 'nvidia_uvm'

apr 20 15:55:50 pc-peen kernel: fbcon: i915drmfb (fb0) is primary device
apr 20 15:55:51 pc-peen kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
apr 20 15:55:51 pc-peen kernel: i915 0000:00:02.0: 7 VFs could be associated with this PF
apr 20 15:55:52 pc-peen kernel: Module xe is blacklisted
apr 20 15:55:52 pc-peen kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
apr 20 15:55:52 pc-peen kernel: nvidia 0000:01:00.0: [drm] fb1: nvidia-drmdrmfb frame buffer device

apr 20 15:56:05 pc-peen systemd-modules-load[1214]: Using 5 probe threads
apr 20 15:56:05 pc-peen systemd-modules-load[1214]: libkmod: ERROR: kmod_config_parse: /etc/modprobe.d/truescale.conf line 2: ignoring bad line starting with '`'
apr 20 15:56:05 pc-peen systemd-modules-load[1214]: libkmod: ERROR: kmod_config_parse: /etc/modprobe.d/truescale.conf line 2: ignoring bad line starting with '`'
apr 20 15:56:05 pc-peen systemd-modules-load[1214]: libkmod: ERROR: kmod_config_parse: /etc/modprobe.d/truescale.conf line 2: ignoring bad line starting with '`'
apr 20 15:56:05 pc-peen systemd-modules-load[1214]: libkmod: ERROR: kmod_config_parse: /etc/modprobe.d/truescale.conf line 2: ignoring bad line starting with '`'
apr 20 15:56:05 pc-peen systemd-modules-load[1214]: libkmod: ERROR: kmod_config_parse: /etc/modprobe.d/truescale.conf line 2: ignoring bad line starting with '`'

apr 20 15:56:06 pc-peen systemd-udevd[1263]: libkmod: ERROR: kmod_config_parse: /etc/modprobe.d/truescale.conf line 2: ignoring bad line starting with '`'
apr 20 15:56:06 pc-peen systemd-udevd[1263]: Using default interface naming scheme 'v260'.

apr 20 15:56:06 pc-peen kernel: Serial bus multi instantiate pseudo device driver CSC3551:00: Instantiated 2 I2C devices.
apr 20 15:56:06 pc-peen kernel: resource: resource sanity check: requesting [mem 0x00000000fedc0000-0x00000000fedcffff], which spans more than pnp 00:05 [mem 0xfedc0000-0xfedc7fff]
apr 20 15:56:06 pc-peen kernel: caller igen6_probe+0x155/0x81c [igen6_edac] mapping multiple BARs

apr 20 15:56:06 pc-peen kernel: mc: Linux media interface: v0.10
apr 20 15:56:06 pc-peen kernel: Module xe is blacklisted

apr 20 15:56:07 pc-peen kernel: faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
apr 20 15:56:07 pc-peen kernel: cfg80211: failed to load regulatory.db

apr 20 15:56:28 pc-dat systemd[1848]: Starting D-Bus User Message Bus...
apr 20 15:56:28 pc-dat dbus-broker-launch[1960]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
apr 20 15:56:28 pc-dat dbus-broker-launch[1960]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
apr 20 15:56:28 pc-dat dbus-broker-launch[1960]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
apr 20 15:56:28 pc-dat dbus-broker-launch[1960]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
apr 20 15:56:28 pc-dat dbus-broker-launch[1960]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
apr 20 15:56:28 pc-dat systemd[1848]: Started D-Bus User Message Bus.
apr 20 15:56:28 pc-dat dbus-broker-launch[1960]: Ready
apr 20 15:56:28 pc-dat systemd[1848]: Reload requested from client PID 1933 ('startplasma-way')...
apr 20 15:56:28 pc-dat systemd[1848]: Reloading...
apr 20 15:56:28 pc-dat systemd[1848]: /home/ego/.config/systemd/user/shutdown-pc.timer.d/override.conf:12: Unknown key 'WantedBy' in section [Timer], ignoring.
apr 20 15:56:28 pc-dat systemd[1848]: Reloading finished in 130 ms.

apr 20 15:56:28 pc-dat systemd[1848]: Starting KDE Wayland Compositor...
apr 20 15:56:28 pc-dat systemd[1848]: Starting User folders update...
apr 20 15:56:28 pc-dat systemd[1848]: Starting Baloo File Indexer Daemon...
apr 20 15:56:28 pc-dat systemd[1848]: Finished User folders update.
apr 20 15:56:28 pc-dat systemd[1848]: Reached target Session services which should run early before the graphical session is brought up.
apr 20 15:56:28 pc-dat systemd[1848]: Started KDE Wayland Compositor.
apr 20 15:56:28 pc-dat systemd[1848]: Starting KDE Config Module Initialization...
apr 20 15:56:28 pc-dat systemd[1848]: Starting Splash screen shown during boot...
apr 20 15:56:28 pc-dat systemd[1848]: Started KDE Global Shortcuts Server.
apr 20 15:56:28 pc-dat systemd[1848]: Started Baloo File Indexer Daemon.
apr 20 15:56:28 pc-dat systemd[1848]: Starting Portal service...
apr 20 15:56:28 pc-dat systemd[1]: Starting Disk Manager...
apr 20 15:56:28 pc-dat systemd[1848]: Starting sandboxed app permission store...
apr 20 15:56:28 pc-dat systemd[1848]: Started sandboxed app permission store.
apr 20 15:56:28 pc-dat kernel: nvme nvme0: using unchecked data buffer
apr 20 15:56:28 pc-dat systemd[1848]: Starting flatpak document portal service...
apr 20 15:56:28 pc-dat systemd[1848]: Started flatpak document portal service.
apr 20 15:56:28 pc-dat /usr/lib/xdg-desktop-portal[1990]: Choosing gtk.portal for org.freedesktop.impl.portal.Lockdown as a last-resort fallback
apr 20 15:56:28 pc-dat kwin_wayland[1982]: No backend specified, automatically choosing drm
apr 20 15:56:28 pc-dat systemd[1]: Started Disk Manager.
apr 20 15:56:29 pc-dat opensnitchd[1570]: Timed out while sending packet to queue channel 2936898933
apr 20 15:56:29 pc-dat kwin_wayland[1982]: XKB: Multiple definitions of group 1 name in map 'intl-unicode'; Using 'English (US, intl., AltGr Unicode combining)', ignoring 'English (US, intl., with dead keys)'
apr 20 15:56:29 pc-dat systemd[1848]: Starting KDE Night Time Service...
apr 20 15:56:29 pc-dat systemd[1848]: Started PipeWire Multimedia Service.
apr 20 15:56:29 pc-dat systemd[1848]: Started Multimedia Service Session Manager.
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat systemd[1848]: Started KDE Night Time Service.
apr 20 15:56:29 pc-dat systemd[1]: Starting RealtimeKit Scheduling Policy Service...
apr 20 15:56:29 pc-dat systemd[1]: Started RealtimeKit Scheduling Policy Service.
apr 20 15:56:29 pc-dat rtkit-daemon[2052]: Handling system-suspend using logind.
apr 20 15:56:29 pc-dat rtkit-daemon[2052]: Successfully made thread 2046 of process 2046 owned by '1000' high priority at nice level -11.
apr 20 15:56:29 pc-dat rtkit-daemon[2052]: Successfully made thread 2045 of process 2045 owned by '1000' high priority at nice level -11.
apr 20 15:56:29 pc-dat rtkit-daemon[2052]: Successfully made thread 2058 of process 2046 owned by '1000' RT at priority 20.
apr 20 15:56:29 pc-dat rtkit-daemon[2052]: Successfully made thread 2051 of process 2045 owned by '1000' RT at priority 20.
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat kernel: Bluetooth: RFCOMM TTY layer initialized
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/ldac
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat kernel: Bluetooth: RFCOMM socket layer initialized
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/aptx_hd
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2098]: The XKEYBOARD keymap compiler (xkbcomp) reports:
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2098]: > Warning:          Multiple symbols for level 1/group 1 on key <FK23>
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2098]: >                   Using F23, ignoring XF86TouchpadOff
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2098]: > Warning:          Symbol map for key <FK23> redefined
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2098]: >                   Using last definition for conflicting fields
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2098]: > Warning:          Symbol map for key <FK24> redefined
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2098]: >                   Using last definition for conflicting fields
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2098]: Errors from xkbcomp are not fatal to the X server
apr 20 15:56:29 pc-dat kernel: Bluetooth: RFCOMM ver 1.11
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_hd
apr 20 15:56:29 pc-dat wireplumber[2046]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2103]: The XKEYBOARD keymap compiler (xkbcomp) reports:
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2103]: > Warning:          Unsupported maximum keycode 709, clipping.
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2103]: >                   X11 cannot support keycodes above 255.
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2103]: > Warning:          Virtual modifier Hyper multiply defined
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2103]: >                   Using 0, ignoring 0
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2103]: > Warning:          Virtual modifier ScrollLock multiply defined
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2103]: >                   Using 0, ignoring 0
apr 20 15:56:29 pc-dat kwin_wayland_wrapper[2103]: Errors from xkbcomp are not fatal to the X server
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/aptx
apr 20 15:56:29 pc-dat wireplumber[2046]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/aac
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aac
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/opus_g
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/opus_g
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_1
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_0
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
apr 20 15:56:29 pc-dat systemd[1848]: Starting Accessibility services bus...
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/faststream
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/faststream_duplex
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/opus_05
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/opus_05
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/opus_05_duplex
apr 20 15:56:29 pc-dat systemd[1848]: Started Accessibility services bus.
apr 20 15:56:29 pc-dat bluetoothd[1494]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/opus_05_duplex
apr 20 15:56:29 pc-dat dbus-broker-launch[2138]: Ready
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:29 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:29 pc-dat pam_kwallet_init[2167]: 2026/04/20 15:56:29 socat[2167] W address is opened in read-write mode but only supports read-only


apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: Library initialization complete.
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: Watching for DPMS state changes unimplemented
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2263] (ddci_init) Done.  Returning 0
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2263] Starting ddca_start_watch_displays()
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2263] Watching for DPMS state changes unimplemented
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2263] Watching for display connection changes, resolved watch mode = Watch_Mode_Udev, poll loop interval = 500 millisec
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2263]                                          extra_stabilization_millisec: 0,  stabilization_poll_millisec: 100
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2263] libddcutil recheck thread 0x55646741d1a0 started
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2263] libddcutil watch thread 0x556467405170 started
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2263] Done     ddca_start_watch_displays returning OK - OK(0): success
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2263] (ddca_get_display_refs) Returned DDCA_Display_Ref list:
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2263] (ddca_get_display_refs)    DDCA_Display_Ref Display_Ref[2:bus /dev/i2c-14 @0x556467408620]
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2263] (ddca_get_display_refs)    DDCA_Display_Ref Display_Ref[3:bus /dev/i2c-15 @0x556467408e20]
apr 20 15:56:31 pc-dat org_kde_powerdevil[2263]: [  2452] (dw_recheck_displays_func) Recheck interval: Sleeping for 200 milliseconds
apr 20 15:56:31 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:31 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:31 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:31 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:31 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:31 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:31 pc-dat systemd[1848]: Created slice Slice /app/dbus-:1.2-org.kde.kdeconnect.
apr 20 15:56:31 pc-dat systemd[1848]: Started dbus-:1.2-org.kde.kdeconnect@0.service.
apr 20 15:56:31 pc-dat kernel: wlan0: AP 74:ea:3a:d1:4b:52 changed bandwidth in beacon, new used config is 2417.000 MHz, width 1 (2417.000/0 MHz)
apr 20 15:56:31 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:31 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:31 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:31 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:31 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:31 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:31 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:31 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:31 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:31 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:31 pc-dat NetworkManager[1492]: <info>  (redacted)
apr 20 15:56:31 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:31 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat opensnitchd[1570]: Timed out while sending packet to queue channel 2936898933
apr 20 15:56:32 pc-dat opensnitchd[1570]: Timed out while sending packet to queue channel 2936898933

apr 20 15:56:32 pc-dat systemd[1848]: Starting Xdg Desktop Portal For KDE...
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat systemd[1848]: Started Xdg Desktop Portal For KDE.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat opensnitch-ui[2525]: WARNING:root:qt_material must be imported after PySide or PyQt!
apr 20 15:56:32 pc-dat systemd[1848]: Started Portal service.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/1982/root")
apr 20 15:56:32 pc-dat ksmserver[2152]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.ksmserver'")
apr 20 15:56:32 pc-dat gmenudbusmenuproxy[2260]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.gmenudbusmenuproxy'")
apr 20 15:56:32 pc-dat xembedsniproxy[2264]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.xembedsniproxy'")
apr 20 15:56:32 pc-dat polkit-kde-authentication-agent-1[2262]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/2262/root")
apr 20 15:56:32 pc-dat kactivitymanagerd[2259]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.ActivityManager'")
apr 20 15:56:32 pc-dat kded6[2156]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.kded6'")
apr 20 15:56:32 pc-dat kwalletd6[2361]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.kwalletd'")
apr 20 15:56:32 pc-dat org_kde_powerdevil[2263]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.org_kde_powerdevil'")
apr 20 15:56:32 pc-dat xembedsniproxy[2264]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.xembedsniproxy'")
apr 20 15:56:32 pc-dat kdeconnectd[2459]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
apr 20 15:56:32 pc-dat ksmserver[2152]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.ksmserver'")
apr 20 15:56:32 pc-dat kded6[2156]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.kded6'")
apr 20 15:56:32 pc-dat kwalletd6[2361]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.kwalletd'")
apr 20 15:56:32 pc-dat polkit-kde-authentication-agent-1[2262]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/2262/root")
apr 20 15:56:32 pc-dat gmenudbusmenuproxy[2260]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.gmenudbusmenuproxy'")
apr 20 15:56:32 pc-dat kactivitymanagerd[2259]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.ActivityManager'")
apr 20 15:56:32 pc-dat ksecretd[1932]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
apr 20 15:56:32 pc-dat xdg-desktop-portal-kde[2637]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
apr 20 15:56:32 pc-dat org_kde_powerdevil[2263]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/1982/root")
apr 20 15:56:32 pc-dat kaccess[2261]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat plasmashell[2233]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won't be used.
apr 20 15:56:32 pc-dat plasmashell[2233]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat systemd[1848]: Started app-org.kde.konsole-2635.scope.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat konsole[2635]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:32 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:32 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:33 pc-dat opensnitchd[1570]: found /usr/lib/libc.so.6
apr 20 15:56:33 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:33 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
apr 20 15:56:33 pc-dat kwin_wayland[1982]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
apr 20 15:56:33 pc-dat kwin_wayland[1982]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"

(etc)

Some on the nvidia forums have the same problem (source https://forums.developer.nvidia.com/t/b … t/363108/2)

Arch nvidia-open-dkms is now on 595.58.03 and believe it or not, it’s got even worse.

Previously I was able to more or less to ignore them. Now I have to use QT_LOGGING_RULES=kwin_scene_opengl=false.

Last edited by pinx (Today 15:47:09)

Offline

#15 Today 15:19:51

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 74,642

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

RE b) they changed to this form

Yeah that's a duplicate of https://bbs.archlinux.org/viewtopic.php?id=310531

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

#16 Today 15:43:28

pinx
Member
Registered: Yesterday
Posts: 10

Re: [Solved] kwin_wayland: eglInitialize failed. OpenGL in hybrid graphics

Thank you very much for getting to the bottom, seth!

Offline

Board footer

Powered by FluxBB