After everything went south yesterday, I decided to reinstall panther, Apple's X11, XTools 1.2, X11SDK, and the pertinent OSXSDKs and see if that fixed things. I could not find any config files that were corrupted, so I thought perhaps some of the code had been corrupted.

When I reinstalled 10.3.0, everything worked! I could start Apple's X11 from the command line in Terminal.app by starting xemacs, emacs, or any other X11 app! Then I installed the 10.3.4 update. Now I cannot start Apple's X11 from Terminal.App, but after starting X11 I can start any X11 app including emacs and xemacs from an xterm, the window manager app menu, Terminal.app, or Apple's X11 menubar pulldown app menu! From this behavior, I believe something has changed with 10.3.4 such that you cannot start X11 from the Terminal.app. Otherwise, everything seems to be okay. Evidently, I had some code somewhere that was corrupted, as I was not able to start emacs from anywhere prior to reinstalling the OS.

Has anyone else noticed after upgrading to 10.3.4 whether they could start X11 by calling an X11 app before loading the Xserver? Thanks again to Jens and Martin for their help.

Gary K. Olson



-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to