GNU bug report logs -
#7949
24.0.50; GNU Emacs with Xaw3d does not launch as X client
Previous Next
Reported by: Peter Dyballa <Peter_Dyballa <at> Freenet.DE>
Date: Mon, 31 Jan 2011 16:51:04 UTC
Severity: normal
Tags: wontfix
Found in version 24.0.50
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #50 received at 7949 <at> debbugs.gnu.org (full text, mbox):
Am 03.02.2011 um 14:47 schrieb Jan Djärv:
> 2011-02-03 11:58, Peter Dyballa skrev:
>>
>> Am 01.02.2011 um 08:20 schrieb Jan Djärv:
>>
>>> This is supposing the error handler is invoked.
>>
>>
>> Is the error handler invoked? If so, it does not seem to work.
>> Xterm or xfd
>> clearly say that the font cannot be loaded and quit. Why is GNU
>> Emacs spinning
>> around in something like an infinite loop?
>>
>> Jeremy Huddleston keeps saying:
>>
>>> Now the reason emacs is spinning is because it's not handling the
>>> error
>>> correctly. It's calling XSync() from within its x_error_handler().
>>
>
> It turns out that XtCloseDisplay also calls XSync. I removed all
> XSync from the error handler. Can you try with a frech checkout
> from trunk?
Jan,
to avoid possible misunderstandings: Since I removed (and then
corrected to iso8859-1 encoding) one X resource, all my Xaw3d X
clients of GNU Emacs launch. Only in gdb it halted with the once
modified xterm.c *while* that resource was set.
So my task is to check whether GNU Emacs launches from gdb when that
faulty resource is set? (which can be accomplished by running it with
arguments "-xrm '*synchronous: true' -xrm '*pane.menubar.font: -
linotype-optima-black-*-*-*-10-*-*-*-*-*-iso10646-1'")
--
Greetings
Pete
Never be led astray onto the path of virtue
This bug report was last modified 7 years and 168 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.