GNU bug report logs - #60163
29.0.60; Error in post-command-hook (winner-save-old-configurations): (wrong-type-argument frame-live-p #<dead frame code action 0x563ea51cbf70>)

Previous Next

Full log

View this message in rfc822 format

From: Po Lu <luangruo <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 60163 <at> debbugs.gnu.org, 张云峰 <zhangyunfeng0101 <at> gmail.com>, João Távora <joaotavora <at> gmail.com>
Subject: bug#60163: 29.0.60; Error in post-command-hook (winner-save-old-configurations): (wrong-type-argument frame-live-p #<dead frame code action 0x563ea51cbf70>)
Date: Mon, 19 Dec 2022 20:54:11 +0800

Eli Zaretskii <eliz <at> gnu.org> writes:

> [Please use Reply All to reply, to keep the bug tracker on the CC List.]
>
>> From: 张云峰 <zhangyunfeng0101 <at> gmail.com>
>> Date: Mon, 19 Dec 2022 11:46:10 +0800
>> 
>> Sorry to reply you so late.
>> 
>> Follow these steps can reproduce this bug:
>> 1. compile emacs29 with option --with-pgtk
>> 2. edit source code (e.g. rust code) in lsp-bridge-mode
>> 3. execute `lsp-bridge-code-action` on a variable, you will see a popup menu, press `Enter ` or just `Ctrl-g`,
>> then bug reproducted.
>> 
>> NOTE: When I compile emacs29 without option --with-pgtk, this bug is gone, and everything is fine. so this
>> bug may be relative to pgtk feature
>
> Po Lu and João, would you please try to look at this?  The combination
> of required features to reproduce the problem is beyond my abilities.

Unfortunately I don't have `lsp-bridge-mode' installed.  Does the dead
frame happen to be a child frame by any chance?

Previous Next

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