June 2008 - Xquartz-dev - lists.macosforge.org

minor fontconfig configuration issues
by Martin Otte 05 Jun '08

05 Jun '08

I have installed X11-2.3.0_rc3, and I've noticed that fontconfig does not see any of my local fonts in ~/Library/Fonts. This was probably true in earlier version too. The relevant lines of /usr/X11/lib/X11/fontconfig/fonts.conf are:  <dir>/usr/X11/lib/X11/fonts</dir> <dir>/usr/X11R6/lib/X11/fonts</dir> <dir>~/.fonts</dir> <!-- and in /usr/X11/lib/X11/fontconfig/conf.d/05-osx-fonts.conf: <fontconfig> <dir>/System/Library/Fonts</dir> <dir>/Library/Fonts</dir> </fontconfig> So either the ~/.fonts entry of fonts.conf should be replaced by ~/ Library/Fonts, or ~/.fonts should be removed and ~/Library/Fonts added to 5-osx-fonts.conf. Also, since /usr/X11R6 is a symbolic link to /usr/X11, all of the X11 fonts are being cached twice. The /usr/X11R6/lib/X11/fonts entry should probably be deleted. Otherwise, I haven't had any issues with 2.3.0-rc3 that haven't been mentioned previously. Martin

2 1

Re: [Xquartz-dev] 2.3.0-rc3
by John Koren 05 Jun '08

05 Jun '08

I have just experienced the same problem using 2.3.0-rc3 and it was a direct ssh to a remote machine. The DISPLAY on the remote was set to 10.0. Starting a new connection to the same machine fixed the problem. I have "Authorize network client connections" checked, so that's not the reason for this unstable ssh behavior. It could be also related to the latest OSX 10.5.3 update, which I installed at the same time as 2.3.0-rc3. Cheers -John >Ok, I just checked "Authorize network client connections" in the X preferences >(not sure the exact wording in english) and it now works fine. Not sure why this >option was unchecked in the first place. Weird. > >Sorry for the noise. > >Cheers >Vincent > On Wed, Jun 4, 2008 at 12:36 PM, Merle Reinhart <merlereinhart at mac.com> wrote: > I just tried it from my mac, ssh -Y to a solaris 10 machine, then ssh - > Y to another solaris 10 machine (I don't have linux boxes readily > available). X11 displayed back just fine whether X11 was started on > the Mac prior to the ssh's or if the final ssh produces the request to > start X11. > > Merle > > > > On Jun 4, 2008, at 6:17 AM, Vincent Noel wrote: > >> FWIW, when I follow the steps outlined below with the rc3, I get >> >> $ nedit >> Xlib: connection to "localhost:16.0" refused by server >> Xlib: Invalid MIT-MAGIC-COOKIE-1 key >> NEdit: Can't open display >> >> still working fine with previous X (rc2 was working fine IIRC). >> >> Cheers >> V >> >> On Wed, Jun 4, 2008 at 8:46 AM, Vincent Noel >> <vincent.noel at gmail.com> wrote: >>> Hello, >>> >>> I have noticed a weird problem that has started with the 2.3.0 rc3 >>> update: >>> >>> I usually connect from my mac to a linux machine through ssh, from >>> where I ssh again >>> to a third linux machine to do actual work (the 3rd machine only >>> allows inbound connections >>> from the second one). Until now, X requests were always correctly >>> forwarded back to the local machine (ie I've always been able to open >>> X applications on the 3rd machine and they showed up correctly on my >>> local display, sorry if I'm not using the appropriate terms). >>> With the rc3, I can't do this anymore -- I get an error message on >>> the >>> 3rd machine telling me the X display cannot be opened (the message >>> says something like "cannot open display on localhost:12.0"). >>> >>> I've just tried this from another mac that hasn't been upgraded to >>> rc3, and it works fine, so nothing has changed on the remote machines >>> (the 3rd machine sets DISPLAY to localhost:10.0 if that's any help). >>> >>> The weird part is that X applications open fine when I launch them on >>> the second machine... >>> >>> I've tried rebooting and trashing the X preferences file, but it >>> doesn't help. >>> This is on an MBP with 10.5.3. Everything works as expected apart >>> from that. >>> >>> Cheers, >>> Vincent >>>

1 0

2.3.0-rc3
by Jeremy Huddleston 04 Jun '08

04 Jun '08

I've uploaded a new release candidate for 2.3.0. I've been using this for about a week now and feel comfortable enough about it to put it out "in the wild" to let you all mess with it while I move on to the next stage of the startup rewrite. Major changes since 2.3.0-rc2: Pulled in proper xkeyboard-config data instead of xkbdata (this should get Xfake and Xephyr to work without needing the '-kb' command line option) Reverted Xquartz to not use xkb since we don't actually have a quartz keyboard xkb data file (not sure the best way to solve this, I'm going to leave this headache for post-2.3.0) Xquartz now has the capability to add a new $DISPLAY socket after the server is started (rather than only at start). This is needed for the new OSX-friendly startup method that I'm working on. We use this now just within the server itself, but in rc4, I expect the socket will be handed off to the server by the stub. Please test it out and let me know of any regressions. http://xquartz.macosforge.org/downloads/X11-2.3.0_rc3.pkg Note, I consider this fairly stable and regression free at this point, but there are bound to be some issues that arise. Now that I have this out, I'm going to be working on some things that are a bit more fragile, so if you want to balance "works" with "testing", this should be a fairly safe beta for you. Of course, I may end up eating these words later... --Jeremy

8 19