From seelybs at gmail.com Tue Mar 15 09:35:56 2011 From: seelybs at gmail.com (Bruce Seely) Date: Tue, 15 Mar 2011 05:35:56 -0400 Subject: [mcclim-devel] Problem starting McClim Message-ID: <4D7F32FC.1000206@gmail.com> Hi All, I would like to use mcclim. I've loaded it (along with clx, flexichains, and spacial-trees), and get this error when I try to start the demo: CL-USER(15): (clim-demo::run-test 'clim-demo::demodemo) ; Autoloading for ACL-SOCKET:CONFIGURE-DNS: ; Fast loading from bundle code/acldns.fasl. Error: "Connection timed out" (errno 60) occurred while creating a local socket and connecting to a remote host "tmp/launch-4lQnm8/org.x" (67.215.65.132) on port 6000. [condition type: SOCKET-ERROR] I suspect that it's a problem with the configuration issue with my mac, and not a mcclim problem, but I'm stuck. Is someone might be able to tell me what I'm doing wrong. I'm using a Macbook Pro running Snow Leopard in 64-bit mode, running Franz Allegro Common Lisp, version 82 (acl8264). Do I need to do something about enabling sockets, or something like that? Is there any more information that would be helpful in explaining the problem? Thank you very much for your help. Bruce From rm at tuxteam.de Tue Mar 15 10:03:17 2011 From: rm at tuxteam.de (rm at tuxteam.de) Date: Tue, 15 Mar 2011 11:03:17 +0100 Subject: [mcclim-devel] Problem starting McClim In-Reply-To: <4D7F32FC.1000206@gmail.com> References: <4D7F32FC.1000206@gmail.com> Message-ID: <20110315100317.GA4637@seid-online.de> On Tue, Mar 15, 2011 at 05:35:56AM -0400, Bruce Seely wrote: > Hi All, > > I would like to use mcclim. I've loaded it (along with clx, flexichains, > and spacial-trees), and get this error when I try to start the demo: > > CL-USER(15): (clim-demo::run-test 'clim-demo::demodemo) > ; Autoloading for ACL-SOCKET:CONFIGURE-DNS: > ; Fast loading from bundle code/acldns.fasl. > Error: "Connection timed out" (errno 60) occurred while > creating a local socket and connecting to a remote host > "tmp/launch-4lQnm8/org.x" (67.215.65.132) on port 6000. > [condition type: SOCKET-ERROR] > > > I suspect that it's a problem with the configuration issue with my mac, > and not a mcclim problem, but I'm stuck. Is someone might be able to > tell me what I'm doing wrong. > > I'm using a Macbook Pro running Snow Leopard in 64-bit mode, running > Franz Allegro Common Lisp, version 82 (acl8264). Do I need to do > something about enabling sockets, or something like that? This looks more like an X11 error than a problem with McClim. Does your X server run and is it accepting connections ? HTH Ralf Mattes > Is there any more information that would be helpful in explaining the > problem? > > Thank you very much for your help. > Bruce > > _______________________________________________ > mcclim-devel mailing list > mcclim-devel at common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel From seelybs at gmail.com Tue Mar 15 10:13:44 2011 From: seelybs at gmail.com (Bruce Seely) Date: Tue, 15 Mar 2011 06:13:44 -0400 Subject: [mcclim-devel] Problem starting McClim In-Reply-To: <20110315100317.GA4637@seid-online.de> References: <4D7F32FC.1000206@gmail.com> <20110315100317.GA4637@seid-online.de> Message-ID: <4D7F3BD8.7090209@gmail.com> On 3/15/11 6:03 AM, rm at tuxteam.de wrote: > On Tue, Mar 15, 2011 at 05:35:56AM -0400, Bruce Seely wrote: >> Hi All, >> >> I would like to use mcclim. I've loaded it (along with clx, flexichains, >> and spacial-trees), and get this error when I try to start the demo: >> >> CL-USER(15): (clim-demo::run-test 'clim-demo::demodemo) >> ; Autoloading for ACL-SOCKET:CONFIGURE-DNS: >> ; Fast loading from bundle code/acldns.fasl. >> Error: "Connection timed out" (errno 60) occurred while >> creating a local socket and connecting to a remote host >> "tmp/launch-4lQnm8/org.x" (67.215.65.132) on port 6000. >> [condition type: SOCKET-ERROR] >> >> >> I suspect that it's a problem with the configuration issue with my mac, >> and not a mcclim problem, but I'm stuck. Is someone might be able to >> tell me what I'm doing wrong. >> >> I'm using a Macbook Pro running Snow Leopard in 64-bit mode, running >> Franz Allegro Common Lisp, version 82 (acl8264). Do I need to do >> something about enabling sockets, or something like that? > This looks more like an X11 error than a problem with McClim. > Does your X server run and is it accepting connections ? > > HTH Ralf Mattes Please forgive me for my lack of knowledge re: X11. I don't know how to check directly, but the xterm app works, so I'm assuming that X11 is running. > >> Is there any more information that would be helpful in explaining the >> problem? >> >> Thank you very much for your help. >> Bruce >> >> _______________________________________________ >> mcclim-devel mailing list >> mcclim-devel at common-lisp.net >> http://common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel From rpgoldman at sift.info Tue Mar 15 13:44:21 2011 From: rpgoldman at sift.info (Robert Goldman) Date: Tue, 15 Mar 2011 08:44:21 -0500 Subject: [mcclim-devel] Problem starting McClim In-Reply-To: <4D7F3BD8.7090209@gmail.com> References: <4D7F32FC.1000206@gmail.com> <20110315100317.GA4637@seid-online.de> <4D7F3BD8.7090209@gmail.com> Message-ID: <4D7F6D35.5090903@sift.info> X-TagToolbar-Keys: D20110315084421903 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I have seen problems like this before. I believe it is caused by disagreements between ACL and the CLX back-end of McCLIM about what form of authentication to use against your X server. Here's a suggestion: try pulling down the ACL mirror of portable CLX, from the Franz Open Source site, and use that instead of the CLX that shipped with ACL. That /may/ fix things --- I believe it supports more different flavors of authentication. Another alternative is that this may involve Mac OS X's way of starting up X. I have a vague memory that it somehow opens a socket or specially named virtual file or something, and that by opening that socket the X11 server automagically starts. IIRC, that was also a place where I had to tweak my set up to get McCLIM to run. I'm afraid this is all 2 years + old, so it's a bit vague. I haven't run McCLIM in quite a while now. Hope that helps. r From mikemac at mikemac.com Wed Mar 16 03:39:05 2011 From: mikemac at mikemac.com (Michael McDonald) Date: Tue, 15 Mar 2011 22:39:05 -0500 Subject: [mcclim-devel] Problem starting McClim In-Reply-To: <4D7F32FC.1000206@gmail.com> References: <4D7F32FC.1000206@gmail.com> Message-ID: On Mar 15, 2011, at 4:35 AM, Bruce Seely wrote: > Hi All, > > I would like to use mcclim. I've loaded it (along with clx, flexichains, > and spacial-trees), and get this error when I try to start the demo: > > CL-USER(15): (clim-demo::run-test 'clim-demo::demodemo) > ; Autoloading for ACL-SOCKET:CONFIGURE-DNS: > ; Fast loading from bundle code/acldns.fasl. > Error: "Connection timed out" (errno 60) occurred while > creating a local socket and connecting to a remote host > "tmp/launch-4lQnm8/org.x" (67.215.65.132) on port 6000. > [condition type: SOCKET-ERROR] Your DISPLAY environment variable isn't set up correctly. It's caused by the retards at Apple breaking 20 years of X compatibility so they can be "innovative". It needs to be something like ":0.0", not "tmp/launch-4lQnm8/org.x". I start X11 up directly (despite the retards saying you just have to run an X application). I get two xterm, one has the bogus DISPLAY and one has the real one. I kill the bogus one and then use the real one from then on. So, in the "Login Items" under "System Preferences" -> "Accounts", I have /Applications/Utilities/X11.app and in my home directory I have my .xinitrc file: #!/bin/sh TERM=xterm export TERM PATH=/Users/mikemac/bin:/usr/X11R6/bin:/usr/bsd:/usr/bin:/bin:/usr/sbin:/sbin export PATH xhost + xterm -geometry +0+0& quartz-wm Mike McDonald mikemac at mikemac.com From rudi at constantly.at Wed Mar 16 10:08:12 2011 From: rudi at constantly.at (Rudi Schlatte) Date: Wed, 16 Mar 2011 11:08:12 +0100 Subject: [mcclim-devel] Problem starting McClim In-Reply-To: References: <4D7F32FC.1000206@gmail.com> Message-ID: <1CBA338F-F0BA-4F08-AA2D-E474A1313A3C@constantly.at> On Mar 16, 2011, at 4:39 , Michael McDonald wrote: > > > > On Mar 15, 2011, at 4:35 AM, Bruce Seely wrote: > >> Hi All, >> >> I would like to use mcclim. I've loaded it (along with clx, flexichains, >> and spacial-trees), and get this error when I try to start the demo: >> >> CL-USER(15): (clim-demo::run-test 'clim-demo::demodemo) >> ; Autoloading for ACL-SOCKET:CONFIGURE-DNS: >> ; Fast loading from bundle code/acldns.fasl. >> Error: "Connection timed out" (errno 60) occurred while >> creating a local socket and connecting to a remote host >> "tmp/launch-4lQnm8/org.x" (67.215.65.132) on port 6000. >> [condition type: SOCKET-ERROR] > > Your DISPLAY environment variable isn't set up correctly. It's caused by the retards at Apple breaking 20 years of X compatibility so they can be "innovative". It needs to be something like ":0.0", not "tmp/launch-4lQnm8/org.x". It's easy and fun to blame apple, but it's a bit more complicated. Marvel at clx's dependent.lisp: get-default-display parses the DISPLAY variable, returning protocol, hostname etc. (this is where the new, Apple-specific value would have to be considered in a sane world, mirroring what has been implemented in xlib - and yes, translating ":0.0" into "/tmp/.X11-unix/X", as is the practice on *nix, is a hack as well). Then, be amused at open-x-stream where the value for protocol calculated by get-default-display end up being subsequently ignored, superseded by another round of heuristics in unix-socket-path-from-host (found in depdefs.lisp). And there, indeed, /tmp/launchfoo values for the DISPLAY variable is considered if *features* contains :darwin (the leading slash is cut off by a previous round of parsing somewhere else). But clx code layout is deep and twisted, and I think ACL (which Bruce's backtrace indicates he's using) has different code paths; the fix might not have been applied there yet. It should not be difficult to patch once the right location is found. FWIW, I do blame Apple for putting the listening unix domain socket for X at /tmp/launcbarblaa instead of /tmp/.X11-unix/X - in that case, things would have continued Just Working because clx's heuristics would have accidentally done the right thing. > I start X11 up directly (despite the retards saying you just have to run an X application). I get two xterm, one has the bogus DISPLAY and one has the real one. I kill the bogus one and then use the real one from then on. An X application that connects to the local socket pointed to by DISPLAY will start up the X server. > xhost + You forgot to advise Bruce about the consequences of this. Rudi From mikemac at mikemac.com Wed Mar 16 14:21:48 2011 From: mikemac at mikemac.com (Michael McDonald) Date: Wed, 16 Mar 2011 09:21:48 -0500 Subject: [mcclim-devel] Problem starting McClim In-Reply-To: <1CBA338F-F0BA-4F08-AA2D-E474A1313A3C@constantly.at> References: <4D7F32FC.1000206@gmail.com> <1CBA338F-F0BA-4F08-AA2D-E474A1313A3C@constantly.at> Message-ID: <550FC6D4-E59C-4F3A-BDBB-5087CE37A1D1@mikemac.com> On Mar 16, 2011, at 5:08 AM, Rudi Schlatte wrote: > > On Mar 16, 2011, at 4:39 , Michael McDonald wrote: > >> >> >> >> On Mar 15, 2011, at 4:35 AM, Bruce Seely wrote: >> >>> Hi All, >>> >>> I would like to use mcclim. >> >> Your DISPLAY environment variable isn't set up correctly. It's caused by the retards at Apple breaking 20 years of X compatibility so they can be "innovative". It needs to be something like ":0.0", not "tmp/launch-4lQnm8/org.x". > > > FWIW, I do blame Apple for putting the listening unix domain socket for X at /tmp/launcbarblaa instead of /tmp/.X11-unix/X - in that case, things would have continued Just Working because clx's heuristics would have accidentally done the right thing. > So, they did break "20 years of X compatibility" then? And they had time to do this "innovation" but couldn't fix the "yellow cursor" problem for years? and then they broke drawing of Xaw borders in 10.6? Sorry, that puts them in the retard category in my book. > >> xhost + > > You forgot to advise Bruce about the consequences of this. That's because I wasn't doing a complete tutorial on X, network security and personnel policy (mine's "If you abuse my X display or any other trust I place in you, I'll fire your sorry *** on the spot!"), I was just trying to get him pointed in a direction where he could get CLIM working. And just for the record, I don't actually do 'xhost +' but since none of you have any need to know the names of my trusted internal machines and since I can't come down the hall and fire you if need be, I simplified the .xinitrc file. And I hope Bruce already knows he should investigate and think about all advice he gets from the net, not just blindly follow what any group of yahoos tells him to do. Mike McDonald mikemac at mikemac.com From seelybs at gmail.com Wed Mar 16 14:29:01 2011 From: seelybs at gmail.com (Bruce Seely) Date: Wed, 16 Mar 2011 10:29:01 -0400 Subject: [mcclim-devel] Problem starting McClim In-Reply-To: <550FC6D4-E59C-4F3A-BDBB-5087CE37A1D1@mikemac.com> References: <4D7F32FC.1000206@gmail.com> <1CBA338F-F0BA-4F08-AA2D-E474A1313A3C@constantly.at> <550FC6D4-E59C-4F3A-BDBB-5087CE37A1D1@mikemac.com> Message-ID: <4D80C92D.4000704@gmail.com> Thank you very much for your responses! I haven't had time to make the changes, but will let you know how it goes. Bruce On 3/16/11 10:21 AM, Michael McDonald wrote: > On Mar 16, 2011, at 5:08 AM, Rudi Schlatte wrote: > >> On Mar 16, 2011, at 4:39 , Michael McDonald wrote: >> >>> >>> >>> On Mar 15, 2011, at 4:35 AM, Bruce Seely wrote: >>> >>>> Hi All, >>>> >>>> I would like to use mcclim. >>> Your DISPLAY environment variable isn't set up correctly. It's caused by the retards at Apple breaking 20 years of X compatibility so they can be "innovative". It needs to be something like ":0.0", not "tmp/launch-4lQnm8/org.x". >> >> FWIW, I do blame Apple for putting the listening unix domain socket for X at /tmp/launcbarblaa instead of /tmp/.X11-unix/X - in that case, things would have continued Just Working because clx's heuristics would have accidentally done the right thing. >> > So, they did break "20 years of X compatibility" then? And they had time to do this "innovation" but couldn't fix the "yellow cursor" problem for years? and then they broke drawing of Xaw borders in 10.6? Sorry, that puts them in the retard category in my book. > >>> xhost + >> You forgot to advise Bruce about the consequences of this. > That's because I wasn't doing a complete tutorial on X, network security and personnel policy (mine's "If you abuse my X display or any other trust I place in you, I'll fire your sorry *** on the spot!"), I was just trying to get him pointed in a direction where he could get CLIM working. > > And just for the record, I don't actually do 'xhost +' but since none of you have any need to know the names of my trusted internal machines and since I can't come down the hall and fire you if need be, I simplified the .xinitrc file. > > And I hope Bruce already knows he should investigate and think about all advice he gets from the net, not just blindly follow what any group of yahoos tells him to do. > > Mike McDonald > mikemac at mikemac.com > > > >