Bugzilla – Bug 1212478
Kontact, Kmail, Digikam all fail to start with EGL_BAD_ALLOC.
Last modified: 2023-06-17 22:24:54 UTC
For about a week now some of the KDE apps fail to start. This is what I get when starting from command line: ps@beest:~> kontact -v kontact 5.23.2 (23.04.2) ps@beest:~> kontact [9718:9764:0617/200306.668564:ERROR:gl_context_egl.cc(259)] eglCreateContext failed with error EGL_BAD_ALLOC 21 -- exe=/usr/bin/kontact 17 -- platform=wayland 16 -- appname=kontact 17 -- apppath=/usr/bin 10 -- signal=11 9 -- pid=9718 28 -- appversion=5.23.2 (23.04.2) 20 -- programname=Kontact 31 -- bugaddress=submit@bugs.kde.org KCrash: Application 'kontact' crashing... The Wayland connection experienced a fatal error: Bad file descriptor ps@beest:~> inxi -Ga Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Lenovo driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300 Device-2: NVIDIA TU104GLM [Quadro RTX 5000 Mobile / Max-Q] vendor: Lenovo driver: nvidia v: 470.182.03 alternate: nouveau,nvidia_drm non-free: 530.xx+ status: current (as of 2023-05) arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: none empty: DP-1,DP-2,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:1eb5 class-ID: 0300 Device-3: Chicony ThinkPad T490 Webcam driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:3 chip-ID: 04f2:b681 class-ID: 0e02 serial: 6926 Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.2 compositor: kwin_wayland driver: X: loaded: intel,nvidia unloaded: modesetting dri: i965 gpu: i915,nvidia display-ID: 0 Monitor-1: eDP-1 res: 2560x1440 size: N/A modes: N/A API: OpenGL v: 4.6 Mesa 23.1.2 renderer: Mesa Intel UHD Graphics 630 (CFL GT2) direct-render: Yes What info is required to get this fixed? Is there a possible workaround until then? best, peter
Mesa 23.1.2 is broken, bug 1212345. *** This bug has been marked as a duplicate of bug 1212345 ***