On 9/29/05, Marc Boxerman <[EMAIL PROTECTED]> wrote: > Alexander: > > Echo $DISPLAY returns localhost:0.0 from my shell running from > Terminal.app. From the xterm I run from Apple's X11 (via the > Applications pull-down menu) it returns :0.0. From what I understand > that is effectively the same thing. > > DISPLAY is set to localhost.0.0 from my .cshrc file. >
Hmmm..yeah, that _should_ be the same thing. So much for brilliant ideas. ;-) Try setting DISPLAY in your .cshrc to just ":0.0" (get rid of "localhost") and see if that helps. > Marc > > On Sep 29, 2005, at 8:00 AM, Alexander K. Hansen wrote: > > > On 9/29/05, Marc Boxerman <[EMAIL PROTECTED]> wrote: > > > >> I too, of late, have been having trouble running X apps from > >> Terminal.app. All used to be well until I temporarily switched from > >> Apple's quartz-wm in rootless mode to Window Maker in full screen > >> mode. Upon returning to quartz-wm, I get the following error: > >> > >> [santorini:~] marc% xclock & > >> [1] 2556 > >> [santorini:~] marc% Error: Can't open display: localhost:0.0 > >> > >> [1] Exit 1 xclock > >> > >> Now my DISPLAY environment is properly set: > >> > >> [santorini:~] marc% echo $DISPLAY > >> localhost:0.0 > >> > >> I do get an error in Console but I do not know if it is related to my > >> problem: > >> > >> XFree86 Version 4.4.0 / X Window System > >> (protocol Version 11, revision 0, vendor release 6600) > >> [DRI] screen 0 installation complete > >> Screen 0 added: 1024x768 @ (0,0) > >> Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, > >> removing from list! > >> > >> > > > > Completely unrelated. > > > > > >> X apps launch and run just fine from within an xterm. > >> > >> I use Apple's X11.app. > >> > >> Any suggestions? > >> > >> Thanks, > >> > >> Marc > >> > >> > >> > >> > > > > I would suspect that you've got a stale reference to display :0 > > somewhere (e.g. a zombie xinit process or a lockfile) and that > > X11.app is putting you on display :1 . You can confirm this by > > checking DISPLAY from an xterm. > > > > (the "screen 0" message on starting X11 still applies because you're > > on screen 0 of display 1) > > > > X11.app is clever and will increment DISPLAY if another X server is > > running. I don't know exactly why it was set up that way, though I've > > exploited it myself--XDarwin.app on :0 and X11.app on :1, for example. > > > > -- > > Alexander K. Hansen > > Fink Documenter > > [Day Job] Levitated Dipole Experiment > > http://psfcwww2.psfc.mit.edu/ldx/ > > > -- Alexander K. Hansen Fink Documenter [Day Job] Levitated Dipole Experiment http://psfcwww2.psfc.mit.edu/ldx/ ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Fink-beginners mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-beginners
