On 1/10/12 3:43 PM, Alexander Hansen wrote:
> On 1/10/12 3:11 PM, Richard Miles wrote:
>> I did /sw/bin/kwin & then ran -bash3.2 rmiles $startx font_cache:
>> Scanning user font directories to generate X11 font caches
>
>> launch_msg("CheckIn") IPC failure: Operation not permitted Xquartz:
>> Unable to locate waiting server: org.x.X11 Xquartz: X11.app =
>> /Applications/Utilities/X11.app/Contents/MacOS/X11 Xquartz:
>> Starting X server:
>> /Applications/Utilities/X11.app/Contents/MacOS/X11 --listenonly
>> font_cache: Updating FC cache X11.app: DISPLAY
>> ("/tmp/launch-NDBntn/org.macports:0") does not match our id
>> ("org.x"), unsetting.
>
> That looks like you have some kind of Macports X11 setup going, too?
> We definitely don't support interaction with that.
>
>> X11.app: main(): argc=2 argv[0] =
>> /Applications/Utilities/X11.app/Contents/MacOS/X11.bin argv[1] =
>> --listenonly Waiting for startup parameters via Mach IPC. X11.app:
>> No launchd socket handed off, unsetting DISPLAY X11.app:
>> do_start_x11_server(): argc=4 argv[0] = /usr/X11/bin/X argv[1] =
>> :0 argv[2] = -nolisten argv[3] = tcp Xquartz starting: X.Org X
>> Server 1.4.2-apple56 Build Date: 20100624 (EE) XKB: Couldn't open
>> rules file /usr/X11/share/X11/xkb/rules/base (EE) XKB: Couldn't
>> open rules file /usr/X11/share/X11/xkb/rules/base font_cache: Done
>> ^C waiting for X server to shut down Quitting Xquartz...
>
>
>
> I assume the ^C is you shutting it down?
>
> And the symptom here is that quartz-wm gets run instead of kwin?
>
I had a similar problem to the above just now, and here's a diagnostic
sequence to try:
1. Verify that your window manager works if you a $HOME/.xinitrc
instead of using the new-style $HOME/.xinitrc.d/foo.sh startup scripts (
cf.
http://finkers.wordpress.com/2010/06/10/user-customization-of-x11-on-10-5-and-10-6/
). E.g.:
. /sw/bin/init.sh
quartz-wm --only-proxy &
exec kwin
$HOME/.xinitrc overrides almost every other normal X11
user-customization option.
2. Assuming test 1 works, check what is in
/usr/X11/lib/X11/xinit/xinitrc . This is important when using Fink's
"xinitrc" package. In particular, if you have multiple Fink setups,
then you need to make sure that it is referring to the correct Fink
tree. If not, use "fink reinstall xinitrc" to restore it.
3) Once test 2 works, if you indeed have "xinitrc" installed, and are
attempting to use a $HOME/.xinitrc.d/foo.sh script to launch it, then
you need to make sure that you are actually set up to read files in
$HOME/.xinitrc.d, via creating a /sw/etc/xinitrc-last-hook file as per
http://finkers.wordpress.com/2010/06/18/finks-xinitrc-gnome-and-kde/
.
4. Make sure that any launch script files from $HOME/.xinitrc.d that
correspond to the window manager and applications that you want to run
are executable.
--
Alexander Hansen, Ph.D.
Fink User Liaison
http://finkakh.wordpress.com/
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users
