From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#30019: 26.0.90; Invalid specification of parent-frame with desktop-read Date: Mon, 08 Jan 2018 10:53:17 +0100 Message-ID: <5A533F8D.3080307@gmx.at> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1515405143 24438 195.159.176.226 (8 Jan 2018 09:52:23 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 8 Jan 2018 09:52:23 +0000 (UTC) To: Aaron Jensen , 30019@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Jan 08 10:52:18 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eYU6K-000607-G3 for geb-bug-gnu-emacs@m.gmane.org; Mon, 08 Jan 2018 10:52:16 +0100 Original-Received: from localhost ([::1]:52420 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eYU8J-0004f9-WB for geb-bug-gnu-emacs@m.gmane.org; Mon, 08 Jan 2018 04:54:20 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49522) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eYU85-0004aM-EL for bug-gnu-emacs@gnu.org; Mon, 08 Jan 2018 04:54:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eYU82-00021u-Dq for bug-gnu-emacs@gnu.org; Mon, 08 Jan 2018 04:54:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:59771) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eYU82-00021g-9u for bug-gnu-emacs@gnu.org; Mon, 08 Jan 2018 04:54:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eYU82-0007p0-2X for bug-gnu-emacs@gnu.org; Mon, 08 Jan 2018 04:54:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 08 Jan 2018 09:54:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 30019 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 30019-submit@debbugs.gnu.org id=B30019.151540521130019 (code B ref 30019); Mon, 08 Jan 2018 09:54:02 +0000 Original-Received: (at 30019) by debbugs.gnu.org; 8 Jan 2018 09:53:31 +0000 Original-Received: from localhost ([127.0.0.1]:40218 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eYU7X-0007o7-7x for submit@debbugs.gnu.org; Mon, 08 Jan 2018 04:53:31 -0500 Original-Received: from mout.gmx.net ([212.227.15.15]:50694) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eYU7V-0007nu-Rh for 30019@debbugs.gnu.org; Mon, 08 Jan 2018 04:53:30 -0500 Original-Received: from [192.168.1.100] ([46.125.249.13]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MSdNs-1eQodj1ZG0-00RVYs; Mon, 08 Jan 2018 10:53:23 +0100 In-Reply-To: X-Provags-ID: V03:K0:9yGFX3ndmz5F0wJ2ocPxb3i+gwPXCXSTZ6Xn3IME1o2c8CBZIo9 capJeq41yTA3cWD0Om32E88U1xwM3mYG3ydJ+hg3J9mWXrlv1T4DJWJ2M+ZqT9fQ4VpsOCP 75dxd2md09qc1jQuBZRWlQRp1TVHNueJC3d5UcrYT3DzXfvbMlpDLonnrHpEKMNAPwo0jMe wxErn0Y/6UR94+RTnGyVQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:Fcpq0EDn1Ew=:BdmtJRw7gjml2miKDZ1nKP ORCs67g0iHaOE0YwrMAFOfew9bok2aEYnBFNGFiYj1yXcGiJBCojsscqxw49Tt8F3YHDJFMm8 ZtcymtBd6UAU5zt1eC8DntOWeBBakXte6xcdW/Q+6VHQZroLO5O2MuEmlzbtz8BJtF3+0GlgQ 8BdW2rkUY1oin3Z4w1KV1RFEkmMkz8dvlS2pMcdvferhXLpOSzxmHM17tPF5ARYocjzRyIKTa lbmtNDaAVIyRWqYJWGhpXVSNpWJEhNN/b0SXCvdV1zLFcDxkeTWT7t9YJdLjF5sTTvavESCf1 NleB/kNijmLvTl8gRTFdUocY9PIDzd/epPjhInYa5TZZWd9w578VMF5Pa6EVkwmrwWoylra0b pG8zo44iC8v8u2OtC1SGM8quedG2n878uvMSFTcoxPTJcwDb9RPUZbR+Csw5rwL3brIZd0srs 7edt6qTagBSDAupmKeHGDdiTTBkD/GGzmnY8qckhykG7UY1LEBsbyLZxhwouyXhLMSsJuVznJ J1ej5m7W8o07xIIVS6oAbFPZpblZoB+a2tSPG46mR2nbzW36bEuWOnSJ48cXmwKOvb1a1VkHw QOF2faV0CV0EatkynS5V6RzO7gbHwOvsZmV+c2iMacYw+tmYRvgScfcKl7WmndhFxHusDf4Qs oqd3skJ6qhVlhYJam/EmK8zR0+nepvVuNplqw7HC8mE/czxfu/vv/7hfmR7awVtsK7tJOmWNb SG7j70UgxKo8/BfgK8KRy9ze74Xrx0KPxZWCe5a5OeFQRn7IyjceJ7GRPH8gPvNgm6Zkooc0 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:141895 Archived-At: > I'm not sure of the exact repro, but hopefully the below stack trace= > will help. After playing around with child frames on macOS while runni= ng > desktop-mode, if I restart emacs, I end up with this error during > "desktop-read" > > Debugger entered--Lisp error: (error "Invalid specification of =E2=80=98= parent-frame=E2=80=99") > modify-frame-parameters(# ((parent-frame .= > #))) > set-frame-parameter(# parent-frame # *Warnings* 0x10982e5b0>) > frameset--restore-frame(((minibuffer . #)= [...] > (frameset--parent-frame . > "8810-6104-369C-7DEE") (frameset--mini nil . "8810-6104-369C-7DEE") `frameset--restore-frame' has this (let* ((frame-id (frame-parameter frame 'frameset--parent-frame)) (parent-frame (and frame-id (frameset-frame-with-id frame-id)))) (when (frame-live-p parent-frame) (set-frame-parameter frame 'parent-frame parent-frame))) and x_set_parent_frame has if (!NILP (new_value) && (!FRAMEP (new_value) || !FRAME_LIVE_P (p =3D XFRAME (new_value)) || !FRAME_X_P (p))) { store_frame_param (f, Qparent_frame, old_value); error ("Invalid specification of `parent-frame'"); When you put a breakpoint at the last line I suppose it's the FRAME_X_P (p) call that failed. Can you confirm that? If so, we would not have a window system window for the parent frame yet and we might have to wait "somehow" until it has been created. Too bad. It might be interesting to find out whether `frameset--mini' has the same problem and, if not, why. After all the minibuffer frame is the same as the parent frame. martin