Bug#1029503: marked as done (spirv-cross: new upstream release breaks API)
Your message dated Mon, 30 Jan 2023 15:00:03 +0100 with message-id <20230130140003.oyt2tb2gkqnkm...@mail.gaussglocke.de> and subject line Re: Bug#1029503: Last upload of spirv-cross breaks API has caused the Debian Bug report #1029503, regarding spirv-cross: new upstream release breaks API to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1029503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spirv-cross Version: 2021.01.15+1.3.236.0-1 Severity: serious Tags: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear co-maintainers, the recent upload of spirv-cross 2021.01.15+1.3.236.0-1 has incompatible API changes which break reverse dependencies, notably src:filament. This type of change is no longer appropriate since the 2023-01-12 transition freeze. Please keep this bug at a RC-critical severity to prevent migration to testing. Relevant excerpt from a filament rebuild: [...] [ 50%] Built target test_utils /<>/libs/filamat/src/GLSLPostProcessor.cpp:349:75: error: too few arguments to function call, expected 3, have 2 glslCompiler.remap_ext_framebuffer_fetch(i.first, i.second); ^ /usr/include/spirv_cross/spirv_glsl.hpp:203:7: note: 'remap_ext_framebuffer_fetch' declared here void remap_ext_framebuffer_fetch(uint32_t input_attachment_index, uint32_t color_location, bool coherent); ^ 1 error generated. make[3]: *** [libs/filamat/CMakeFiles/filamat.dir/build.make:331: libs/filamat/CMakeFiles/filamat.dir/src/GLSLPostProcessor.cpp.o] Error 1 [...] Cheers Timo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmPOhI8ACgkQ+C8H+466 LVmO/QwAnyuW2b78PW1dGWP/S0uOn10R4Khg1vtayd6dG+d4DItcDYtiXQcB4p4a 1f9zJwnkB3PT2nvpXT29frqvOO9rz4JQ/fT68bEpjluRL3255MNRTjseTSiZRIFA rBkmyflC1+5agaJhuQSH4FR7PkuSpnCKA4uTAuvQf4gYQEmeUGb8Exca2YKXVeK1 8iPTIDyvd8LUVJBhnp0O7d8j1XJXibzewuyEzivGoTGbNJ+PVoeBLSxx1BzOKT5C 2QEpy6Ji9tG9UIzm7AjqNdTwnQOejSXKWthQsyFx4QAgoIOv+ppv2PpZiQWSzgFY CVy8ngQdS2k1uwCokAFperRS9XuoUT0EaR43jALpZ1ryfmSzmZrkGDMyZXaUFV9l ubYMQpp/JBe9YfMV6M02kV45ihbXqHSUdK9QrwVnWGLZIwnoeLJbs+K0Jm/jpfY+ Qq7pVAtEt2Kr+LU0xkssuskKbyMeFvkLJcAXFJ3vI55/e8XgaiHMUJuwzzbnH9aj NOfNqANT =/4Kr -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Control: notfound -1 spirv-cross/2021.01.15+1.3.236.0-1 Hi, * Sebastian Ramacher [2023-01-27 23:55]: Now, the question is what should I do because of the freeze? Should I somehow revert my upload with a new `2021.01.15+1.3.236.0+real2021.01.15` version? Should I fix filament or should I keep the RC #1029503 open against the new version of spirv-cross? Both is acceptable at this stage of the freeze. I have uploaded a fixed version of filament and will close this bug now to let both filament and spirv-cross migrate to testing. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature --- End Message ---
Bug#1029731: libglapi-mesa: Apps fail with 'DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory' after upgrade from 22.3.2-1 to 22.3.3-1
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 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
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 1029731 https://gitlab.freedesktop.org/mesa/mesa/-/issues/8198 Bug #1029731 [libglapi-mesa] libglapi-mesa: Apps fail with 'DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory' after upgrade from 22.3.2-1 to 22.3.3-1 Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/mesa/mesa/-/issues/8198'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1029731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
