Your message dated Mon, 6 Mar 2023 10:47:29 +0000 with message-id <ZAXEwcGiGrYlXy/[email protected]> and subject line Re: Bug#1027452: libmutter-11-0: ffmpeg kmsgrab stopped working after update from 43.2-2 to 43.2-4 has caused the Debian Bug report #1027452, regarding libmutter-11-0: ffmpeg kmsgrab stopped working after update from 43.2-2 to 43.2-4 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 [email protected] immediately.) -- 1027452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027452 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libmutter-11-0 Version: 43.2-4 Severity: normal X-Debbugs-Cc: [email protected] Dear Maintainer, i used to capture my screen with ffmpeg kmsgrab feature, it really simple and very effective. But after update from 43.2-2 to 43.2-4 it captures very distorted images. My own programs for capturing based in same principle stopped working too, for example, my fork of OBS Studio with this feature. (https://github.com/scaledteam/obs-studio) It appears in Gnome Wayland, but Gnome X11 works fine. To test this, run this command: sudo ffmpeg -framerate 30 -device /dev/dri/card0 -f kmsgrab -i - -vf 'hwmap=derive_device=vaapi,scale_vaapi=format=nv12' -c:v h264_vaapi output.mp4 This is zero-copy capture, which means very low CPU load and ability to capture giant resolutions with almost 0% cpu usage. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-0-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 libmutter-11-0 depends on: ii adwaita-icon-theme 43-1 ii gsettings-desktop-schemas 43.0-1 ii libatk1.0-0 2.46.0-4 ii libc6 2.36-7 ii libcairo-gobject2 1.16.0-7 ii libcairo2 1.16.0-7 ii libcanberra0 0.30-10 ii libcolord2 1.4.6-2.1 ii libdrm2 2.4.114-1 ii libegl1 1.5.0-1 ii libfontconfig1 2.13.1-4.5 ii libfribidi0 1.0.8-2.1 ii libgbm1 22.2.4-1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1 ii libgl1 1.5.0-1 ii libglib2.0-0 2.74.4-1 ii libgnome-desktop-3-20 43-2 ii libgraphene-1.0-0 1.10.8-1 ii libgtk-3-0 3.24.35-3 ii libgudev-1.0-0 237-2 ii libice6 2:1.0.10-1 ii libinput10 1.22.0-1 ii libjson-glib-1.0-0 1.6.6-1 ii liblcms2-2 2.13.1-1+b1 ii libpango-1.0-0 1.50.10+ds-1 ii libpangocairo-1.0-0 1.50.10+ds-1 ii libpangoft2-1.0-0 1.50.10+ds-1 ii libpipewire-0.3-0 0.3.63-1 ii libsm6 2:1.2.3-1 ii libstartup-notification0 0.12-6+b1 ii libsystemd0 252.4-1 ii libudev1 252.4-1 ii libwacom9 2.5.0-1 ii libwayland-server0 1.21.0-1 ii libx11-6 2:1.8.3-3 ii libx11-xcb1 2:1.8.3-3 ii libxau6 1:1.0.9-1 ii libxcb-randr0 1.15-1 ii libxcb-res0 1.15-1 ii libxcb1 1.15-1 ii libxcomposite1 1:0.4.5-1 ii libxcursor1 1:1.2.1-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2 ii libxi6 2:1.8-1+b1 ii libxinerama1 2:1.1.4-3 ii libxkbcommon-x11-0 1.4.1-1 ii libxkbcommon0 1.4.1-1 ii libxkbfile1 1:1.1.0-1 ii libxrandr2 2:1.5.2-2+b1 ii libxtst6 2:1.2.3-1.1 ii mutter-common 43.2-4 libmutter-11-0 recommends no packages. libmutter-11-0 suggests no packages. Versions of packages libmutter-11-0 is related to: ii libegl-mesa0 [libegl-vendor] 22.2.4-1 ii libgl1-mesa-dri 22.2.4-1 ii libglx-mesa0 [libglx-vendor] 22.2.4-1 -- no debconf information
--- End Message ---
--- Begin Message ---On Mon, 02 Jan 2023 at 18:30:53 +0500, Alexandr Podgorniy wrote: > I figured out the problem. Mutter on wayland uses multiplane framebuffer, > and it's not compatible with old capture method. It's not very hard to > implement in software that uses kmsgrab, so it's not mutter problem, it's > ffmpeg problem. Thanks, closing as "not a bug" for mutter. smcv
--- End Message ---
