[Xquartz-dev] XQuartz 2.6.1_rc1

Peter Dyballa Peter_Dyballa at Web.DE
Mon Mar 21 10:12:04 PDT 2011


Am 21.03.2011 um 17:00 schrieb Jeremy Huddleston:

>>>>> Are you saying that your rendering issue is ok in 1.3.0-apple5  
>>>>> and present in 1.5.3-apple14?
>>>>
>>>>
>>>> Exactly! The XFree86 Version 4.4.0 X server is top!
>>>
>>> ?  What do you mean by that?  X11_Legacy.pkg, or 1.3.0-apple5?   
>>> Where are you getting 1.3.0-apple5?  That version is from 2.1.1  
>>> and matches what shipped in OSX 10.5.2 ...
>>
>> Sorry! I did not understand that your question was about a so early  
>> package as X11-2.1.1.pkg! I fetched it, installed it, and rebooted.  
>> The effect is that this X server does not come up delegates its  
>> duties to Macports:
>
> I only mentioned 2.1.1 after you mentioned the 1.3.0-apple5 server.   
> I'm just saying you should figure out when the problem was  
> introduced.  YOU mentioned that it worked in 1.3.0-apple5.  1.3.0- 
> apple5 comes with either 2.1.1, or Mac OS X 10.5.2 ... so I was  
> wondering how you got your 1.3.0-apple5 case.

I think I saw the "1.3.0-apple5" name when launched the X11_Legacy X  
server, so I assumed two names for the same and forgot the hard to  
remember name with the apple.

>
>> Should I remove /opt/local/bin from PATH or deactivate the MacPorts  
>> X server for proper testing?
>
> yes just:
>
> sudo port -v deactivate xorg-server
> logout


I also had to remove /Library/LaunchAgents/org.macports.startx.plist  
and /Library/LaunchDaemons/org.macports.privileged_startx.plist to  
foreclose MacPorts' X server. Now it looks as if /Applications/ 
Utilities/X11.app does the job itself.

--
Greetings

   Pete

There's no sense in being precise when you don't even know what you're  
talking about.
				– John von Neumann



More information about the Xquartz-dev mailing list