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
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
> 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
> 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
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
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: Installed CygwinX and xhost not found
Lots of apps have moved into their own packages. xhost can be found in the X11 group, to be installed on its own. However, it's generally a good option to connect to your client with "ssh -Y" and then you can display directly, without using xhost. I have a Cygwin-X menu item, with "XWin server" option in it. I think that's a default install... It runs /usr/bin/startxwin.bat (which was created/installed automatically). If you don't have that it must have been one of the X11 items I selected - not sure which. HTH, James. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of RICHARD RASO Sent: Tuesday, December 02, 2008 1:03 PM To: cygwin-xfree@cygwin.com Subject: Installed CygwinX and xhost not found Hi, I have just installed CygwinX on my new laptop which is running MS XP Pro version 2002 service pack 2. I used install options All User and Unix mode. I also took the default of downloading all packages. I am trying to setup a X window environment so I can run the Oracle Universal Installer to load Oracle onto my zOS mainframe environment. The first time I started Cygwin from the desktop short cut, I issue the command xhost + , I then received the error message 'bash: xhost not found'. So I have searched the FAQs and found a note that says to add a path statement to correct this problem. Next, I remembered the installation said I could customize the C:\cygwin\home\rraso\.bash_profile by adding this statement PATH="/usr/local/bin:/usr/bin:/bin:$PATH".So I customized the profile and retried the shortcut, followed by xhost +, same resulting error message. After removing the change, I tried inserting the path statement into the Cygwin.BAT file, both before the change directory command and after the bash logon command. Both tests produced the same results 'xhost + not found'. Next, I reinstalled the software but I installed the CygwinX support. I checked the CygwinX documentation and in chapter 4, it talks about starting CygwinX with either startwxin.bat, or startxwin.sh or startx. I have searched my Cygwin files for this members and do not find them. I was expecting to find one or more of them. Do I create a startxwin file? If not, did my installation not work correctly? So at this point, I am not sure where to insert the path statement or even if I have the right statement to insert into someplace the Cygwin files. Any suggestion will be greatly appreciated. -- 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/
X11 apps failing after upgrade
All help gratefully received! I haven't found this problem through searches, apologies if I've been searching for the wrong terms. In my first update in a few months I picked up the major upgrade to the X server. XWin -version now reports 1.5.3.0. After having the problems below I did a full reinstall of Cygwin, with no success. My symptoms look similar to tunneling via `ssh -X`, but it happens with both `ssh -Y`, and when I do `xhost +` and display directly to :0 without ssh tunneling. 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 During which, my /var/log/XWin.0.log gets 8 lines of: GetWindowProp - pWin or name was NULL I can't run GNU Emacs at all (self-built Emacs 22.3.1 on the client Solaris machine, but I also tried 21.3.1 installed from sunfreeware.com, same result): $ emacs X protocol error: BadAtom (invalid Atom parameter) on protocol request 20 Fatal error (6)Abort (core dumped) Nothing in /var/win/Xwin.0.log on that failure though. I /can/ run the local, Cygwin-installed GNU Emacs - kicked it off via the X server system-tray menu. Any suggestions gratefully received, including what other info I can supply or what diagnostics can I run? Since it seems nobody else is screaming about this suggests it's something about my setup, but I can't think what. On the plus side, I've now fixed my Emacs configuration to work better in the terminal :). Thanks in advance, 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/
