RE: X11 apps failing after upgrade
So perhaps what you need to do is uninstall the dpi100 font package? Just to confirm - I removed the 100dpi fonts, and now my display is back to what it was before the recent major X update. Unfortunately, Cygwin thinks other installs are dependent on the the 100dpi fonts, so on any update I'll have to manually force it not to reinstall them, but at least things look ok again. Kind of odd, since my XP settings are 100dpi, and in reality my screen is more like 120dpi. Anyway, improvement... Thanks. James. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11 apps failing after upgrade
James Ferguson wrote: So perhaps what you need to do is uninstall the dpi100 font package? Just to confirm - I removed the 100dpi fonts, and now my display is back to what it was before the recent major X update. Unfortunately, Cygwin thinks other installs are dependent on the the 100dpi fonts, so on any update I'll have to manually force it not to reinstall them, but at least things look ok again. Hmm.. which package(s) is this? Kind of odd, since my XP settings are 100dpi, and in reality my screen is more like 120dpi. 'dpi' in the context used by XP and the X server is really just a measure of how big you'd like your fonts. Making the fonts on a screen 'actual-size' (so 72 point fonts are 1 inch high) isn't very useful (as people sit at different distances from the screen, have different visual acuities, and want to be able to read). For printed pages, of course it's different. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11 apps failing after upgrade
James Ferguson wrote: But anyway, when my Emacs fails, it does not trigger the breakpoint. My xterm gave me a BadAlloc, but the Solaris patch fixed that. My instructions were really aimed at investigating the XkbSetNamedIndicator problem, and the report that installing the Solaris patches made no difference to that. Sorry for not making that clearer. My GNU Emacs gives me: $ emacs X protocol error: BadAtom (invalid Atom parameter) on protocol request 20 Fatal error (6)Abort (core dumped) This happens almost immediately. The Emacs call stack is below. Is there another breakpoint I should try in the X server? Urk. Looking at the backtrace, the failure is occurring in XIM initialization. That looks really complex :( If you're building emacs yourself, you might try to ./configure it --without-xim to see if that makes a difference, or if it just fails in a different place. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11 apps failing after upgrade
If you use my pre-built binary you only need to have the cygwin source package installed and cygwin prep'ed, you don't need all of it's build dependencies as well. Jon, the probem is that xorg-server-1.5.3-4/build/hw/xwin/.libs does not exist because of the build failure I sent you privately. More accurately the build driectory is created but is empty. If I put the Xwin binary in the build directory will it still find all the sources? One question I should have asked: do X clients running locally (i.e. on the windows computer running the X server) work correctly or not? Except for nedit (I didn't rebuild it), all other clients (emacs, gvim, xterm) appear to work fine from the local machine. Furthermore, remote xterm clients and other X clients work fine from a remote linux machine (fedora 2.6.26.6-49.fc8) Kindest regards Richard -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: X11 apps failing after upgrade
If you're building emacs yourself, you might try to ./configure it --without-xim to see if that makes a difference, or if it just fails in a different place. That worked - Thank you... Now I can run Emacs (from the non-production Solaris machine I'm allowed to patch). Now I'm just trying to work out how to get readable fonts. The behavior seems weird. The fonts appear to be huge and they looks like a bitmap font scaled up. 10 point Courier is really quite large, and 8 point is too small. It's all very strange. Is there some dpi setting I should tweak? I tried -dpi on the XWin command but it didn't seem to have any effect. (background: My XP is at the default dpi, though I did tweak it up and back down a few months ago) I don't suppose there is any way to get the Cygwin of a couple of months ago? That just worked. This is really frustrating, but thanks for your help, without which it would be a disaster. Thanks, James. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11 apps failing after upgrade
James Ferguson wrote: If you're building emacs yourself, you might try to ./configure it --without-xim to see if that makes a difference, or if it just fails in a different place. That worked - Thank you... Now I can run Emacs (from the non-production Solaris machine I'm allowed to patch). Thanks for being the guinea pig. What is the failure mode for running emacs on an unpatched Solaris? Now I'm just trying to work out how to get readable fonts. The behavior seems weird. The fonts appear to be huge and they looks like a bitmap font scaled up. 10 point Courier is really quite large, and 8 point is too small. It's all very strange. Do you have the font-adobe-dpi75 package installed? Is there some dpi setting I should tweak? I tried -dpi on the XWin command but it didn't seem to have any effect. (background: My XP is at the default dpi, though I did tweak it up and back down a few months ago) I don't think changing the X server -dpi actually affects the DPI used for fonts (counter-intuitive perhaps, but this would generally make them look even worse) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11 apps failing after upgrade
TOY Richard wrote: Jon First problem is something to do with permissions. [EMAIL PROTECTED] /usr/src $ cygport xorg-server-1.5.3-4.cygport prep compile [...] Compiling xorg-server-1.5.3-4 autoreconf-2.63: Entering directory `.' autoreconf-2.63: configure.ac: not using Gettext autoreconf-2.63: running: aclocal --force /usr/bin/m4:configure.ac:1510: cannot create temporary file for diversion: Permission denied autom4te-2.63: /usr/bin/m4 failed with exit status: 1 aclocal-1.10: autom4te failed with exit status: 1 autoreconf-2.63: aclocal failed with exit status: 1 *** ERROR: autoreconf failed Any ideas? This is not really an area I know much about and the error message is a little cryptic. I am assuming /tmp exists and is writable Google seems to suggest that this kind of problem can be caused by antivirus software etc. (http://cygwin.com/faq/faq.using.html#faq.using.bloda) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: X11 apps failing after upgrade
What is the failure mode for running emacs on an unpatched Solaris? Same before and after the patch (the almost immediate BadAtom error). However, before the patch, when I ran an xterm it displayed, but the first keystroke made it crash with BadAlloc. After the patch, xterm appears to run fine, though I notice that the menus on ctrl-mouse don't appear correctly, they're foreshortened and only show half the first item in the menu. My .Xdefaults files are pretty much empty. I can't think what else I might have that's odd. Do you have the font-adobe-dpi75 package installed? Yeah - I installed them - indeed trying to find something which looks good to my eyes, I've installed just about every font except the Cyrillic fonts. I used to try to avoid Courier, because in some personal aesthetic I don't like it, but even that doesn't work for me now because 8pt is too small and 10pt is really large (much larger and uglier than, for instance, MS Word displays its 10pt Courier). Thanks, James. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11 apps failing after upgrade
James Ferguson wrote: What is the failure mode for running emacs on an unpatched Solaris? Same before and after the patch (the almost immediate BadAtom error). Are you sure that the stack trace points back to XCreateIC() in an emacs built --without-xim run on an unpatched Solaris? However, before the patch, when I ran an xterm it displayed, but the first keystroke made it crash with BadAlloc. After the patch, xterm appears to run fine, though I notice that the menus on ctrl-mouse don't appear correctly, they're foreshortened and only show half the first item in the menu. My .Xdefaults files are pretty much empty. I can't think what else I might have that's odd. Do you have the font-adobe-dpi75 package installed? Yeah - I installed them - indeed trying to find something which looks good to my eyes, I've installed just about every font except the Cyrillic fonts. I used to try to avoid Courier, because in some personal aesthetic I don't like it, but even that doesn't work for me now because 8pt is too small and 10pt is really large (much larger and uglier than, for instance, MS Word displays its 10pt Courier). If you have both dpi75 and dpi100 font packages installed, I think the default server fontpath lists the dpi100 font first, so that is the font which will be used. The difference between dpi75 and dpi100 font packages for any given point size on the same display is that the dpi100 font is larger. So perhaps what you need to do is uninstall the dpi100 font package? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: X11 apps failing after upgrade
Some confusion... Are you sure that the stack trace points back to XCreateIC() in an emacs built --without-xim run on an unpatched Solaris? No - built --without-xim, on a patched Solaris, it doesn't crash any more _at all_, my only problem is fonts. I'll try getting rid of the 100dpi fonts. Built with (i.e. without setting --without-xim), I was pretty sure it crashed with BadAtom from unpatched machines, as that was my original problem and I remember it was different from the xterm scenario, but now I try it, it crashes with BadAlloc. Thanks, James. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: X11 apps failing after upgrade
Hi We get all the same issues described in [1]. Furthermore, installing the Solaris patch mentioned in [2] made *NO* difference (we are using Solaris 9). Some applications half work e.g. xclearcase does not crash but keyboard inputs into some dialogue boxes are ignored. Other appications e.g. gvim emacs allow menu actions but crash at the first keyboard input. Any suggestions as to how to progress this issue further? [1] http://cygwin.com/ml/cygwin-xfree/2008-11/msg00141.html [2] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/292973 [3] https://bugzilla.redhat.com/show_bug.cgi?id=458373 Kindest regards Richard Toy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: X11 apps failing after upgrade
Yeah, I'm sorry to confirm that I installed the Solaris patch (119059-45) on one machine (Solaris 10) and while it seems to allow me to run an xterm (though I have no interest in doing so - didn't do much testing), my GNU Emacs still fails in the same way. I tried a recompilation of Emacs, in case the patch changed some statically linked library (yeah, a long shot I know), but no change. I can't run it up. Thanks, James. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Toy Sent: Thursday, December 04, 2008 9:09 AM To: cygwin-xfree@cygwin.com Subject: RE: X11 apps failing after upgrade Hi We get all the same issues described in [1]. Furthermore, installing the Solaris patch mentioned in [2] made *NO* difference (we are using Solaris 9). Some applications half work e.g. xclearcase does not crash but keyboard inputs into some dialogue boxes are ignored. Other appications e.g. gvim emacs allow menu actions but crash at the first keyboard input. Any suggestions as to how to progress this issue further? [1] http://cygwin.com/ml/cygwin-xfree/2008-11/msg00141.html [2] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/292973 [3] https://bugzilla.redhat.com/show_bug.cgi?id=458373 Kindest regards Richard Toy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11 apps failing after upgrade
Richard Toy wrote: Hi We get all the same issues described in [1]. Furthermore, installing the Solaris patch mentioned in [2] made *NO* difference (we are using Solaris 9). :-( Any suggestions as to how to progress this issue further? If you are willing to do some further investigation, it would be a great help if you could: * build the X server from source with debugging enabled (no, don't run away! the autotoolized modular server is much easier to work with the monolithic imaked monstrosity) Rebuilding the source *should* be as simple as: 1) Run cygwin setup, select cygport, the xorg-server source package; the packages for it's build-time dependencies, and devel packages corresponding to it's run-time dependencies. The dependencies for xorg-server are listed in /usr/share/doc/Cygwin/xorg-server-1.5.3.README 2) cd /usr/src/ 3) edit xorg-server-1.5.3-3.cygport to add CFLAGS=-g -O0 to the line starting 'cygconf' 4) cygport xorg-server-1.5.3-3.cygport prep compile I have made a start at updating http://x.cygwin.com/docs/cg/cygwin-x-cg.html, so you may find that helpful, but it still needs more work so don't take it as gospel. * run XWin under gdb, set a breakpoint on ProcXkbSetNamedIndicator, and tell me where and what the context is when it returns BadAlloc... 1) cd xorg-server-1.5.3-4/build/hw/xwin/.libs 2) gdb --args ./XWin.exe -multiwindow -clipboard 3) b ProcXkbSetNamedIndicator 4) run -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11 apps failing after upgrade
Jon TURNEY wrote: If you are willing to do some further investigation, it would be a great help if you could: * build the X server from source with debugging enabled (no, don't run away! the autotoolized modular server is much easier to work with the monolithic imaked monstrosity) Rebuilding the source *should* be as simple as: 1) Run cygwin setup, select cygport, the xorg-server source package; the packages for it's build-time dependencies, and devel packages corresponding to it's run-time dependencies. The dependencies for xorg-server are listed in /usr/share/doc/Cygwin/xorg-server-1.5.3.README 2) cd /usr/src/ 3) edit xorg-server-1.5.3-3.cygport to add CFLAGS=-g -O0 to the line starting 'cygconf' 4) cygport xorg-server-1.5.3-3.cygport prep compile To save you 30 minutes, here is a binary I built with debugging symbols. ftp://cygwin.com/pub/cygwinx/XWin.20081204180806.exe.bz2 You will still need to install the source package and cygport prep to have the source available for debugging, though. * run XWin under gdb, set a breakpoint on ProcXkbSetNamedIndicator, and tell me where and what the context is when it returns BadAlloc... 1) cd xorg-server-1.5.3-4/build/hw/xwin/.libs 2) gdb --args ./XWin.exe -multiwindow -clipboard 3) b ProcXkbSetNamedIndicator 4) run -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: X11 apps failing after upgrade
Thanks for the build, because I couldn't get the build to work. I double checked I'd installed everything (Cygwin installer needs command line option!). Something to do with autoconf I think: checking build system type... config.sub: missing argument Try `config.sub --help' for more information. configure: error: /bin/sh /usr/src/xorg-server-1.5.3-4/src/xorg-server-1.5.3/config.sub failed *** ERROR: configure failed But anyway, when my Emacs fails, it does not trigger the breakpoint. My xterm gave me a BadAlloc, but the Solaris patch fixed that. My GNU Emacs gives me: $ emacs X protocol error: BadAtom (invalid Atom parameter) on protocol request 20 Fatal error (6)Abort (core dumped) This happens almost immediately. The Emacs call stack is below. Is there another breakpoint I should try in the X server? Thanks, James. - (dbx) where [1] _kill(0x0, 0x6, 0x0, 0x0, 0x20, 0x0), at 0xfec46398 =[2] fatal_error_signal(sig = 6), line 398 in src/emacs.c [3] __sighndlr(0x6, 0x0, 0xffbfcf50, 0xe751c, 0x0, 0x0), at 0xfec45924 called from signal handler with signal 6 (SIGABRT) -- [4] _kill(0x0, 0x6, 0x33a801, 0x0, 0xa, 0x1), at 0xfec46398 [5] abort(), line 432 in src/emacs.c [6] check_glyph_memory(), line 2622 in src/dispnew.c [7] shut_down_emacs(sig = 0, no_x = 0, stuff = 3385345), line 2155 in src/emacs.c [8] x_connection_closed(dpy = 0x322000, error_message = 0x322000 ), line 7803 in src/xterm.c [9] x_error_quitter(display = 0x635800, error = 0xffbfd7f0), line 7877 in src/xterm.c [10] x_error_handler(display = 0x635800, error = 0xffbfd7f0), line 7833 in src/xterm.c [11] _XError(0x635800, 0xffbfd918, 0x48c384, 0x0, 0x5, 0xff060bf0), at 0xfef40bb4 [12] _XReply(0x635800, 0xffbfd918, 0x0, 0x0, 0x0, 0x20), at 0xfef20194 [13] XGetWindowProperty(0x635800, 0x80001e, 0x0, 0x0, 0x2, 0x0), at 0xfef2aff8 [14] 0xfea518dc(0x635800, 0x80001e, 0x744, 0x0, 0x3, 0x400), at 0xfea518dc [15] 0xfea51c78(0x635800, 0x80001e, 0x400, 0x400, 0x122, 0x0), at 0xfea51c78 [16] 0xfea51e4c(0x635800, 0x7c, 0x80001e, 0x0, 0x3, 0x800020), at 0xfea51e4c [17] 0xfea3c3b0(0x698400, 0x7c, 0x1, 0x1, 0x635800, 0x59d500), at 0xfea3c3b0 [18] 0xfea3cddc(0x698400, 0x0, 0x0, 0x635800, 0x3e5c00, 0xfea6bddc), at 0xfea3cddc [19] 0xfea3ceac(0x698400, 0x0, 0x2ef5c, 0x364, 0x3e5c00, 0x0), at 0xfea3ceac [20] 0xfea33014(0x698400, 0x649370, 0x1, 0x6752c0, 0xffbfdf98, 0xfea6bddc), at 0xfea33014 [21] 0xfea33940(0x698400, 0x675258, 0x0, 0xffbfdf98, 0x28c, 0xfea56dcc), at 0xfea33940 [22] 0xfea31174(0x698400, 0x675240, 0x675a80, 0x67e280, 0x3e5c00, 0xfea6bddc), at 0xfea31174 [23] 0xfea30ffc(0x3e5c00, 0x675240, 0xffbfe0d8, 0x3ae34, 0x698400, 0xfea6bddc), at 0xfea30ffc [24] XCreateIC(0x3e5c00, 0xfdc, 0x11da90, 0xc00, 0xff054000, 0xc00), at 0xfef365ec [25] create_frame_xic(f = 0x647a00), line 2307 in src/xfns.c [26] Fx_create_frame(parms = 5696389), line 2611 in src/xfns.c [27] Ffuncall(nargs = 1, args = 0x372491), line 2993 in src/eval.c [28] Fbyte_code(bytestr = 3613841, vector = 2128216, maxdepth = 1), line 679 in src/bytecode.c [29] funcall_lambda(fun = 2128148, nargs = 1, arg_vector = 0xffbfe64c), line 3180 in src/eval.c [30] Ffuncall(nargs = 1, args = 0x3f26e9), line 3050 in src/eval.c [31] Fbyte_code(bytestr = 4138729, vector = 2400240, maxdepth = 1), line 679 in src/bytecode.c [32] funcall_lambda(fun = 2400172, nargs = 1, arg_vector = 0xffbfe7ec), line 3180 in src/eval.c [33] Ffuncall(nargs = 1, args = 0x4835b1), line 3050 in src/eval.c [34] Fbyte_code(bytestr = 4732337, vector = 2398288, maxdepth = 1), line 679 in src/bytecode.c [35] funcall_lambda(fun = 2398236, nargs = 0, arg_vector = 0xffbfe98c), line 3180 in src/eval.c [36] Ffuncall(nargs = 0, args = 0x35bb01), line 3050 in src/eval.c [37] Fbyte_code(bytestr = 3521281, vector = 2152264, maxdepth = 0), line 679 in src/bytecode.c [38] funcall_lambda(fun = 2152220, nargs = 0, arg_vector = 0xffbfeb3c), line 3180 in src/eval.c [39] Ffuncall(nargs = 0, args = 0x3d8791), line 3050 in src/eval.c [40] Fbyte_code(bytestr = 4032401, vector = 2148904, maxdepth = 0), line 679 in src/bytecode.c [41] funcall_lambda(fun = 2148860, nargs = 0, arg_vector = 0xffbfec50), line 3180 in src/eval.c [42] apply_lambda(fun = 2148860, args = 3385345, eval_flag = 3331072), line 3104 in src/eval.c [43] Feval(form = 4202525), line 2384 in src/eval.c [44] internal_condition_case(bfun = 0xe9418 = top_level_2(), handlers = 3453601, hfun = 0xef9c4 = cmd_error()), line 1484 in src/eval.c [45] top_level_1(), line 1347 in src/keyboard.c [46] internal_catch(tag = 3443713, func = 0xe9430 = top_level_1(), arg = 3385345), line 1224 in src/eval.c [47] command_loop(), line 1304 in src/keyboard.c [48] recursive_edit_1(), line 1007 in src/keyboard.c [49] Frecursive_edit(), line 1068 in src/keyboard.c [50] main(argc = 1, argv = 0xffbff25c), line 1770 in src/emacs.c -- Unsubscribe info:
Re: X11 apps failing after upgrade
James Ferguson wrote: My client machine is Solaris. Everything worked fine before the update. I'm running the installed startxwin.bat startup (with xterm REM'd out). I can display xclock fine. xterm appears up, but as soon as I hit a key it crashes with: $ xterm xterm: warning, error event received: X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 136 (XKEYBOARD) Minor opcode of failed request: 16 (XkbSetNamedIndicator) Serial number of failed request: 117 Current serial number in output stream: 130 This appears to be an issue with connecting to the Cygwin/X server from X clients from older X versions running on Solaris See the thread at [1] This thread references [2] (and it can also be found at [3]), which would suggest this is not a cygwin specific issue, but seems to be something that has changed in the X.Org 1.5.x server. Those bugs reference some Solaris patches, which, as far as I can tell, upgrade X to a later version. Applying those is the only solution I know of at this time. I did some searching, but I can't find a X server patch for this issue. If you find a patch that someone else has written, please let me know! This is on my list of issues to investigate, but it is not straightforward for me to duplicate as I don't have a Solaris server to hand. [1] http://cygwin.com/ml/cygwin-xfree/2008-11/msg00141.html [2] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/292973 [3] https://bugzilla.redhat.com/show_bug.cgi?id=458373 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
