Bug#1050734: xfce4-terminal: Preference to disable F10 key not working

[Joe]

Package: xfce4-terminal
Version: 1.1.0-1
Severity: normal

Dear Maintainer,

Edit-> Preferences in xfce4-terminal includes a checkbox to disable use
of the F10 key by the terminal so it can be used by the running
program. This is not working, F10 is working as the terminal menu key.
I have cleared the box, closed the terminal, opened another one and
checked the box, no change.

In mc, F10 is the key to close the current file and also to close mc.
mc does have a backup in the form of a bottom F-key bar, which can be
clicked with a mouse, but having used mc for a couple of decades, this
action does not come normally for me, I normally operate mc with just
the keyboard.

This problem has happened in the last week or two, I've been using
xfce4-terminal with mc for years previously.


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

Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-terminal depends on:
ii exo-utils 4.18.0-1
ii libatk1.0-0 2.49.90-4
ii libc6 2.37-7
ii libcairo2 1.16.0-7
ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii libglib2.0-0 2.77.2-1
ii libgtk-3-0 3.24.38-4
ii libpango-1.0-0 1.51.0+ds-2
ii libpcre2-8-0 10.42-3
ii libutempter0 1.2.1-3
ii libvte-2.91-0 0.73.93-1
ii libx11-6 2:1.8.6-1
ii libxfce4ui-2-0 4.18.4-1
ii libxfce4util7 4.18.1-2
ii libxfconf-0-3 4.18.1-1
ii perl 5.36.0-8

Versions of packages xfce4-terminal recommends:
ii dbus-user-session [default-dbus-session-bus] 1.14.8-2

xfce4-terminal suggests no packages.

-- no debconf information

[Martin Šturc]

Hello all,

I came accross this issue on my Debian unstable amd64 machine a few days
ago.

The upstream's bug
https://gitlab.xfce.org/apps/xfce4-terminal/-/issues/259#note_78740
suggests a temporary workaround.
This works for me.

Best regards

Martin Šturc