On Nov 8, 2007, at 5:46 PM, Robert T Wyatt wrote:
Robert T Wyatt wrote:Daniel Johnson wrote:On Nov 8, 2007, at 4:21 PM, Robert T Wyatt wrote:/tmp/launch-xxxxxx/:0 is what X11 sets $DISPLAY to. Could you have set $DISPLAY somewhere like .bashrc or .xinitrc? That would cause problems.Hmmm, don't know how I managed this one (Leopard on Intel): bash-3.2$ xterm xterm: fatal IO error 32 (Broken pipe) or KillClient on X server "/tmp/launch-vZlaTL/:0"DanielYes, the display is now set when Terminal.app starts up. Apparently .bashrc sets it. It didn't yesterday. I only built about 150 packages today, I wonder if one of them volunteered to update .bashrc for me....Wow, thought I had stored that instead of sending it.... Must be getting old. It's not .bashrc either since I moved it away and I still have DISPLAY set when I open my first Terminal.app window after a reboot.
It should be set. Launchd creates a socket in /tmp at login and sets DISPLAY to it. Then whenever a program accesses the socket via DISPLAY, launchd auto-launches X11.app. That way you never have to explicitly start X11, it just magically starts when it's needed. If DISPLAY gets changed somewhere else, things break. I don't know if that's your problem but it's been an issue for other people.
Daniel
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
