Subject: bug#30019: 26.0.90; Invalid specification of parent-frame with desktop-read

From: Eli Zaretskii <[email-masked]>
Date: Thu, 11 Jan 2018 18:07:39 +0200

> Date: Thu, 11 Jan 2018 11:54:57 +0100
> From: martin rudalics <[email-masked]>
> CC: [email-masked], [email-masked]
> 
> Normal minibuffer frames are top-level frames, they have no parent.
> So we have no problems with minibuffer frames because the window
> system will have created and made them visible some time before the
> first user interaction occurs.
> 
> The problem here is with child frames whose window system parent
> window can be assigned only after that parent window has been made by
> the window system and whose identity has been reported to us.

OK, so I've misinterpreted your references to minibuffer.

Then the problem is that desktop.el is trying to restore a child frame
whose parent frame's ID has not yet been reported back to us, is that
right?