Dear Maintainer, Since 22.3.4 is out, I've built 22.3.4 myself and checked currently available 22.3.4-1 packages from sid. The problem exists in 22.3.4 as well.
Here is link to created upstream issue. https://gitlab.freedesktop.org/mesa/mesa/-/issues/8198 The problem is caused by commit included in 22.3.3: ``` commit 2adab724e59c662a046cb1da8bfb3177330e01da Author: Asahi Lina <l...@asahilina.net> Date: Wed Dec 21 00:37:31 2022 +0900 kmsro: Fix renderonly_scanout BO aliasing BOs can only have one handle. If renderonly_create_gpu_import_for_resource ends up importing a BO that was already mapped for scanout, it will get the same handle. This leaves us with two renderonly_scanout objects for one handle, and the first one to be destroyed will free it. Import the BO map tracking logic from asahi, to avoid aliasing renderonly_scanout objects. Each actual BO now is only represented by a single object instance, which is reference counted. Fixes KWin full-screen PipeWire capture breaking scanout entirely. ``` I reverted it and that solved this problem. On 23-01-27 00:05, Andrey Skvortsov wrote: > Package: libglapi-mesa > Version: 22.3.3-1 > Severity: important > > Dear Maintainer, > > > after upgrade from 22.3.2-1 to 22.3.3-1 applications starts to crash > with following error > > ``` > янв 26 23:41:00 mobian-dev dbus-daemon[1018]: [session uid=1000 pid=1018] > Activating service name='org.gnome.Console' requested by ':1.34' (uid=1000 > pid=1250 comm="/usr/libexec/phosh") > янв 26 23:41:01 mobian-dev dbus-daemon[1018]: [session uid=1000 pid=1018] > Successfully activated service 'org.gnome.Console' > янв 26 23:41:04 mobian-dev org.gnome.Console[6004]: > DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory > янв 26 23:41:04 mobian-dev org.gnome.Console[6004]: > DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory > ``` > > The system is aarch64 (arm64) Original PinePhone running Phosh. To > trigger this problem I start and close different applications (mostly > gtk3 and gtk4) after some time (~3-5 minutes) no application can start. > > Downgrade to 22.3.2-1 fixes this problem. > > ``` > wget > https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/mesa-vdpau-drivers_22.3.2-1_arm64.deb > wget > https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libegl-mesa0_22.3.2-1_arm64.deb > wget > https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/mesa-va-drivers_22.3.2-1_arm64.deb > wget > https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libglx-mesa0_22.3.2-1_arm64.deb > wget > https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libglapi-mesa_22.3.2-1_arm64.deb > wget > https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libgl1-mesa-dri_22.3.2-1_arm64.deb > wget > https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libgbm1_22.3.2-1_arm64.deb > ``` > > > -- Package-specific info: > glxinfo: > -------- > DISPLAY is not set. > > /usr/share/bug/xserver-xorg-core/script not available > > -- System Information: > Debian Release: bookworm/sid > APT prefers testing-debug > APT policy: (500, 'testing-debug'), (500, 'testing') > Architecture: arm64 (aarch64) > Foreign Architectures: armhf > > Kernel: Linux 6.1-sunxi64 (SMP w/4 CPU threads) > Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages libglapi-mesa depends on: > ii libc6 2.36-8 > > libglapi-mesa recommends no packages. > > libglapi-mesa suggests no packages. > > -- no debconf information -- Best regards, Andrey Skvortsov