Trying XDarwin 1.0a2 on OS X 10.1, and it quits unexpectedly:
[localhost:~] anarkhos% ./Downloads/XDarwin1.0a2\ Folder/Applications/XDarwin.app/Contents/MacOS/XDarwin -rootless
Running rootless inside Mac OS X window server.
This is a pre-release version of XFree86, and is not supported in any
way. Bugs may be reported to XFree86@XFree86.Org and patches submitted
to fixes@XFree86.Org. Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
XFree86 Version 220.127.116.11 / X Window System
(protocol Version 11, revision 0, vendor release 6510)
Release Date: xx September 2001
If the server is older than 6-12 months, or if your hardware is
newer than the above date, look for a newer version before
reporting problems. (See http://www.XFree86.Org/FAQ\)
Operating System: Darwin
Using keymapping provided in /System/Library/Keyboards/USA.keymapping.
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
2001-09-26 16:38:24.566 XDarwin X client process terminated with status 1.
Display mode: Rootless Quartz
Screen 0 added: 1280x1003 @ (0,21)
Screen 1 added: 1024x768 @ (-1024,0)
Screen 0 placed at X11 coordinate (1024,21).
Screen 1 placed at X11 coordinate (0,0).
2001-09-26 16:38:29.567 XDarwin X server thread never quit.
PS: Changing /tmp/.X11-unix to root didn't help
The /tmp/.X11-unix error is harmless.
The 1.0a2 package might have installed read-only root. Check the permissions, especially on the new /usr/X11R6/bin/XDarwinStartup, .../XDarwinQuartz, /Applications/XDarwin.app . The quick permissions fix is `sudo chmod -R a+rX /usr/X11R6 /etc/X11 /Applications/XDarwin.app`
Also, /usr/X11R6/bin/XDarwinQuartz is a symlink to the XDarwin.app binary. If XDarwin.app isn't in /Applications, it might not work.
First off, you need to follow the installation instructions so that XDarwin ends up in /Applications. Second, from the command line, you need to use "startx -- -rootless" instead of trying to start XDarwin directly. If startx is not found, you need to set your path following the directions at http://mrcla.com/XonX/start.html. Previous versions of XDarwin were somewhat lax with regard to path problems, which later caused random bugs. XDarwin 1.0a2 insists you have your path right to start.
Talk abouit moving BACKWARDS!
Now I have to put it in /Applications?!?!
You don't have to put it in /Applications, but if you don't you should change the symlink /usr/X11R6/bin/XDarwinQuartz to point to its new location so startx works, as has always been the case. This has been discussed on the forums here in the past.
One of the goals for XDarwin 1.0a2 has been to make it less contigent on things being in fixed locations. In fact all previous versions were hardwired so that /usr/X11R6/bin had to contain all the X11 excutables. There was no way to change your path, and have it start from somewhere else. (This is not ideal if you want to share the XFree86 stuff on a network for people to try out.)
XDarwin is quite flexible in the configurations that it can be used in, but my point was that it is far easier for us to help track down bugs if you first try it in its standard configuration. In this case, the way you started XDarwin 1.0a2 should work provided:
1. You properly unpacked the rest of the XDarwin 1.0a2 tarball into /usr/X11R6/* where it belongs. XDarwin1.0a2.tgz doesn't only contain the XDarwin application.
2. You set your path correctly to include /usr/X11R6/bin.
3. /usr/X11R6/bin/X is a symlink pointing to /usr/X11R6/bin/XDarwinStartup
4. /usr/X11R6/bin/XDarwinQuartz is a symlink pointing back to your new XDarwin application executable location.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.