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: Sat, 05 Aug 2017 14:46:12 +0200 Message-ID: <5985BE14.5070207@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> <5984362B.3030205@gmx.at> <838tizy84b.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: 7bit X-Trace: blaine.gmane.org 1501937290 1515 195.159.176.226 (5 Aug 2017 12:48:10 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 5 Aug 2017 12:48:10 +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 Sat Aug 05 14:48:06 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 1ddyUv-00008F-R4 for geb-bug-gnu-emacs@m.gmane.org; Sat, 05 Aug 2017 14:48:05 +0200 Original-Received: from localhost ([::1]:56710 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ddyV2-0002cj-0n for geb-bug-gnu-emacs@m.gmane.org; Sat, 05 Aug 2017 08:48:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57293) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ddyUw-0002c8-BS for bug-gnu-emacs@gnu.org; Sat, 05 Aug 2017 08:48:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ddyUs-0005P1-3l for bug-gnu-emacs@gnu.org; Sat, 05 Aug 2017 08:48:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:39933) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ddyUr-0005OT-Th for bug-gnu-emacs@gnu.org; Sat, 05 Aug 2017 08:48:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ddyUr-0003rV-MW for bug-gnu-emacs@gnu.org; Sat, 05 Aug 2017 08:48:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 05 Aug 2017 12:48: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.150193722414777 (code B ref 27816); Sat, 05 Aug 2017 12:48:01 +0000 Original-Received: (at 27816) by debbugs.gnu.org; 5 Aug 2017 12:47:04 +0000 Original-Received: from localhost ([127.0.0.1]:42610 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ddyTw-0003qH-Bz for submit@debbugs.gnu.org; Sat, 05 Aug 2017 08:47:04 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:49788) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ddyTu-0003pe-2e for 27816@debbugs.gnu.org; Sat, 05 Aug 2017 08:47:02 -0400 Original-Received: from [192.168.1.100] ([46.125.250.55]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MdWO8-1e16zG1hiG-00PKDG; Sat, 05 Aug 2017 14:46:18 +0200 In-Reply-To: <838tizy84b.fsf@gnu.org> X-Provags-ID: V03:K0:HGk3upp/6fqnTEacYYP3PAK+9oVKHxDoxJnBaZZO5CETMkKOaGH zsAR9ZhTdN6X7roVPlitzClxHEPkGHL9CVioH6C2hWrYeG/Fn+vGnN8AYtDgLvJkbSxqW6b LpOkvaSHxDKxgsGCpiRZu2wffDZSvzvbeV/Y4252dqMAKABzZAVCOZL7R6ww2f+pkRzpptr P44kPN9tgMnL5oS2uo/8A== X-UI-Out-Filterresults: notjunk:1;V01:K0:H0kNeuNkX+Y=:7Qgt26VMlGO2n8JAvy0ccr hrVSOG2ISxnp2hctGv/EqZcm+qXIi8XZs80LZSkMJGj5jawnxliOpPyDtKiemQgcfr2cX4tja AOUGfs3CqCwfVcQWxpg7+Fu0J3PS8V7Tzbh5oN59jnvbu91nA1Zt3L75dGas6dPH/SIgLbaAI XVrwCNytsYYPpyownshx00PjxjzXcnXo3xUyRLDU/5LjGw7BjeTwttJIQ/5cEw0gXgnVGNNaY q+mqMyTLKxFpBbtboV5zcNUY3icN185idY+a3Pz5KYFPo/Gp6kfYiGcJPnGN4lIdyhjnaRbtq eudGIlkqQpFILBnmiwIfkFlT+4i8I3NLdxpIu0yf0ufmMjiIh4he5STn7FsP5Er2EKpKXrdlI sscwvE8FYYJnRpEJLr5xqV3dI3VdJQFYLSF5Vhjz5V9nHS/AoXbQsXBKa2Y7Fw8x7QHR7mHnB PEFJHoKvoFlmvuDWN1dYGCBlSo2iNxaDI8rlmq/wM1b0PSopAdrqJ+LDSC7llxKh4PFJ8J5n2 NQkG3jwM5ahHc/6n8Rxk8VUTN0rOiVih7p3JlDVh60uZPgMUcAsAgQfGTlCwSsKc8kOEDQUKm UJTtgoCrcPwbJFnFKNREOgvdExGCRdXyaxxxwGCWFQyuCzLuqy9IrBmgtelTTEi3/CdH0NQyo swy8wbVfz3aZONJR3AQa935PGm6QS9jGxwz7a264iFqWx2UZz9SdYFzVaD+ss8r+TjfSFErRI wVpEzRKyMjBASx9xTVjwZ4fyfCvEo59vOTfucQK9kgwlh9yxEWflSRHqVORdFuYyuGO6zpBO 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:135423 Archived-At: > etc/DEBUG suggests to evaluate (x-synchronize t). Gets me Debugger entered--Lisp error: (error "X windows are not in use or not initialized") x-synchronize(t) here. >> Apparently, the shadow calculations for the Xaw3D scroll bars, when >> done from a TTY-started server, are sometimes not digested by X11. > > Can you try figuring out why is that? I have no idea how to do that. Passing no arguments to XtCreateWidget doesn't help so IIUC the problem is somewhere in between Xaw3dComputeTopShadowRGB and XQueryColor but maybe someone has a better explanation. BTW, this behavior has been reported in bug#5802 where it says: When the lucid version, emacs does not crash, but for some reason, when I run the emacsclient frame-creating loop that I described previously, sometimes the client frame disappears as soon as it appears, and I assumed that a crash had occurred. But in this case, emacs does not crash, and I only get the problem in a loop like this. Simply running "emacsclient -c" manually over and over at the command-line never causes a frame to disappear. So, I think I will move forward using the lucid version, and you can mark this as a GTK problem. And obviously this is bug#23499 where you stated: Error code 4 is BadPixmap, according to my references. I hope some X expert will chime in and tell why this happens. (I actually don't understand why we try to create the scroll bar when the frame is iconified.) martin