unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 14033@debbugs.gnu.org
Subject: bug#14033: 24.3.50; Deleting frame and reconnecting to Emacs daemon results in blank frame
Date: Sun, 06 Dec 2020 19:56:54 +0100	[thread overview]
Message-ID: <878saasqyx.fsf@gnus.org> (raw)
In-Reply-To: <20812.47615.543535.749761@a1i15.kph.uni-mainz.de> (Ulrich Mueller's message of "Fri, 22 Mar 2013 21:07:27 +0100")

Ulrich Mueller <ulm@gentoo.org> writes:

> With Emacs from Bzr linked against Motif 2.3.4, I get a blank frame
> when connecting for the second time to a daemonised Emacs.
>
> To reproduce:
>
>    $ emacs -Q --daemon
>    $ emacsclient -c
>    Waiting for Emacs...
>
> Up to here everything appears to be o.k.
> Now I delete the frame and try to connect for a second time:
>
>    C-x 5 0
>    $ emacsclient -c
>    Waiting for Emacs...
>    *ERROR*: X protocol error: RenderBadPicture (invalid Picture parameter) on protocol request 138
>
> This time, I get above error message and a blank Emacs frame. (For the
> menu bar, the background colour is visible, but otherwise it is also
> blank. The toolbar is not visible at all.) Sometimes the error appears
> only when connecting to the daemon for the third time.
>
> The problem disappears when I disable the menu bar ("M-x menu-bar-mode
> RET" before doing "C-x 5 0" the first time).

(This bug report unfortunately got no response at the time.)

I am unable to reproduce this error.  Do you still see it in more recent
versions of Emacs?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-12-06 18:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 20:07 bug#14033: 24.3.50; Deleting frame and reconnecting to Emacs daemon results in blank frame Ulrich Mueller
2020-12-06 18:56 ` Lars Ingebrigtsen [this message]
2020-12-06 19:52   ` Ulrich Mueller
2020-12-06 20:27     ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878saasqyx.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=14033@debbugs.gnu.org \
    --cc=ulm@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).