I think I've fixed the major issues that were still present in 2.3.2- rc4. I've uploaded a drop-in binary for testing... If you're not comfortable with this process, just wait for the final package release. The following issues should be addressed: 1) Root window shows a strip of the OSX desktop at the bottom the first time it's used * This caused a crash if you'd do something like 'xsetroot ...' in that state 2) Fixed a deadlock issue between our pbproxy/appkit/server threads 3) Run applications using '/bin/sh -c' (or whatever your login_shell default is set to instead of /bin/sh) 4) Don't pass a character to the X clients when doing cmd-alt-a to enter/leave fullscreen (This has no impact on the shell script issues that are being discussed) Instructions: curl -LO http://static.macosforge.org/xquartz/downloads/X11.bin-1.4.2-apple29.bz2 bunzip2 X11.bin-1.4.2-apple29.bz2 sudo cp X11.bin-1.4.2-apple29 /Applications/Utilities/X11.app/Contents/ MacOS/X11.bin sudo chmod 755 /Applications/Utilities/X11.app/Contents/MacOS/X11.bin
Hi Jeremy, I dropped in the new X11.bin. I see "XQuartz 2.3.2_rc4 (xorg-server 1.4.2-apple29)" in the About X11 window, so the binary is being used. I'm having root window problems, perhaps similar to those reported by Viv Kendon, if memory serves. For reference, I have the X11 "Full-screen mode" box checked and the "Auto-show menu bar in full-screen mode" unchecked. With X11.app not open, I type "xsetroot -solid red" in Terminal. This automatically starts X11. I click on the X11 dock icon and I see a solid red screen. I do "command-option-a" and my Desktop appears with X11 as the active application. I immediately do another "command-option-a" and the menu bar disappears but no red screen. I still see my Desktop, and clicking on it simply activates Finder. Something seems amiss. By the way, I was surprised to see that the size of this new X11.bin is 6.5M compared to 3.4M. Louis On Sun, 21 Dec 2008 21:30:52 -0800 Jeremy Huddleston <jeremyhu@apple.com> wrote:
I think I've fixed the major issues that were still present in 2.3.2- rc4. I've uploaded a drop-in binary for testing... If you're not comfortable with this process, just wait for the final package release. The following issues should be addressed:
1) Root window shows a strip of the OSX desktop at the bottom the first time it's used * This caused a crash if you'd do something like 'xsetroot ...' in that state 2) Fixed a deadlock issue between our pbproxy/appkit/server threads 3) Run applications using '/bin/sh -c' (or whatever your login_shell default is set to instead of /bin/sh) 4) Don't pass a character to the X clients when doing cmd-alt-a to enter/leave fullscreen
(This has no impact on the shell script issues that are being discussed)
Instructions: curl -LO http://static.macosforge.org/xquartz/downloads/X11.bin-1.4.2-apple29.bz2 bunzip2 X11.bin-1.4.2-apple29.bz2 sudo cp X11.bin-1.4.2-apple29 /Applications/Utilities/X11.app/Contents/ MacOS/X11.bin sudo chmod 755 /Applications/Utilities/X11.app/Contents/MacOS/X11.bin
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Dec 22, 2008, at 03:24, Zulli, Louis P wrote:
Hi Jeremy,
I dropped in the new X11.bin. I see "XQuartz 2.3.2_rc4 (xorg-server 1.4.2-apple29)" in the About X11 window, so the binary is being used.
I'm having root window problems, perhaps similar to those reported by Viv Kendon, if memory serves. For reference, I have the X11 "Full- screen mode" box checked and the "Auto-show menu bar in full-screen mode" unchecked.
With X11.app not open, I type "xsetroot -solid red" in Terminal. This automatically starts X11. I click on the X11 dock icon and I see a solid red screen. I do "command-option-a" and my Desktop appears with X11 as the active application. I immediately do another "command-option-a" and the menu bar disappears but no red screen. I still see my Desktop, and clicking on it simply activates Finder.
I don't think this was not one of the issues that Viv reported... (or if it was, it was one that I can't dig up and fell through the cracks). Please report this at http://xquartz.macosforge.org so it doesn't get lost. If I can come up with a fix in the next few days, I'll include it... otherwise it will have to wait for 2.3.3 or 2.4.0 ...
Something seems amiss.
By the way, I was surprised to see that the size of this new X11.bin is 6.5M compared to 3.4M.
It has debug symbols in it.
OK, I'll report it officially. Unless I'm mistaken, this seems like a significant regression, in that full-screen mode is simply not working---the root window becomes "lost" forever after one application of command-option-a. Try starting X11 by typing xeyes in Terminal, with X11 set for full-screen mode. Then do command-option-a twice in succession. No more gray root window. Things seemed much better with the X11.bin from Dec. 17; I just put it back in place and checked. Louis On Mon, 22 Dec 2008 11:48:30 -0800 Jeremy Huddleston <jeremyhu@apple.com> wrote:
On Dec 22, 2008, at 03:24, Zulli, Louis P wrote:
Hi Jeremy,
I dropped in the new X11.bin. I see "XQuartz 2.3.2_rc4 (xorg-server 1.4.2-apple29)" in the About X11 window, so the binary is being used.
I'm having root window problems, perhaps similar to those reported by Viv Kendon, if memory serves. For reference, I have the X11 "Full- screen mode" box checked and the "Auto-show menu bar in full-screen mode" unchecked.
With X11.app not open, I type "xsetroot -solid red" in Terminal. This automatically starts X11. I click on the X11 dock icon and I see a solid red screen. I do "command-option-a" and my Desktop appears with X11 as the active application. I immediately do another "command-option-a" and the menu bar disappears but no red screen. I still see my Desktop, and clicking on it simply activates Finder.
I don't think this was not one of the issues that Viv reported... (or if it was, it was one that I can't dig up and fell through the cracks). Please report this at http://xquartz.macosforge.org so it doesn't get lost.
If I can come up with a fix in the next few days, I'll include it... otherwise it will have to wait for 2.3.3 or 2.4.0 ...
Something seems amiss.
By the way, I was surprised to see that the size of this new X11.bin is 6.5M compared to 3.4M.
It has debug symbols in it.
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Well I can't reproduce your findings at all... sorry... On Dec 22, 2008, at 12:22, Zulli, Louis P wrote:
OK, I'll report it officially. Unless I'm mistaken, this seems like a significant regression, in that full-screen mode is simply not working---the root window becomes "lost" forever after one application of command-option-a. Try starting X11 by typing xeyes in Terminal, with X11 set for full-screen mode. Then do command-option-a twice in succession. No more gray root window.
Things seemed much better with the X11.bin from Dec. 17; I just put it back in place and checked.
Louis
On Mon, 22 Dec 2008 11:48:30 -0800 Jeremy Huddleston <jeremyhu@apple.com> wrote:
On Dec 22, 2008, at 03:24, Zulli, Louis P wrote:
Hi Jeremy,
I dropped in the new X11.bin. I see "XQuartz 2.3.2_rc4 (xorg- server 1.4.2-apple29)" in the About X11 window, so the binary is being used.
I'm having root window problems, perhaps similar to those reported by Viv Kendon, if memory serves. For reference, I have the X11 "Full- screen mode" box checked and the "Auto-show menu bar in full-screen mode" unchecked.
With X11.app not open, I type "xsetroot -solid red" in Terminal. This automatically starts X11. I click on the X11 dock icon and I see a solid red screen. I do "command-option-a" and my Desktop appears with X11 as the active application. I immediately do another "command-option-a" and the menu bar disappears but no red screen. I still see my Desktop, and clicking on it simply activates Finder.
I don't think this was not one of the issues that Viv reported... (or if it was, it was one that I can't dig up and fell through the cracks). Please report this at http://xquartz.macosforge.org so it doesn't get lost. If I can come up with a fix in the next few days, I'll include it... otherwise it will have to wait for 2.3.3 or 2.4.0 ...
Something seems amiss.
By the way, I was surprised to see that the size of this new X11.bin is 6.5M compared to 3.4M. It has debug symbols in it.
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Well, now I'm puzzled. Will reinstall X11-2.3.2_rc4.pkg. Afterwards I'll replace X11.bin with your latest version, as I did early this morning. Is there something else I need to update too? Then I'll try again. Louis On Mon, 22 Dec 2008 12:47:32 -0800 Jeremy Huddleston <jeremyhu@apple.com> wrote:
Well I can't reproduce your findings at all... sorry...
On Dec 22, 2008, at 12:22, Zulli, Louis P wrote:
OK, I'll report it officially. Unless I'm mistaken, this seems like a significant regression, in that full-screen mode is simply not working---the root window becomes "lost" forever after one application of command-option-a. Try starting X11 by typing xeyes in Terminal, with X11 set for full-screen mode. Then do command-option-a twice in succession. No more gray root window.
Things seemed much better with the X11.bin from Dec. 17; I just put it back in place and checked.
Louis
On Mon, 22 Dec 2008 11:48:30 -0800 Jeremy Huddleston <jeremyhu@apple.com> wrote:
On Dec 22, 2008, at 03:24, Zulli, Louis P wrote:
Hi Jeremy,
I dropped in the new X11.bin. I see "XQuartz 2.3.2_rc4 (xorg- server 1.4.2-apple29)" in the About X11 window, so the binary is being used.
I'm having root window problems, perhaps similar to those reported by Viv Kendon, if memory serves. For reference, I have the X11 "Full- screen mode" box checked and the "Auto-show menu bar in full-screen mode" unchecked.
With X11.app not open, I type "xsetroot -solid red" in Terminal. This automatically starts X11. I click on the X11 dock icon and I see a solid red screen. I do "command-option-a" and my Desktop appears with X11 as the active application. I immediately do another "command-option-a" and the menu bar disappears but no red screen. I still see my Desktop, and clicking on it simply activates Finder.
I don't think this was not one of the issues that Viv reported... (or if it was, it was one that I can't dig up and fell through the cracks). Please report this at http://xquartz.macosforge.org so it doesn't get lost. If I can come up with a fix in the next few days, I'll include it... otherwise it will have to wait for 2.3.3 or 2.4.0 ...
Something seems amiss.
By the way, I was surprised to see that the size of this new X11.bin is 6.5M compared to 3.4M. It has debug symbols in it.
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Hi again, Same issues still. I just reinstalled X11-2.3.2_rc4.pkg. I then followed these instructions: curl -LO http://static.macosforge.org/xquartz/downloads/X11.bin-1.4.2-apple29.bz2 bunzip2 X11.bin-1.4.2-apple29.bz2 sudo cp X11.bin-1.4.2-apple29 /Applications/Utilities/X11.app/Contents/ MacOS/X11.bin sudo chmod 755 /Applications/Utilities/X11.app/Contents/MacOS/X11.bin (Actually, I followed the first two and then moved X11.bin-1.4.2-apple29 to /Applications/Utilities/X11.app/Contents/MacOS/ I then changed its permissions to 755 and did sudo chown root X11.bin-1.4.2-apple29 . Finally I edited the X11 script in that directory, changing X11.bin to X11.bin-1.4.2-apple29 ) The situation is actually worse than I reported previously. With X11 set for full-screen mode but not open, I type xeyes in Terminal. This starts X11, and for an instant I see the eyes, but then they disappear and I see an empty gray screen. Two successive toggles using command-option-a and then I see the xeyes window, but it's in front of my Desktop, not on a gray background. And if I click on that Desktop I activate Finder. What's wrong with my system? That is the right binary you posted the link to, right? Sorry for taking your time, Louis On Mon, 22 Dec 2008 15:56:58 -0500 "Zulli, Louis P" <zullil@lafayette.edu> wrote:
Well, now I'm puzzled. Will reinstall X11-2.3.2_rc4.pkg. Afterwards I'll replace X11.bin with your latest version, as I did early this morning. Is there something else I need to update too?
Then I'll try again.
Louis
On Mon, 22 Dec 2008 12:47:32 -0800 Jeremy Huddleston <jeremyhu@apple.com> wrote:
Well I can't reproduce your findings at all... sorry...
On Dec 22, 2008, at 12:22, Zulli, Louis P wrote:
OK, I'll report it officially. Unless I'm mistaken, this seems like a significant regression, in that full-screen mode is simply not working---the root window becomes "lost" forever after one application of command-option-a. Try starting X11 by typing xeyes in Terminal, with X11 set for full-screen mode. Then do command-option-a twice in succession. No more gray root window.
Things seemed much better with the X11.bin from Dec. 17; I just put it back in place and checked.
Louis
On Mon, 22 Dec 2008 11:48:30 -0800 Jeremy Huddleston <jeremyhu@apple.com> wrote:
On Dec 22, 2008, at 03:24, Zulli, Louis P wrote:
Hi Jeremy,
I dropped in the new X11.bin. I see "XQuartz 2.3.2_rc4 (xorg- server 1.4.2-apple29)" in the About X11 window, so the binary is being used.
I'm having root window problems, perhaps similar to those reported by Viv Kendon, if memory serves. For reference, I have the X11 "Full- screen mode" box checked and the "Auto-show menu bar in full-screen mode" unchecked.
With X11.app not open, I type "xsetroot -solid red" in Terminal. This automatically starts X11. I click on the X11 dock icon and I see a solid red screen. I do "command-option-a" and my Desktop appears with X11 as the active application. I immediately do another "command-option-a" and the menu bar disappears but no red screen. I still see my Desktop, and clicking on it simply activates Finder.
I don't think this was not one of the issues that Viv reported... (or if it was, it was one that I can't dig up and fell through the cracks). Please report this at http://xquartz.macosforge.org so it doesn't get lost. If I can come up with a fix in the next few days, I'll include it... otherwise it will have to wait for 2.3.3 or 2.4.0 ...
Something seems amiss.
By the way, I was surprised to see that the size of this new X11.bin is 6.5M compared to 3.4M. It has debug symbols in it.
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Dec 22, 2008, at 13:32, Zulli, Louis P wrote:
Hi again,
Same issues still.
<snip/>
The situation is actually worse than I reported previously. With X11 set for full-screen mode but not open, I type xeyes in Terminal. This starts X11, and for an instant I see the eyes, but then they disappear and I see an empty gray screen.
Yeah, that's a known/existing bug not new to 1.4.2-apple29...
Two successive toggles using command-option-a and then I see the xeyes window, but it's in front of my Desktop, not on a gray background.
I see an X11 "weave" background... can anyone else confirm this problem?
And if I click on that Desktop I activate Finder.
What's wrong with my system? That is the right binary you posted the link to, right?
Yeah, it's the right binary... check the ticket you opened. I asked for some info (your system spec, 'defaults read org.x.X11' ... maybe it's a combination of options that somehow triggers it...)
Hi Jeremy, Your X11.bin-20081224 seems to fixed the "lost" root window issues that I reported. Thanks again! It also seems to have resolved this: "With X11 set for full-screen mode but not open, I type xeyes in Terminal. This starts X11, and for an instant I see the eyes, but then they disappear and I see an empty gray screen. Two successive toggles using command-option-a and then I see the xeyes window, but it's in front of my Desktop, not on a gray background. And if I click on that Desktop I activate Finder." Thank you for all your work on Xquartz. Louis On Mon, 22 Dec 2008 16:32:40 -0500 "Zulli, Louis P" <zullil@lafayette.edu> wrote:
Hi again,
Same issues still.
I just reinstalled X11-2.3.2_rc4.pkg. I then followed these instructions:
curl -LO http://static.macosforge.org/xquartz/downloads/X11.bin-1.4.2-apple29.bz2 bunzip2 X11.bin-1.4.2-apple29.bz2 sudo cp X11.bin-1.4.2-apple29 /Applications/Utilities/X11.app/Contents/ MacOS/X11.bin sudo chmod 755 /Applications/Utilities/X11.app/Contents/MacOS/X11.bin
(Actually, I followed the first two and then moved X11.bin-1.4.2-apple29 to /Applications/Utilities/X11.app/Contents/MacOS/ I then changed its permissions to 755 and did sudo chown root X11.bin-1.4.2-apple29 . Finally I edited the X11 script in that directory, changing X11.bin to X11.bin-1.4.2-apple29 )
The situation is actually worse than I reported previously. With X11 set for full-screen mode but not open, I type xeyes in Terminal. This starts X11, and for an instant I see the eyes, but then they disappear and I see an empty gray screen. Two successive toggles using command-option-a and then I see the xeyes window, but it's in front of my Desktop, not on a gray background. And if I click on that Desktop I activate Finder.
What's wrong with my system? That is the right binary you posted the link to, right?
Sorry for taking your time,
Louis
On Mon, 22 Dec 2008 15:56:58 -0500 "Zulli, Louis P" <zullil@lafayette.edu> wrote:
Well, now I'm puzzled. Will reinstall X11-2.3.2_rc4.pkg. Afterwards I'll replace X11.bin with your latest version, as I did early this morning. Is there something else I need to update too?
Then I'll try again.
Louis
On Mon, 22 Dec 2008 12:47:32 -0800 Jeremy Huddleston <jeremyhu@apple.com> wrote:
Well I can't reproduce your findings at all... sorry...
On Dec 22, 2008, at 12:22, Zulli, Louis P wrote:
OK, I'll report it officially. Unless I'm mistaken, this seems like a significant regression, in that full-screen mode is simply not working---the root window becomes "lost" forever after one application of command-option-a. Try starting X11 by typing xeyes in Terminal, with X11 set for full-screen mode. Then do command-option-a twice in succession. No more gray root window.
Things seemed much better with the X11.bin from Dec. 17; I just put it back in place and checked.
Louis
On Mon, 22 Dec 2008 11:48:30 -0800 Jeremy Huddleston <jeremyhu@apple.com> wrote:
On Dec 22, 2008, at 03:24, Zulli, Louis P wrote:
Hi Jeremy,
I dropped in the new X11.bin. I see "XQuartz 2.3.2_rc4 (xorg- server 1.4.2-apple29)" in the About X11 window, so the binary is being used.
I'm having root window problems, perhaps similar to those reported by Viv Kendon, if memory serves. For reference, I have the X11 "Full- screen mode" box checked and the "Auto-show menu bar in full-screen mode" unchecked.
With X11.app not open, I type "xsetroot -solid red" in Terminal. This automatically starts X11. I click on the X11 dock icon and I see a solid red screen. I do "command-option-a" and my Desktop appears with X11 as the active application. I immediately do another "command-option-a" and the menu bar disappears but no red screen. I still see my Desktop, and clicking on it simply activates Finder.
I don't think this was not one of the issues that Viv reported... (or if it was, it was one that I can't dig up and fell through the cracks). Please report this at http://xquartz.macosforge.org so it doesn't get lost. If I can come up with a fix in the next few days, I'll include it... otherwise it will have to wait for 2.3.3 or 2.4.0 ...
Something seems amiss.
By the way, I was surprised to see that the size of this new X11.bin is 6.5M compared to 3.4M. It has debug symbols in it.
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (2)
-
Jeremy Huddleston
-
Zulli, Louis P