GNU bug report logs - #59733
29.0.50; unrespnsive Xaw menus

Previous Next

Package: emacs;

Reported by: Madhu <enometh <at> meer.net>

Date: Thu, 1 Dec 2022 02:37:01 UTC

Severity: normal

Merged with 57320, 57518, 58771

Found in version 29.0.50

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Po Lu <luangruo <at> yahoo.com>
To: Madhu <enometh <at> meer.net>
Cc: 59733 <at> debbugs.gnu.org
Subject: bug#59733: 29.0.50; unrespnsive Xaw menus
Date: Sun, 04 Dec 2022 14:36:59 +0800
Madhu <enometh <at> meer.net> writes:

> [Maybe this can be done on the same machine with xpra. Right now I'm
> set up walking between two rooms...  it's tricky as the frame display
> can lock up and the process has to be killed.]

You're welcome to try, but my gut feeling is that it won't work.  Thanks
for going through all that trouble to debug this!

> The upshot is XtGrabPointer returns 0 and the menu becomes unresponsive[1]
>
> When it works, i.e. when XtGrabPointer returns True, It seems I'm not
> able to step into XtGrabPointer as `s' puts me on the next line of
> pop_up_menu.

If XtGrabPointer returns a non-zero value, then it means obtaining the
grab failed.  Exactly which non-zero value does it return?  Do the menus
start working if you comment out the call to "XtGrabPointer" entirely?

The relevant return codes are:

        #define GrabSuccess		0
        #define AlreadyGrabbed		1
        #define GrabInvalidTime		2
        #define GrabNotViewable		3
        #define GrabFrozen		4

> PS (can the typo in the Subject line be fixed)

Yes, as long as you keep the "bug#" intact.




This bug report was last modified 2 years and 182 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.