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#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55 Date: Thu, 03 Aug 2017 19:56:23 +0200 Message-ID: <598363C7.5010609@gmx.at> 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> <833799z61h.fsf@gnu.org> <5982E700.5010006@gmx.at> <83wp6ky5xn.fsf@gnu.org> 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 1501783099 6790 195.159.176.226 (3 Aug 2017 17:58:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 3 Aug 2017 17:58:19 +0000 (UTC) Cc: 27816@debbugs.gnu.org, bugs@gnu.support To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Aug 03 19:58:15 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 1ddKNp-0000zs-UP for geb-bug-gnu-emacs@m.gmane.org; Thu, 03 Aug 2017 19:58:06 +0200 Original-Received: from localhost ([::1]:37316 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ddKNw-0008Az-6g for geb-bug-gnu-emacs@m.gmane.org; Thu, 03 Aug 2017 13:58:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45170) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ddKNq-0008AZ-Q6 for bug-gnu-emacs@gnu.org; Thu, 03 Aug 2017 13:58:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ddKNm-0003SX-Lx for bug-gnu-emacs@gnu.org; Thu, 03 Aug 2017 13:58:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:37660) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ddKNm-0003ST-Jk for bug-gnu-emacs@gnu.org; Thu, 03 Aug 2017 13:58:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ddKNl-0005Sl-Va for bug-gnu-emacs@gnu.org; Thu, 03 Aug 2017 13:58:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 03 Aug 2017 17:58:01 +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.150178304620949 (code B ref 27816); Thu, 03 Aug 2017 17:58:01 +0000 Original-Received: (at 27816) by debbugs.gnu.org; 3 Aug 2017 17:57:26 +0000 Original-Received: from localhost ([127.0.0.1]:40337 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ddKNB-0005Rp-Rm for submit@debbugs.gnu.org; Thu, 03 Aug 2017 13:57:26 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:53293) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ddKNA-0005Ra-7v for 27816@debbugs.gnu.org; Thu, 03 Aug 2017 13:57:24 -0400 Original-Received: from [192.168.1.100] ([46.125.250.81]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Me5Q2-1e22DF1Ifm-00PrIa; Thu, 03 Aug 2017 19:56:35 +0200 In-Reply-To: <83wp6ky5xn.fsf@gnu.org> X-Provags-ID: V03:K0:GAb4JG1LrHVf7sf5b38fspeL19vTi/yq0qOzSbnUthmgHt0nlCG uSsHLt+GKYkTzAiF3GVvwB5adtOHs4SjAV+ywURx9UYxqRTYsAnAY45efOgGNbUFyBWqiN/ XeoexEKzjaaAft3ef9jVrHt5kynvSdxni1xYIC0gtoxrXfD4qprVYwi95bIyFgoozLjamY9 jNiCspoJi/pjUrF/PtJ1A== X-UI-Out-Filterresults: notjunk:1;V01:K0:J4wMUmiPoXg=:K7VnynSsJ85k60Ca+1VM3f C0XLOPJPZIrG29VJkHsm9XYFHbnjcClqbkM+ghpMMop3P6LGEA6jt9qzdV9JdaJnrGTWVf1Ec MdZi3xdYkmoEtLv+iD/dwbsycmnyeTCdcKTTjz7PuvoK5RbNB5i0xbK3/mwGs2K0axJc2gwA1 T0E15yJ5HGd129kA4/Z4nsf9naUnii5bMifFPMn4GAoCYAfD/9vJFBiD0sy9nKbLm1MRM0kmQ weYrdD9Eh5MHPBk/PSSgSCikVbPd3SIVfKMh0cu3lcUlisgTxY9MgIifGYcGoDKwTUXa/gG3c PdfTVdh6Vx+ETf0Z/a9yIwFs3hz2exuwCA8GTZnAdhCAcYIaMwka4X73L++82N0x4+8DD9J1W 9L/TKdLyclXmaL1epH8pDzzxe6yxM7a0FgCGEOJd73FDb1NDL+4dU8zTAMRgGOTNyr46i6zId VPorqETeiloYYHqhtzwx/9No6Pm+sVJvZfNGAHgAzGfQemaDcVC2x+jTkSN3TKjJgQMdqhozf qTLAEw4ySYEM99yPIVBasQ+60jiJPlXXr3dUj0S373XEho9icFXFLWRQwQtMcaLLKnDlE6saG 5EAJOCX/NKZg635xiI5UsJT8xBmJRaVVXwHxOcdShBjItCQ3wvY1/XPcuD32yeaG9xcggc1Ms eTwdnwV/SBiPKsZNZJZhZ7NzulTdxK/7Y8Gw1Q+w/ZuTMVjiPGUxR8q+kp3YSs72zGCVI+TbG 8ij5wYOiba9w2/xe/4EoMABvAsprxcxUQSwWbs3IGWTt0UQcq61TFFjEcwokdXOZ2T4V6fY0 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:135295 Archived-At: > Could any of this be related to the change whereby we no longer wait > for the frame to become visible? You mean that Emacs now doesn't consume CPU cycles any more? In any case, I think that the problem has existed ever since. It just manifests itself in different ways. And it would be nice if someone else who builds Lucid tried the scenario. It's even simpler than Jean Louis describes it: (1) In one terminal do emacs -Q -nw (2) M-x server-start (3) In another terminal do emacsclient -c (4) In the GUI frame do C-x 5 0 and repeat (3) and (4) at least five times. > If you run Emacs in X synchronized mode and put a breakpoint on > x_error_quitter, can you see why the problem happens? Which picmap > parameter is invalid? I'll try to do that as soon as I understand how it works and how to debug it. Also IIRC synchronized mode didn't always work 100% reliably here. From the pngs it seems obvious that the arrows above and below the slider didn't get drawn. >> /usr/lib/gcc/x86_64-linux-gnu/4.7/include/stddef.h:426:3: note: previ= ous declaration of =E2=80=98max_align_t=E2=80=99 was here > > Sounds like some Gnulib-related issue. Perhaps Paul could help figure= > this out. I suppose some leftovers in the build directory. I have to build from scratch. >> BTW, I never use emacsclient and have no idea how to use it. Is ther= e a >> way to stop the server from the starting emacs? > > I don't understand the question. When Emacs starts, the server is not= > started automatically, so I'm unsure what is it that you want to do. > Please tell me what I missed. The doc-string of =E2=80=98server-start=E2=80=99 says that this would "Al= low this Emacs process to be a server for client processes". How can I "Stop this Emacs process to be a server for client processes"? Frankly I have no idea what emacsclient is, how it works and how it interacts with the server. martin