We've come a long way since 2.4.0 was released, and the end of the road is in sight for 2.5.0. 2.5.0_rc1 looks quite solid, and I'd like to get more people using it. This is the first pre-release of 2.5.0 that has been built for both Leopard and SnowLeopard. The Leopard version still installs to /usr/X11 and X11.app while the SL version installs to /opt/X11 and XQuartz.app to avoid the Software Update collisions that were so common in the Leopard days. With this release, I've created a separate Software Update feed that will contain beta versions (as well as final release versions). To switch to this feed rather than the final-release feed, please execute the following: SnowLeopard: defaults write org.macosforge.xquartz.X11 SUFeedURL http://static.macosforge.org/xquartz/downloads/sparkle/beta.xml Leopard: defaults write org.x.X11 SUFeedURL http://static.macosforge.org/xquartz/downloads/sparkle/beta.xml Assuming you have 2.4.0 on Leopard or one of the earlier 2.5.0 betas for SL, you should see an auto-update notification the next time you start X11 after running the above command. If you don't want to use the SU, you can just download the installer from these links: SnowLeopard: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.5.0_rc1.dmg Leopard: http://static.macosforge.org/xquartz/downloads/Leopard/X11-2.5.0_rc1.dmg The full ChangeLog from 2.4.0 can be seen in the draft release notes: http://xquartz.macosforge.org/trac/wiki/X112.5.0 Please hammer this release. I feel confident that it is release quality, but I want to get a wider audience first. Thanks, Jeremy
On Mar 16, 2010, at 2:59 AM, Jeremy Huddleston wrote: On 10.6, I ran the suggested command.
defaults write org.macosforge.xquartz.X11 SUFeedURL http://static.macosforge.org/xquartz/downloads/sparkle/beta.xml
Assuming you have 2.4.0 on Leopard or one of the earlier 2.5.0 betas for SL, you should see an auto-update notification the next time you start X11 after running the above command.
As expected, the Sparkle update dialog appeared, although I'll note that the changelog page is difficult to read in the narrow dialog box. You may want to create a plainer page to display for the updater. Sparkle then downloads the update and gives me an "Install" button. Once I click the button, it says "An error occurred while installing the update.", which is not terribly descriptive. Checking Console.app, I find: 3/16/10 10:27:56 AM X11.bin[31126] Sparkle Error: An error occurred while installing the update. Please try again later. 3/16/10 10:27:56 AM X11.bin[31126] Sparkle Error (continued): Couldn't find an appropriate update in the downloaded package. I am updating from 2.5.0_beta2 on 10.6.2 ~~ Brian
On Mar 16, 2010, at 07:38, Brian Gernhardt wrote:
As expected, the Sparkle update dialog appeared, although I'll note that the changelog page is difficult to read in the narrow dialog box. You may want to create a plainer page to display for the updater.
Yeah, I know. I'd like to be able to have a URL that contains just the HTML for the page contents (and eliminate the other clutter). Trac should allow this, but when I looked into it, I couldn't find anything to do it.
Sparkle then downloads the update and gives me an "Install" button. Once I click the button, it says "An error occurred while installing the update.", which is not terribly descriptive. Checking Console.app, I find:
3/16/10 10:27:56 AM X11.bin[31126] Sparkle Error: An error occurred while installing the update. Please try again later. 3/16/10 10:27:56 AM X11.bin[31126] Sparkle Error (continued): Couldn't find an appropriate update in the downloaded package.
I am updating from 2.5.0_beta2 on 10.6.2
Odd. I tested that exact update path just now. I wonder if you were given the Leopard version. I was told by the Sparkle developers that the setup I have should work (providing the SL update to SL users and the Leo version to Leo users). I'll comment about this in the existing reports to them: https://bugs.launchpad.net/sparkle/+bug/449942 https://answers.launchpad.net/sparkle/+question/84464 --Jeremy
Hi, the rc1 seems to work pretty good for what I can tell you thus far. I have a problem with fv i.e. a fits file viewer. Apparently it is always looking in the old place to start X11. Regardless on the status of XQuartz, already running or not, it starts the old X11. I guess this might be a problem of fv, but you asked for feedback! ;) cheers Aldo
On Mar 16, 2010, at 02:59 , Jeremy Huddleston wrote:
Please hammer this release. I feel confident that it is release quality, but I want to get a wider audience first.
Double weirdness with dual displays: I have my HDTV hooked up for occasional use as a second monitor, positioned to the left of my iMac's internal screen (iMac is the master screen with the menubar and dock). As it turned out, the mini- DVI connector had worked its way loose, so when I started the new X11 it knew only about the internal display. When I fixed the connector, all my X11 windows moved to the HDTV, then X11 froze. I was able to move the windows back but not to do anything else with them. Interestingly, quitting X11 worked, so it wasn't completely frozen even though things like motion events clearly weren't being responded to (admittedly I couldn't say if they weren't being delivered or if the resulting window updates weren't happening; I need to get xscope and/or xmon going here). -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH
Interesting... I did "fix" some multi-monitor related issues (specifically dealing with and detecting configuration changes). Please file a bug at http://xquartz.macosforge.org, and I'll take a look. I haven't seen anything like this... in fact, it's working better for me now than before... =/ On Mar 16, 2010, at 18:17, Brandon Allbery wrote:
On Mar 16, 2010, at 02:59 , Jeremy Huddleston wrote:
Please hammer this release. I feel confident that it is release quality, but I want to get a wider audience first.
Double weirdness with dual displays:
I have my HDTV hooked up for occasional use as a second monitor, positioned to the left of my iMac's internal screen (iMac is the master screen with the menubar and dock). As it turned out, the mini-DVI connector had worked its way loose, so when I started the new X11 it knew only about the internal display. When I fixed the connector, all my X11 windows moved to the HDTV, then X11 froze. I was able to move the windows back but not to do anything else with them. Interestingly, quitting X11 worked, so it wasn't completely frozen even though things like motion events clearly weren't being responded to (admittedly I couldn't say if they weren't being delivered or if the resulting window updates weren't happening; I need to get xscope and/or xmon going here).
-- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH
_______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list (X11-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/jeremyhu%40freedesktop.org
This email sent to jeremyhu@freedesktop.org
Brandon Allbery <allbery@kf8nh.com> writes:
I have my HDTV hooked up for occasional use as a second monitor, positioned to the left of my iMac's internal screen (iMac is the master screen with the menubar and dock). As it turned out, the mini- DVI connector had worked its way loose, so when I started the new X11 it knew only about the internal display. When I fixed the connector, all my X11 windows moved to the HDTV, then X11 froze. I was able to move the windows back but not to do anything else with them. Interestingly, quitting X11 worked, so it wasn't completely frozen even though things like motion events clearly weren't being responded to (admittedly I couldn't say if they weren't being delivered or if the resulting window updates weren't happening; I need to get xscope and/or xmon going here).
That last bit seems quite like a freeze that I've seen occasionally in recent Xquartz beta versions. The couple of times that I saw it were not during monitor add/remove events, but being able to do menu actions matches up. If you can reproduce it (so far I cannot), try the workaround of hiding and re-exposing X11 to see if it comes back to life. regards, tom lane
On Mar 17, 2010, at 16:40 , Tom Lane wrote:
That last bit seems quite like a freeze that I've seen occasionally in recent Xquartz beta versions. The couple of times that I saw it were not during monitor add/remove events, but being able to do menu actions matches up. If you can reproduce it (so far I cannot), try the workaround of hiding and re-exposing X11 to see if it comes back to life.
I've seen that one as well; this one was different in that there was no mouse tracking, whereas with that freeze the mouse would track but clicking and typing didn't do anything. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH
On 15Mar2010 23:59, Jeremy Huddleston <jeremyhu@apple.com> wrote: | We've come a long way since 2.4.0 was released, and the end of the road | is in sight for 2.5.0. 2.5.0_rc1 looks quite solid, and I'd like to | get more people using it. This is the first pre-release of 2.5.0 that | has been built for both Leopard and SnowLeopard. The Leopard version | still installs to /usr/X11 and X11.app while the SL version installs to | /opt/X11 and XQuartz.app to avoid the Software Update collisions that | were so common in the Leopard days. Does it support a G4 running Leopard? Not important if it doesn't; I'm on a loaner machine for a comparitively brief period of time:-) Cheers, -- Cameron Simpson <cs@zip.com.au> DoD#743 http://www.cskk.ezoshosting.com/cs/ "You can't fit the truth on a t-shirt, man." "That'd fit."
Yes. It supports all Leopard hardware. On Mar 17, 2010, at 17:44, Cameron Simpson wrote:
On 15Mar2010 23:59, Jeremy Huddleston <jeremyhu@apple.com> wrote: | We've come a long way since 2.4.0 was released, and the end of the road | is in sight for 2.5.0. 2.5.0_rc1 looks quite solid, and I'd like to | get more people using it. This is the first pre-release of 2.5.0 that | has been built for both Leopard and SnowLeopard. The Leopard version | still installs to /usr/X11 and X11.app while the SL version installs to | /opt/X11 and XQuartz.app to avoid the Software Update collisions that | were so common in the Leopard days.
Does it support a G4 running Leopard? Not important if it doesn't; I'm on a loaner machine for a comparitively brief period of time:-)
Cheers, -- Cameron Simpson <cs@zip.com.au> DoD#743 http://www.cskk.ezoshosting.com/cs/
"You can't fit the truth on a t-shirt, man." "That'd fit." _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On 17Mar2010 20:50, Jeremy Huddleston <jeremyhu@apple.com> wrote: | Yes. It supports all Leopard hardware. | | On Mar 17, 2010, at 17:44, Cameron Simpson wrote: | > Does it support a G4 running Leopard? Not important if it doesn't; I'm | > on a loaner machine for a comparitively brief period of time:-) Great! -- Cameron Simpson <cs@zip.com.au> DoD#743
On Mon, Mar 15, 2010 at 11:59:06PM -0700, Jeremy Huddleston wrote:
We've come a long way since 2.4.0 was released, and the end of the road is in sight for 2.5.0. 2.5.0_rc1 looks quite solid, and I'd like to get more people using it. This is the first pre-release of 2.5.0 that has been built for both Leopard and SnowLeopard. The Leopard version still installs to /usr/X11 and X11.app while the SL version installs to /opt/X11 and XQuartz.app to avoid the Software Update collisions that were so common in the Leopard days.
With this release, I've created a separate Software Update feed that will contain beta versions (as well as final release versions). To switch to this feed rather than the final-release feed, please execute the following:
SnowLeopard: defaults write org.macosforge.xquartz.X11 SUFeedURL http://static.macosforge.org/xquartz/downloads/sparkle/beta.xml
Leopard: defaults write org.x.X11 SUFeedURL http://static.macosforge.org/xquartz/downloads/sparkle/beta.xml
Assuming you have 2.4.0 on Leopard or one of the earlier 2.5.0 betas for SL, you should see an auto-update notification the next time you start X11 after running the above command. If you don't want to use the SU, you can just download the installer from these links:
SnowLeopard: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.5.0_rc1.dmg
Leopard: http://static.macosforge.org/xquartz/downloads/Leopard/X11-2.5.0_rc1.dmg
The full ChangeLog from 2.4.0 can be seen in the draft release notes: http://xquartz.macosforge.org/trac/wiki/X112.5.0
Please hammer this release. I feel confident that it is release quality, but I want to get a wider audience first.
Thanks, Jeremy
Jeremy, I installed the X11-2.5.0-rc1 release from the Leopard dmg on a QuickSilver G4 and have noticed one oddity. Without rebooting yet, whenever I select the "About X11" dialog from the X11 application, which is launched when starting x windows programs, it reports... Xquartz 2.4.0 (xorg-server 1.5.3-apple14) Is this just a typo in the strings of this for this release? Other than this issue, pymol seems to run fine under this release without any regressions in its demos on a Radeon 9600 graphics card. Jack
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Jeremy, I installed the X11-2.5.0-rc1 release from the Leopard dmg on a QuickSilver G4 and have noticed one oddity. Without rebooting yet, whenever I select the "About X11" dialog from the X11 application, which is launched when starting x windows programs, it reports...
Xquartz 2.4.0 (xorg-server 1.5.3-apple14)
Is this just a typo in the strings of this for this release? Other than this issue, pymol seems to run fine under this release without any regressions in its demos on a Radeon 9600 graphics card.
It should report: 2.5.0_rc1 (xorg-server 1.7.5) Do you have multiple X11.apps on your system that have bundle id org.x.x11? (The MacPorts one is different)? If so, it might've replaced a different one. You can check /var/log/install.log (grep for X11) to see where it may have been redirected.
participants (7)
-
Aldo Dall'Aglio
-
Brandon Allbery
-
Brian Gernhardt
-
Cameron Simpson
-
Jack Howarth
-
Jeremy Huddleston
-
Tom Lane