From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.bugs Subject: bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55 Date: Wed, 2 Aug 2017 22:31:58 +0300 Message-ID: <20170802193158.GB30834@protected.rcdrun.com> 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> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1501702398 21296 195.159.176.226 (2 Aug 2017 19:33:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 2 Aug 2017 19:33:18 +0000 (UTC) Cc: 27816@debbugs.gnu.org, Jean Louis To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Aug 02 21:33:12 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 1dczOG-00056N-HA for geb-bug-gnu-emacs@m.gmane.org; Wed, 02 Aug 2017 21:33:08 +0200 Original-Received: from localhost ([::1]:49935 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dczOM-0007eN-MR for geb-bug-gnu-emacs@m.gmane.org; Wed, 02 Aug 2017 15:33:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:32770) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dczOD-0007dn-Jc for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 15:33:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dczOA-00019e-Tj for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 15:33:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:36147) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dczOA-00019K-Of for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 15:33:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dczOA-0007Zm-6p for bug-gnu-emacs@gnu.org; Wed, 02 Aug 2017 15:33:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Jean Louis Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 02 Aug 2017 19:33: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.150170233529066 (code B ref 27816); Wed, 02 Aug 2017 19:33:02 +0000 Original-Received: (at 27816) by debbugs.gnu.org; 2 Aug 2017 19:32:15 +0000 Original-Received: from localhost ([127.0.0.1]:38823 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dczNO-0007Yj-VC for submit@debbugs.gnu.org; Wed, 02 Aug 2017 15:32:15 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:49384) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dczNM-0007YV-64 for 27816@debbugs.gnu.org; Wed, 02 Aug 2017 15:32:12 -0400 Original-Received: from protected.rcdrun.com (localhost [::1]) (AUTH: PLAIN securesender, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by stw1.rcdrun.com with ESMTPSA; Wed, 02 Aug 2017 12:32:06 -0700 id 0000000000092684.00000000598228B7.00006270 Original-Received: from localhost (localhost [127.0.0.1]) (uid 1001) by protected.rcdrun.com with local; Wed, 02 Aug 2017 22:31:58 +0300 id 00000000000EE192.00000000598228AE.00007A50 Content-Disposition: inline In-Reply-To: <838tj1ztum.fsf@gnu.org> 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:135250 Archived-At: Dear Eli, Thank you so far. See below my answers. On Wed, Aug 02, 2017 at 09:51:13PM +0300, Eli Zaretskii wrote: > > ./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 will try changing the lucid to gtk kit to see if it is happening again. > > 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. 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. > What if you invoke emacsclient from the shell > prompt -- does the problem happen if you invoke > it several times in a row? Exactly like that, it happens if I invoke it from terminal. Also if I invoke it directly on keypress from Window Manager or through mutt. > Also, are you sure the version of emacsclient > that is invoked belongs to the version of Emacs > which is run in the daemon mode? Yes, very sure. I am running emacs-repository-version "cf1da46761675f1886e54765fa213c7bd7d93437" And emacs is then in /package/text/emacs/ and emacs client is then linked to the version I am running: admin-> ls -l /usr/bin/emacsclient lrwxrwxrwx 1 root root 40 Aug 2 18:55 /usr/bin/emacsclient -> ../../package/text/emacs/bin/emacsclient and because it is in /package/text/emacs/ it belongs to same version. > 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? You mean if I run emacs without daemon? There is no problem at all. But due to loading times, and configuration, it is not usable. > > emacsclient is basically remaining in memory as process, but the frame > > is disappearing. > > So Emacs now runs without any frames displayed? Emacs runs all the time, as main program under screen, I can access it through screen. The problem is also happening when I do not run it under screen, I can run it as user. If there is no GUI frame, and I wish to invoke it by emacsclient, each few times, the instance failes, GUI frame disappears, but the emacsclient still runs in memory, until I kill it. > > 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. I do not have dsitribution and did not update system in any manner, neither touched X Window or similar. I have updated security certificates, just nothing special on the system. Jean