11:18 a.m.
hi, the xemacs-21.4.? generation produces the error message below (in
the xterm-window) from where we called xemacs. at the same time all
xemacs-frames turn white and most often nothing helps but kill -9 ...
any suggestions?
tomy
xemacs-21.4.5: X Error of failed request: BadIDChoice (invalid resource ID chosen for
this connection)
Major opcode of failed request: 1 (X_CreateWindow)
Resource id in failed request: 0x4000305
Serial number of failed request: 101942
Current serial number in output stream: 167282
xemacs-21.4.5: X Error of failed request: BadIDChoice (invalid resource ID chosen for
this connection)
Major opcode of failed request: 1 (X_CreateWindow)
Resource id in failed request: 0x4000306
Serial number of failed request: 101968
Current serial number in output stream: 167282
xemacs-21.4.5: X Error of failed request: BadIDChoice (invalid resource ID chosen for
this connection)
Major opcode of failed request: 1 (X_CreateWindow)
Resource id in failed request: 0x4000307
Serial number of failed request: 101991
Current serial number in output stream: 167282
xemacs-21.4.5: X Error of failed request: BadImplementation (server does not implement
operation)
Major opcode of failed request: 20 (X_GetProperty)
Serial number of failed request: 218003
Current serial number in output stream: 218003
7:23 a.m.
>>>> "Thomas" == Thomas Gerds
<gerds(a)paracelsus.fdm.uni-freiburg.de> writes:
Thomas> hi, the xemacs-21.4.? generation produces the error
Thomas> message below (in the xterm-window) from where we called
Thomas> xemacs. at the same time all xemacs-frames turn white and
Thomas> most often nothing helps but kill -9 ...
We've seen something like this before, it has not yet been
identified. I think it's mostly been on exit, though. What context,
are you usually doing a particular kind of thing or does it seem
totally random?
Please send your Installation file, and any details about platform
that might be significant (eg, OpenMotif vs. platform Motif) that are
not evident from Installation.
If you can get XEmacs running at all, and you have a recent version of
the net-utils package, M-x report-xemacs-bug RET is the recommended
way to submit bug reports, as it will give all that data
automatically, as well as a lot of information about context (such as
your packages and recent keystrokes).
Thomas> xemacs-21.4.5: X Error of failed request: BadIDChoice (invalid resource
ID chosen for this connection)
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.
1:26 p.m.
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
We've seen something like this before, it has not yet been
identified. I think it's mostly been on exit, though. What context,
are you usually doing a particular kind of thing or does it seem
totally random?
indeed, it seems not to be connected to a particular command ... at
least i cant force the problem to turn up.
Please send your Installation file, and any details about platform
that might be significant (eg, OpenMotif vs. platform Motif) that
are not evident from Installation.
it is sparc-sun-solaris2.8 and uname -a gives
SunOS zion.fdm.uni-freiburg.de 5.8 Generic_108528-05 sun4u sparc SUNW,Ultra-5_10
and here is the relevant part from the installation file:
##
##
## xemacs-21.4.5
##
##
umask 002
##
mkdir /usr/local/lib/xemacs-21.4.5
##
cd /tmp
gzip -cd /h/sc/downloads/xemacs/xemacs-21.4.5.tar.gz | tar xvf -
gzip -cd /h/sc/downloads/xemacs/xemacs-21.4.5-elc.tar.gz | tar xvf -
gzip -cd /h/sc/downloads/xemacs/xemacs-21.4.5-info.tar.gz | tar xvf -
##
cd xemacs-21.4.5
./configure \
--cflags='-O2' \
--dynamic=yes \
--site-includes=/usr/local/include/X11 \
--site-libraries=/usr/local/lib/X11 \
--package-path=/usr/local/lib/xemacs/xemacs-packages
## --cflags='-O2 -mcpu=v8' \
##
make
make install
make gzip-el
##
cd /usr/local
chgrp -R staff bin/xemacs-21.4.5
chmod -R g+w bin/xemacs-21.4.5
##
rm -rf /tmp/xemacs-21.4.5
cd /usr/local/lib/xemacs-21.4.5/lisp
ln -s /h/sc/xemacs/site-start.el
##
##
##
## xemacs-sumo-2001-07-09
##
##
umask 002
##
cd /usr/local/lib/xemacs
rm -rf xemacs-packages-old
mv xemacs-packages xemacs-packages-old
##
zcat /h/sc/downloads/xemacs/xemacs-sumo-2001-07-09.tar.gz | tar xf -
##
cd xemacs-packages/lisp/auctex
rm tex-site.el
ln -s /h/sc/xemacs/tex-site.el
ln -s /h/sc/xemacs/auctex/style
##
If you can get XEmacs running at all, and you have a recent version
of the net-utils package, M-x report-xemacs-bug RET is the
recommended way to submit bug reports, as it will give all that data
automatically, as well as a lot of information about context (such
as your packages and recent keystrokes).
i will send a proper bug-report as soon as the problem turns up again ...
thank you very much,
tomy
--
Signature for mail groups
12:03 a.m.
=> On Nov 1, 2001, Stephen J Turnbull(S) wrote:
>>>>> "Thomas" == Thomas Gerds
<gerds(a)paracelsus.fdm.uni-freiburg.de> writes:
Thomas> hi, the
xemacs-21.4.? generation produces the error
Thomas> message below (in the xterm-window) from where we called
Thomas> xemacs. at the same time all xemacs-frames turn white and
Thomas> most often nothing helps but kill -9 ...
S> We've seen something like this before, it has not yet been
S> identified. I think it's mostly been on exit, though. What context,
S> are you usually doing a particular kind of thing or does it seem
S> totally random?
There are numerous report on this error for XEmacs on Solaris and
AIX(?). It usually occurs after XEmacs is being used for some time(a
few days), but it almost happens every time on frame re-painting. This
bug has not been tracked down.
Tony
1:04 a.m.
Tony Lam <Tony.W.Lam(a)Sun.Com> wrote:
There are numerous report on this error for XEmacs on Solaris and
AIX(?). It usually occurs after XEmacs is being used for some time(a
few days), but it almost happens every time on frame re-painting. This
bug has not been tracked down.
As far as I can tell, *ANY* X error will cause XEmacs to lock up.
It doesn't seem to matter which one -- once one occurs, XEmacs is dead.
--
Darryl Okahata
darrylo(a)soco.agilent.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.
8:32 a.m.
Darryl Okahata <darrylo(a)soco.agilent.com> writes:
Tony Lam <Tony.W.Lam(a)Sun.Com> wrote:
> There are numerous report on this error for XEmacs on Solaris and
> AIX(?). It usually occurs after XEmacs is being used for some time(a
> few days), but it almost happens every time on frame re-painting. This
> bug has not been tracked down.
As far as I can tell, *ANY* X error will cause XEmacs to lock up.
It doesn't seem to matter which one -- once one occurs, XEmacs is dead.
ok, thanks to all of you. i will beware of forcing frame re-paintings
in the future :) and shorten the auto-save interval ...
tomy
--
Signature for mail groups
5:38 p.m.
Thomas Gerds <gerds(a)paracelsus.fdm.uni-freiburg.de> wrote:
ok, thanks to all of you. i will beware of forcing frame
re-paintings
in the future :) and shorten the auto-save interval ...
You shouldn't have to shorten the auto-save interval. If XEmacs
"locks up", you can usually recover the data by sending it a SIGHUP --
this should cause XEmacs to auto-save everything, and then exit.
--
Darryl Okahata
darrylo(a)soco.agilent.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.
8213
days inactive
8219
days old
6 comments
4 participants
participants (4)
-
Darryl Okahata -
Stephen J. Turnbull -
Thomas Gerds -
Tony Lam