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: Thu, 03 Aug 2017 06:25:30 +0300 Message-ID: <833799z61h.fsf@gnu.org> References: <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> <838tj1ztum.fsf@gnu.org> <20170802193158.GB30834@protected.rcdrun.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1501730780 9963 195.159.176.226 (3 Aug 2017 03:26:20 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 3 Aug 2017 03:26:20 +0000 (UTC) Cc: 27816@debbugs.gnu.org To: Jean Louis , martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Aug 03 05:26:13 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 1dd6lx-0001sD-SW for geb-bug-gnu-emacs@m.gmane.org; Thu, 03 Aug 2017 05:26:06 +0200 Original-Received: from localhost ([::1]:58307 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dd6m3-0005Eh-NQ for geb-bug-gnu-emacs@m.gmane.org; Wed, 02 Aug 2017 23:26:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40504) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dd6lv-0005Ck-OY for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 23:26:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dd6lu-0007mv-QB for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 23:26:03 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:36514) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dd6lu-0007mn-Lj for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 23:26:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dd6lu-00072W-GO for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 23:26: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: Thu, 03 Aug 2017 03:26: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.150173075627047 (code B ref 27816); Thu, 03 Aug 2017 03:26:02 +0000 Original-Received: (at 27816) by debbugs.gnu.org; 3 Aug 2017 03:25:56 +0000 Original-Received: from localhost ([127.0.0.1]:39191 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dd6lo-00072A-4U for submit@debbugs.gnu.org; Wed, 02 Aug 2017 23:25:56 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:49467) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dd6ll-00071y-SC for 27816@debbugs.gnu.org; Wed, 02 Aug 2017 23:25:54 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dd6ld-0007gf-Dv for 27816@debbugs.gnu.org; Wed, 02 Aug 2017 23:25:48 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:40714) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dd6ld-0007gX-5N; Wed, 02 Aug 2017 23:25:45 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3086 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dd6lc-0001rQ-Bf; Wed, 02 Aug 2017 23:25:44 -0400 In-reply-to: <20170802193158.GB30834@protected.rcdrun.com> (message from Jean Louis on Wed, 2 Aug 2017 22:31:58 +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:135265 Archived-At: > Date: Wed, 2 Aug 2017 22:31:58 +0300 > From: Jean Louis > Cc: Jean Louis , 27816@debbugs.gnu.org > > > > 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. > > That is just one application on how I start > emacsclient, but mutt is not related to it. > > Another way of starting emacs is from terminal is > as this: > > emacsclient -s tmp/emacs1001/server -c > Waiting for Emacs... > > then each few times it works, like 85%, then it > fails. > > Emacs is running in background under screen, and > it has (server-start) in .emacs or when I was > testing without ~/.emacs I evaluated > (server-start) in *scratch* buffer. > > 28078 pts/0 Ssl+ 2:02 /usr/bin/emacs --user admin --chdir /home/data1/protected > > Then I run the emacsclient in following fashion: > > 30859 pts/2 S+ 0:00 emacsclient -c -s /home/data1/protected/tmp/emacs1001/server /home/data1/protected/tmp/mutt-protected-1001-30834-15325602171702686152 > > That means my main Emacs is running in console > under screen, it is not just backgrounded > daemon. But I do not think that it is related to > screen. > > I have noticed it now, that if one frame is open, > the error is not appearing on the second frame. > > It appears only when there is no existing frame, > and new frame instance has to be open. > > > guess is correct, it doesn't say whether > > emacsclient is invoked to open a new frame or > > reuse an old frame > > The bug is appearing on opening a new instance of > emacsclient frame when there is no other frame > present. > > > whether that frame is a GUI frame or a text-mode > > frame > > There is no problem with text mode frames. Just > with GUI frame. > > > and whether any other Emacs frames existed > > before the invocation of emacsclient and were > > supposed to remain after you finish editing the > > response. > > The text emacs is running under screen. > > > Btw, does this happen only when emacsclient is > > invoked from mutt, or also with other programs? > > It happens if I invoke emacsclient by any means, > when it is opening first frame. Martin, could you please look into this? It sounds like there's some timing issue with drawing the scroll bars in this scenario, perhaps we attempt to draw the scroll bar too early or something? I wonder why no one else is seeing this problem, though. This part: > The problem is also happening when I do not run it under screen, I can > run it as user. seems to indicate that just doing the following should reproduce the problem with ~25% probability, in an Emacs built with the Lucid toolkit: $ emacs -Q -nw $ emacsclient -s tmp/emacs1001/server -c Jean, does the above indeed reproduce the problem? Btw, Jean, do you have any Emacs-related settings in your X resources? (Although -Q should bypass those as well, AFAIR...)