From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55 Date: Wed, 02 Aug 2017 21:51:13 +0300 Message-ID: <838tj1ztum.fsf@gnu.org> References: <837eyw7fma.fsf@gnu.org> <20170725174823.GD5480@protected.rcdrun.com> <83vamg5pu8.fsf@gnu.org> <20170727073827.GA17695@protected.rcdrun.com> <83vamd4x4n.fsf@gnu.org> <20170727193029.GH26109@protected.rcdrun.com> <83lgn93unk.fsf@gnu.org> <20170728212321.GA1358@protected.rcdrun.com> <20170728233123.GA29256@protected.rcdrun.com> <83zibn3gei.fsf@gnu.org> <20170802161229.GA28199@protected.rcdrun.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1501699934 29018 195.159.176.226 (2 Aug 2017 18:52:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 2 Aug 2017 18:52:14 +0000 (UTC) Cc: 27816@debbugs.gnu.org To: Jean Louis Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Aug 02 20:52:10 2017 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 1dcykZ-0007B2-Fq for geb-bug-gnu-emacs@m.gmane.org; Wed, 02 Aug 2017 20:52:08 +0200 Original-Received: from localhost ([::1]:49797 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dcykf-0006aA-Is for geb-bug-gnu-emacs@m.gmane.org; Wed, 02 Aug 2017 14:52:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49460) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dcykY-0006Zr-MZ for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 14:52:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dcykU-0002nT-I6 for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 14:52:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:36114) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dcykU-0002nN-FT for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 14:52:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dcykU-0006bx-96 for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 14:52:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 02 Aug 2017 18:52:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 27816 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 27816-submit@debbugs.gnu.org id=B27816.150169990825393 (code B ref 27816); Wed, 02 Aug 2017 18:52:02 +0000 Original-Received: (at 27816) by debbugs.gnu.org; 2 Aug 2017 18:51:48 +0000 Original-Received: from localhost ([127.0.0.1]:38791 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dcykF-0006bV-TM for submit@debbugs.gnu.org; Wed, 02 Aug 2017 14:51:48 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:58311) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dcykE-0006bI-KO for 27816@debbugs.gnu.org; Wed, 02 Aug 2017 14:51:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dcyk5-0002aH-6n for 27816@debbugs.gnu.org; Wed, 02 Aug 2017 14:51:41 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:60296) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dcyk5-0002a8-3K; Wed, 02 Aug 2017 14:51:37 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2106 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dcyk0-0002z0-Fq; Wed, 02 Aug 2017 14:51:36 -0400 In-reply-to: <20170802161229.GA28199@protected.rcdrun.com> (message from Jean Louis on Wed, 2 Aug 2017 19:12:30 +0300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:135248 Archived-At: > Date: Wed, 2 Aug 2017 19:12:30 +0300 > From: Jean Louis > Cc: Jean Louis , 27816@debbugs.gnu.org > > My configuration of GNU Emacs is following: > > ./configure --prefix=/package/text/emacs-26.0.50 --with-sound=alsa --with-modules --with-x-toolkit=lucid --without-gconf --without-gsettings --without-libsystemd --without-dbus --without-pop --with-mailutils --without-imagemagick --with-x > > I am still getting: > > X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55 > > And I have tried starting Emacs daemon in background without my > ~/.emacs so it is still happening without custom configuration. Please describe the sequence of actions leading to the problem in more detail. Here's what you said about that last time: > What I do, I read email by using mutt, then I hit r to reply email, > including your emails, and I can see the notice from emacsclient on > console, but the graphic frame is dropped, and later I see the bug in > Emacs. This is not detailed enough for me to understand what is going on. I presume that mutt somehow invokes emacsclient and you then expect Emacs to allow you to edit the response to an email message before sending it. But even if that guess is correct, it doesn't say whether emacsclient is invoked to open a new frame or reuse an old frame, whether that frame is a GUI frame or a text-mode frame, and whether any other Emacs frames existed before the invocation of emacsclient and were supposed to remain after you finish editing the response. Btw, does this happen only when emacsclient is invoked from mutt, or also with other programs? What if you invoke emacsclient from the shell prompt -- does the problem happen if you invoke it several times in a row? Also, are you sure the version of emacsclient that is invoked belongs to the version of Emacs which is run in the daemon mode? And finally, if you start Emacs not in daemon mode and then use mutt as you normally do with daemon, does the problem persist or does it go away? > emacsclient is basically remaining in memory as process, but the frame > is disappearing. So Emacs now runs without any frames displayed? > It is annoying as it makes programs wait on emacs client to come back, > as it blocks the console, right? That depends how emacsclient is invoked. But if you invoke it from mutt to edit a response, then you must let it block mutt, because mutt cannot proceed with sending your response until Emacs is done editing it. > Do you think that reason for that can be that I use lucid kit? I very much doubt that. > Now I cannot understand what happened that it started showing this > error, it is being shown in each 4th 5th or so attempt to spawn > emacsclient. Something has changed on your system, it seems.