• Bug#1064943: libvte-2.91-0: fails to emit bell if on a different worksp

    From as@php.net@21:1/5 to All on Wed Feb 28 02:50:01 2024
    Package: libvte-2.91-0
    Version: 0.75.91-2
    Severity: normal
    Tags: a11y
    X-Debbugs-Cc: none

    Somewhere between 0.74.2-1 and 0.75.91-2, there was a regression in
    libvte that causes it to not emit a bell signal if the terminal window
    is on a different workspace. This seems to be fixed upstream (0.77.0).
    Assuming trixie is staying at 0.75.91, it would be nice if the package maintainer could pull in a patch to fix this behavior.

    To reproduce, pick a terminal emulator that uses libvte (like
    xfce4-terminal), ensure visual and/or audible bell is enabled, and run
    it in a window manager with workspaces (like Xfce). Confirm the bell
    works by running something like

    $ sleep 2 && echo -e '\a'

    and switching focus to a different window before the sleep completes.
    When the echo runs, the terminal should emit an audible beep (may rely
    on pcspkr kernel module depending on your terminal emulator) and/or
    your window manager should style it "urgent"
    (_NET_WM_STATE_DEMANDS_ATTENTION) often represented by blinking or
    flashing.

    Now do the same thing except switch to a different workspace. No bell.
    It seems the bell GTK signal isn't processed until the terminal is
    back in the active workspace.

    I've confirmed this behavior in the vte test app as well.

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

    Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT)
    Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
    Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
    (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
    Shell: /bin/sh linked to /usr/bin/dash
    Init: systemd (via /run/systemd/system)
    LSM: AppArmor: enabled

    Versions of packages libvte-2.91-0 depends on:
    ii libatk1.0-0 2.50.0-1+b1
    ii libc6 2.37-15
    ii libcairo-gobject2 1.18.0-1+b1
    ii libcairo2 1.18.0-1+b1
    ii libfribidi0 1.0.13-3+b1
    ii libgcc-s1 14-20240201-3
    ii libglib2.0-0 2.78.4-1
    ii libgnutls30 3.8.3-1
    ii libgtk-3-0 3.24.41-1
    ii libicu72 72.1-4+b1
    ii liblz4-1 1.9.4-1+b2
    ii libpango-1.0-0 1.51.0+ds-4
    ii libpangocairo-1.0-0 1.51.0+ds-4
    ii libpcre2-8-0 10.42-4+b1
    ii libstdc++6 14-20240201-3
    ii libsystemd0 255.3-2
    ii libvte-2.91-common 0.75.91-2

    libvte-2.91-0 recommends no packages.

    libvte-2.91-0 suggests no packages.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From as@php.net@21:1/5 to All on Mon Mar 4 18:40:01 2024
    The maintainers pointed me to this commit:

    https://gitlab.gnome.org/GNOME/vte/-/commit/6581fea7a4450a724ec3a4bc4859156722d1df1d.patch

    Applying this on top of 0.75.91 indeed fixes the bug.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)