Your message dated Sat, 21 Feb 2026 13:32:48 +0000
with message-id <[email protected]>
and subject line Re: Bug#1081963: mesa-vulkan-drivers: Intel driver prints 
messages to standard error
has caused the Debian Bug report #1081962,
regarding mesa-vulkan-drivers: Intel driver logs "FINISHME" warnings on load
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.)


-- 
1081962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081962
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libgtk-4-1
Version: 4.16.1+ds-2
Severity: normal

I use NeovimGtk, which is a GTK+4 graphical frontend to Neovim.  With
the new version uploaded to unstable today, spawning an editor includes
the following messages on the terminal:

  MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FINISHME: support 
YUV colorspace with DRM format modifiers
  MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:794: FINISHME: support 
more multi-planar formats with DRM modifiers

Since I realize NeovimGtk is not in Debian at the moment, this can also
be reproduced with gnome-text-editor, which is:

  % gnome-text-editor foo.rs
  MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FINISHME: support 
YUV colorspace with DRM format modifiers
  MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:794: FINISHME: support 
more multi-planar formats with DRM modifiers

It is also reproducible with gnome-mahjongg, so I assume it happens with
all GTK+4 apps.

GTK and the libraries it depends on should never write to stderr unless
a user-visible problem has occurred, since this is annoying when being
invoked in the terminal.  Since the software appears to be otherwise
functional here, it should remain silent.

I realize this may be a bug in Mesa, but if it will not be fixed
promptly, please apply a workaround to revert the appropriate parts to
the 4.14 version in the meantime.

-- System Information:
Debian Release: trixie/sid
  APT prefers oldstable-security
  APT policy: (500, 'oldstable-security'), (500, 'unstable'), (500, 'stable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.10.6-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_WARN
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgtk-4-1 depends on:
ii  adwaita-icon-theme            47.0-1
ii  hicolor-icon-theme            0.18-1
ii  libc6                         2.40-2
ii  libcairo-gobject2             1.18.2-1
ii  libcairo-script-interpreter2  1.18.2-1
ii  libcairo2                     1.18.2-1
ii  libcloudproviders0            0.3.6-1
ii  libcpdb-frontend2t64          2.0~b5-1.2+b2
ii  libcpdb2t64                   2.0~b5-1.2+b2
ii  libepoxy0                     1.5.10-1+b2
ii  libfontconfig1                2.15.0-1.1
ii  libfribidi0                   1.0.15-1
ii  libgdk-pixbuf-2.0-0           2.42.12+dfsg-1
ii  libgles2                      1.7.0-1+b1
ii  libglib2.0-0t64               2.82.0-1
ii  libgraphene-1.0-0             1.10.8-4
ii  libgtk-4-common               4.16.1+ds-2
ii  libharfbuzz-subset0           9.0.0-1
ii  libharfbuzz0b                 9.0.0-1
ii  libjpeg62-turbo               1:2.1.5-3
ii  libpango-1.0-0                1.54.0+ds-2
ii  libpangocairo-1.0-0           1.54.0+ds-2
ii  libpangoft2-1.0-0             1.54.0+ds-2
ii  libpng16-16t64                1.6.43-5
ii  libtiff6                      4.5.1+git230720-5
ii  libvulkan1                    1.3.290.0-1
ii  libwayland-client0            1.23.0-1
ii  libwayland-egl1               1.23.0-1
ii  libx11-6                      2:1.8.7-1+b1
ii  libxcursor1                   1:1.2.2-1
ii  libxdamage1                   1:1.1.6-1+b1
ii  libxext6                      2:1.3.4-1+b1
ii  libxfixes3                    1:6.0.0-2+b1
ii  libxi6                        2:1.8.1-1
ii  libxinerama1                  2:1.1.4-3+b1
ii  libxkbcommon0                 1.6.0-1+b1
ii  libxrandr2                    2:1.5.4-1
ii  shared-mime-info              2.4-5

Versions of packages libgtk-4-1 recommends:
pn  cpdb-backend-cups         <none>
ii  iso-codes                 4.17.0-1
ii  libgtk-4-bin              4.16.1+ds-2
ii  libgtk-4-media-gstreamer  4.16.1+ds-2
ii  librsvg2-common           2.59.0+dfsg-3

Versions of packages libgtk-4-1 suggests:
ii  gvfs  1.56.0-1

-- no debconf information

-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Version: 26.0.0~rc3-1

On Mon, 16 Sep 2024 at 18:49:56 +0000, brian m. carlson wrote:
With today's libgtk-4-1 upgrade, starting any GTK+4 program causes
Mesa's Intel driver to print the following to standard output:

 MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FINISHME: support 
YUV colorspace with DRM format modifiers
 MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:794: FINISHME: support 
more multi-planar formats with DRM modifiers

This warning appears to have been silenced in production builds of Mesa 26.0.0 upstream (https://gitlab.freedesktop.org/mesa/mesa/-/issues/14259, https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/38369) and I no longer see it with the version that recently reached forky.

    smcv

--- End Message ---

Reply via email to