GNU bug report logs - #29067
26.0.90; "Invalid client frame" when doing save-buffers-kill-terminal

Previous Next

Full log

View this message in rfc822 format

From: Kaushal Modi <kaushal.modi <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 29067 <at> debbugs.gnu.org
Subject: bug#29067: 26.0.90; "Invalid client frame" when doing save-buffers-kill-terminal
Date: Mon, 30 Oct 2017 18:49:29 +0000

[Message part 1 (text/plain, inline)]

On Mon, Oct 30, 2017 at 2:40 PM Eli Zaretskii <eliz <at> gnu.org> wrote:

>
> Please show a Lisp backtrace from this error.
>

Sorry, should have done that earlier; I just assumed it didn't hold any
information of value for this case.

Debugger entered--Lisp error: (error "Invalid client frame")
  signal(error ("Invalid client frame"))
  error("Invalid client frame")
  server-save-buffers-kill-terminal(nil)
  save-buffers-kill-terminal()
  eval((save-buffers-kill-terminal) nil)
  eval-expression((save-buffers-kill-terminal) nil nil 127)
  funcall-interactively(eval-expression (save-buffers-kill-terminal) nil
nil 127)
  call-interactively(eval-expression nil nil)
  command-execute(eval-expression)

When I edebugged save-buffers-kill-terminal, I saw that (frame-parameter
nil 'client) was evaluating to non-nil as it was returning "Unprintable
entity". So it is executing the wrong clause of that if.

-- 

Kaushal Modi

[Message part 2 (text/html, inline)]

Previous Next

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