bug#22832: 25.0.91; Keyboard navigation broken on menus

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Óscar Fuentes]

emacs -Q

;; disable menu bar:
M-x menu-bar-mode

Press F10 to show the menu. It is not possible to navigate the popup
menu using the keyboard. This worked fine on

GNU Emacs 25.0.50.29 (x86_64-unknown-linux-gnu, X toolkit) of 2016-01-21
5293d1bdb3e665a565af032a163004c976328cc2



In GNU Emacs 25.0.91.3 (x86_64-unknown-linux-gnu, X toolkit)
 of 2016-02-25 built on qcore
Repository revision: 8be32cf45cd8b39ff6c8dc431b0ac04a0959786d
Windowing system distributor 'The X.Org Foundation', version 11.0.11702000
System Description:	Ubuntu 15.10

Configured using:
 'configure --without-toolkit-scroll-bars --with-x-toolkit=lucid'

Configured features:
XAW3D XPM JPEG TIFF GIF PNG SOUND GSETTINGS NOTIFY GNUTLS LIBXML2
FREETYPE XFT ZLIB LUCID X11

Important settings:
  value of $LANG: C
  locale-coding-system: nil

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Eli Zaretskii]

> From: oscarfv@telefonica.net (Óscar Fuentes)
> Date: Sat, 27 Feb 2016 20:35:39 +0100
> 
> emacs -Q
> 
> ;; disable menu bar:
> M-x menu-bar-mode
> 
> Press F10 to show the menu. It is not possible to navigate the popup
> menu using the keyboard. This worked fine on
> 
> GNU Emacs 25.0.50.29 (x86_64-unknown-linux-gnu, X toolkit) of 2016-01-21
> 5293d1bdb3e665a565af032a163004c976328cc2

Can you see if 8784ebf is the culprit?  (On my platform, F10 in this
situation just invokes tmm-menubar, as it always did, so I cannot
debug this.)

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Óscar Fuentes]

Eli Zaretskii <eliz@gnu.org> writes:

> Can you see if 8784ebf is the culprit?

No, it isn't. The previous revision also shows the problem.

Give an hour and I'll bisect the problem.

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Eli Zaretskii]

> From: oscarfv@telefonica.net (Óscar Fuentes)
> Cc: 22832@debbugs.gnu.org
> Date: Sat, 27 Feb 2016 21:03:56 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Can you see if 8784ebf is the culprit?
> 
> No, it isn't. The previous revision also shows the problem.

Could it be 76045f7, then?

> Give an hour and I'll bisect the problem.

Thanks.

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Óscar Fuentes]

Eli Zaretskii <eliz@gnu.org> writes:

>> Give an hour and I'll bisect the problem.

It looks like a local problem. After building from scratch the same
revision that works on my installed Emacs (5293d1b) the new build shows
the problem, but the old installed build works fine. The only reason I
can think of is some library that is statically linked to Emacs and
changed on the last month, but the OS package manager's doesn't show
obvious candidates.

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Eli Zaretskii]

> From: oscarfv@telefonica.net (Óscar Fuentes)
> Cc: 22832@debbugs.gnu.org
> Date: Sat, 27 Feb 2016 22:05:39 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Give an hour and I'll bisect the problem.
> 
> It looks like a local problem. After building from scratch the same
> revision that works on my installed Emacs (5293d1b) the new build shows
> the problem, but the old installed build works fine. The only reason I
> can think of is some library that is statically linked to Emacs and
> changed on the last month, but the OS package manager's doesn't show
> obvious candidates.

Strange.

Can anyone else reproduce the problem using Óscar's recipe?

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

> Can anyone else reproduce the problem using Óscar's recipe?

This was five years ago, and there was no response.  I'm not able to
reproduce the problem, either, so I'm guessing that this is fixed, and
I'm closing this bug report.  (If anybody can reproduce the problem,
please respond to the debbugs address and we'll reopen.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Óscar Fuentes]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> This was five years ago, and there was no response.  I'm not able to
> reproduce the problem, either, so I'm guessing that this is fixed, and
> I'm closing this bug report.  (If anybody can reproduce the problem,
> please respond to the debbugs address and we'll reopen.)

I can reproduce the problem with:

In GNU Emacs 29.0.50 (build 3, x86_64-pc-linux-gnu, X toolkit, cairo version 1.16.0, Xaw3d scroll bars)
 of 2021-12-02 built on sky
Repository revision: 7dfa758fef58dbfcd00baaea374260d5d3510b7f
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12011000
System Description: Debian GNU/Linux bookworm/sid

Configured features:
CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GSETTINGS HARFBUZZ JPEG JSON
LIBOTF LIBSELINUX LIBXML2 MODULES NOTIFY INOTIFY PDUMPER PNG RSVG
SECCOMP SOUND THREADS TIFF TOOLKIT_SCROLL_BARS X11 XAW3D XDBE XIM XPM
LUCID ZLIB


and my configure command (why doesn't it appear on the above chunk of
text copied from M-x report-emacs-bug as it used to do?):

--with-native-compilation --without-toolkit-scroll-bars --with-x-toolkit=lucid --with-modules --without-imagemagick

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Lars Ingebrigtsen]

Óscar Fuentes <oscarfv@telefonica.net> writes:

> I can reproduce the problem with:

OK, reopening.

How do you reproduce the problem, starting from "emacs -Q"?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Óscar Fuentes]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Óscar Fuentes <oscarfv@telefonica.net> writes:
>
>> I can reproduce the problem with:
>
> OK, reopening.
>
> How do you reproduce the problem, starting from "emacs -Q"?

As stated on the original report:

emacs -Q

M-x menu-bar-mode

Press F10, a popup menu is shown, press the cursor keys to navigate the
menu. The cursor keys (or any other keys I tried) have no effect.

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Lars Ingebrigtsen]

Óscar Fuentes <oscarfv@telefonica.net> writes:

> emacs -Q
>
> M-x menu-bar-mode
>
> Press F10, a popup menu is shown, press the cursor keys to navigate the
> menu. The cursor keys (or any other keys I tried) have no effect.

emacs -Q
M-x menu-bar-mode
F10
<down>
<down>

works fine here.  The major difference I can see in the system settings
is that I'm using a Gtk build, but yours seems to be without.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Óscar Fuentes]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Óscar Fuentes <oscarfv@telefonica.net> writes:
>
>> emacs -Q
>>
>> M-x menu-bar-mode
>>
>> Press F10, a popup menu is shown, press the cursor keys to navigate the
>> menu. The cursor keys (or any other keys I tried) have no effect.
>
> emacs -Q
> M-x menu-bar-mode
> F10
> <down>
> <down>
>
> works fine here.  The major difference I can see in the system settings
> is that I'm using a Gtk build, but yours seems to be without.

Exactly. AFAIK the Lucid menu widgets are unrelated to Gtk.

bug#22832: 25.0.91; Keyboard navigation broken on menus

[Mike Kupfer]

Lars Ingebrigtsen wrote:

> emacs -Q
> M-x menu-bar-mode
> F10
> <down>
> <down>
> 
> works fine here.  The major difference I can see in the system settings
> is that I'm using a Gtk build, but yours seems to be without.

FWIW, I see the problem intermittently.  Sometimes keyboard navigation
works, sometimes not.  This is running something a few days old from the
emacs-28 branch, using the Lucid toolkit.

mike

bug#22832: #22832 likely dup of #58771 et al

[Mike Kupfer]

I was going through some old Emacs bug reports and came across #22832.
This looks like it's the same issue as 57320/57518/58771/59733, which
was fixed in Emacs 29.

mike

bug#22832: #22832 likely dup of #58771 et al

[Óscar Fuentes]

Mike Kupfer <kupfer@rawbw.com> writes:

> I was going through some old Emacs bug reports and came across #22832.
> This looks like it's the same issue as 57320/57518/58771/59733, which
> was fixed in Emacs 29.

Thanks for the heads up. It works here too. Closing.