GNU bug report logs - #3877
23.1.50; X protocol error: BadDrawable (invalid Pixmap or Window parameter) on protocol request 53

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 3877 in the body.
You can then email your comments to 3877 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Peter Dyballa <Peter_Dyballa <at> Freenet.DE>
To: emacs-pretest-bug <at> gnu.org
Subject: 23.1.50; X protocol error: BadDrawable (invalid Pixmap or Window parameter) on protocol request 53
Date: Sat, 18 Jul 2009 16:15:16 +0200

Hello!

I tried to debug a problem with xkill and opened emacs/src directory  
in dired. Then I clicked with the mouse cursor on emacs-23.1.50.1  
file – GNU Emacs crashed at once with the error message cited in the  
subject.

I can repeat it always. (Before I can debug I need an executable with  
debug information.)


In GNU Emacs 23.1.50.1 (powerpc-apple-darwin8.11.0, X toolkit, Xaw3d  
scroll bars)
 of 2009-07-18 on Latsche.local
Windowing system distributor `The XFree86 Project, Inc', version  
11.0.40400000
configured using `configure  '--without-sound' '--without-pop' '-- 
with-dbus' '--with-libotf' '--with-x-toolkit=athena' '--x-includes=/ 
usr/X11R6/include' '--x-libraries=/usr/X11R6/lib' '--enable- 
locallisppath=/Library/Application Support/Emacs/calendar23:/Library/ 
Application Support/Emacs' 'CFLAGS=-Wno-pointer-sign -H -pipe -fPIC - 
mcpu=7450 -mtune=7450 -fast -mpim-altivec -ftree-vectorize -foptimize- 
register-move -freorder-blocks -freorder-blocks-and-partition - 
fthread-jumps -fpeephole -fno-crossjumping' 'LDFLAGS=-dead_strip - 
multiply_defined suppress' 'CPPFLAGS=-no-cpp-precomp -I/usr/include/ 
openssl -I/sw/include/pango-1.0 -I/sw/lib/fontconfig2/include -I/usr/ 
local/include -I/sw/include''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: de_DE.UTF-8
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: de_DE.UTF-8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default-enable-multibyte-characters: t

Major mode: Dired by name

Minor modes in effect:
  show-paren-mode: t
  display-time-mode: t
  tooltip-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
C-x d <return> C-s e m a c s - <return> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <menu-bar>
<help-menu> <send-emacs-bug-report>

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Loading iso-transl...done
Loading time...done
Loading paren...done
Mark saved where search started


--
Greetings

  Pete

There's something the technicians need to learn from the artists. If  
it isn't aesthetically pleasing, it's probably wrong.

Message #10 received at 3877 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Peter Dyballa <Peter_Dyballa <at> Freenet.DE>
To: 3877 <at> debbugs.gnu.org
Subject: Bug probably solved
Date: Mon, 27 Jul 2009 21:05:53 +0200

Hello!

It looks as if the cause lies in incompatible versions (of  
libraries), most probably Xft2, and here C header and PC files. I'll  
retry a build later tonight with the updated extra files removed.

--
Greetings

  Pete

Programming today is a race between software engineers striving to  
build bigger and better idiot-proof programs, and the Universe trying  
to produce bigger and better idiots. So far, the Universe is winning.
				– Rich Cook

Message #15 received at 3877 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: Peter Dyballa <Peter_Dyballa <at> Freenet.DE>
Cc: 3877 <at> debbugs.gnu.org
Subject: Re: Bug probably solved
Date: Sat, 15 Aug 2009 19:08:16 -0400

> It looks as if the cause lies in incompatible versions (of  
> libraries), most probably Xft2, and here C header and PC files. I'll  
> retry a build later tonight with the updated extra files removed.

Hi Peter,

Was this resolved?

Message #20 received at 3877 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Peter Dyballa <Peter_Dyballa <at> Freenet.DE>
To: Chong Yidong <cyd <at> stupidchicken.com>
Cc: 3877 <at> debbugs.gnu.org
Subject: Re: Bug probably solved
Date: Sun, 16 Aug 2009 01:30:06 +0200

Am 16.08.2009 um 01:08 schrieb Chong Yidong:

>> It looks as if the cause lies in incompatible versions (of
>> libraries), most probably Xft2, and here C header and PC files. I'll
>> retry a build later tonight with the updated extra files removed.
>
> Hi Peter,
>
> Was this resolved?


No, not really. I'd have to change some statements in the Makefiles  
to make ld bind the binaries to particular libraries (most probably  
statically) and haven't yet used my spare-time to investigate on this  
topic, copy good examples from other software. Besides, maybe I am  
the last one who tries to compile up-to-date software on an old set  
of soft- and PPC hardware. Apple's Tiger, Mac OS X 10.4(.11), is now  
four or five years old, the 'recent' Mac OS X 10.5.x, Leopard, is  
going to be superseded by Snow Leopard, Mac OS X 10.6, any day now...

Since I am sure that this is the reality (not a 'buggy' software from  
GNU/FSF) I am a bit reluctant and rather pay attention to not xkill  
GNU Emacs.

--
Greetings

  Pete

Clovis' Consideration of an Atmospheric Anomaly:
        The perversity of nature is nowhere better demonstrated
        than by the fact that, when exposed to the same atmosphere,
        bread becomes hard while crackers become soft.

Message #25 received at 3877 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Peter Dyballa <Peter_Dyballa <at> Freenet.DE>
To: Chong Yidong <cyd <at> stupidchicken.com>
Cc: 3877 <at> debbugs.gnu.org
Subject: Re: Bug probably solved
Date: Thu, 10 Sep 2009 23:17:15 +0200

Am 16.08.2009 um 01:08 schrieb Chong Yidong:

>> It looks as if the cause lies in incompatible versions (of
>> libraries), most probably Xft2, and here C header and PC files. I'll
>> retry a build later tonight with the updated extra files removed.
>
> Hi Peter,
>
> Was this resolved?


I think it is not. I build GNU Emacs 23.1.50 now, a few days, with  
GTK and need some more xkills. Before, with Xaw3d, sporadically cores  
were built upon xkill. Both variants of the X client are built with  
shared libraries from MacPorts (plus some inevitable ones from the  
system), which all are, supposedly, fitting each-other. When both  
variants act so differently than one has to have something like a  
bug, related to libXaw3d or libXt or libXmu presumingly, which the  
Athena 3D variant uses.

(The next ten or such days I'll presumingly be on holidays.)

--
Greetings

  Pete

We have to expect it, otherwise we would be surprised.

Message #30 received at 3877 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: Peter Dyballa <Peter_Dyballa <at> Freenet.DE>
Cc: 3877 <at> debbugs.gnu.org
Subject: Re: bug#3877: X protocol error: BadDrawable
Date: Sun, 10 Jul 2011 22:41:56 -0400

Do you still see this with the latest version?
If so, we need a backtrace from a build with debugging information in
order to be able to do anything.

Message #33 received at 3877 <at> debbugs.gnu.org (full text, mbox):

From: Peter Dyballa <Peter_Dyballa <at> Freenet.DE>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 3877 <at> debbugs.gnu.org
Subject: Re: bug#3877: X protocol error: BadDrawable
Date: Mon, 11 Jul 2011 09:59:03 +0200

Am 11.07.2011 um 04:41 schrieb Glenn Morris:

>
> Do you still see this with the latest version?
> If so, we need a backtrace from a build with debugging information in
> order to be able to do anything.


I tried to repeat what I was doing two years ago. So many things  
obviously have changed, so no X protocol error happens anymore. I'd  
like to try one more thing, compile with the complete set of m17n  
libraries and libraries from the Fink package manager.

--
Greetings

  Pete

Journalism is printing what someone else does not want printed;  
everything else is public relations.
			– George Orwell

Message #36 received at 3877 <at> debbugs.gnu.org (full text, mbox):

From: Peter Dyballa <Peter_Dyballa <at> Freenet.DE>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 3877 <at> debbugs.gnu.org
Subject: Re: bug#3877: X protocol error: BadDrawable
Date: Tue, 12 Jul 2011 00:16:33 +0200

Am 11.07.2011 um 04:41 schrieb Glenn Morris:

>
> Do you still see this with the latest version?
> If so, we need a backtrace from a build with debugging information in
> order to be able to do anything.


The GNU Emacs I've built with libm17n support from the Fink package  
manager too behaves OK. Maybe it was indeed due to the exotic  
combination of slightly incompatible libraries.

I think this old bug report can be closed!

--
Greetings

  Pete

Government is actually the worst failure of civilized man. There has  
never been a really good one, and even those that are most tolerable  
are arbitrary, cruel, grasping and unintelligent.
				– H. L. Mencken

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.