I just pushed out a second alpha for 2.4.1. This pulls in all the work done at XDC including some fixes for some graphical issues (the "borders" problem), some keymapping issues, scrolling event problems, and many others. This release bumps us up to the 1.6 server branch with 1.6.5-apple1. I was living on the 1.6 branch for a while, and it seems fairly regression free from 1.5, but as always there may be some lingering issues that I haven't picked up on. For those of you interested in helping test out an even newer branch, I've built a server binary from the 1.7.0.901 release. After installing 2.4.1_alpha2, please copy/paste the following to get it installed: cd /tmp curl -LO http://static.macosforge.org/xquartz/downloads/X11.bin-1.7.0.901.bz2 bunzip2 X11.bin-1.7.0.901.bz2 for f in $(otool -L X11.bin-1.7.0.901 | grep /usr/X11 | awk '{print $1}' | sort -u); do install_name_tool -change $f ${f/usr/opt} X11.bin-1.7.0.901 ; done sudo cp X11.bin-1.7.0.901 /Applications/Utilities/XQuartz.app/Contents/ MacOS/X11.bin If I don't hear any nasty problems with 1.7, we'll be moving to it for the next release instead of 1.5 or 1.6. Thanks, Jeremy http://static.macosforge.org/xquartz/downloads/X11-SL-2.4.1_alpha2.dmg http://xquartz.macosforge.org/trac/wiki/ChangeLog Known Issues: You'll need to manually run 'xmodmap' if you have a ~/.Xmodmap file
On Mon, Oct 12, 2009 at 04:34:53PM -0700, Jeremy Huddleston wrote:
I just pushed out a second alpha for 2.4.1. This pulls in all the work done at XDC including some fixes for some graphical issues (the "borders" problem), some keymapping issues, scrolling event problems, and many others.
This release bumps us up to the 1.6 server branch with 1.6.5-apple1. I was living on the 1.6 branch for a while, and it seems fairly regression free from 1.5, but as always there may be some lingering issues that I haven't picked up on.
For those of you interested in helping test out an even newer branch, I've built a server binary from the 1.7.0.901 release. After installing 2.4.1_alpha2, please copy/paste the following to get it installed:
cd /tmp curl -LO http://static.macosforge.org/xquartz/downloads/X11.bin-1.7.0.901.bz2 bunzip2 X11.bin-1.7.0.901.bz2 for f in $(otool -L X11.bin-1.7.0.901 | grep /usr/X11 | awk '{print $1}' | sort -u); do install_name_tool -change $f ${f/usr/opt} X11.bin-1.7.0.901 ; done sudo cp X11.bin-1.7.0.901 /Applications/Utilities/XQuartz.app/Contents/ MacOS/X11.bin
Is anyone having any luck installing the 1.7.0.901 release with these instructions on top of X11-SL-2.4.1_alpha2? I am finding that, while the X11-SL-2.4.1_alpha2 release runs fine, when I install 1.7.0.901, the Xquartz application quits immediately upon launching. Jack
If I don't hear any nasty problems with 1.7, we'll be moving to it for the next release instead of 1.5 or 1.6.
Thanks, Jeremy
http://static.macosforge.org/xquartz/downloads/X11-SL-2.4.1_alpha2.dmg http://xquartz.macosforge.org/trac/wiki/ChangeLog
Known Issues: You'll need to manually run 'xmodmap' if you have a ~/.Xmodmap file
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Oct 12, 2009, at 18:48, Jack Howarth wrote:
Is anyone having any luck installing the 1.7.0.901 release with these instructions on top of X11-SL-2.4.1_alpha2? I am finding that, while the X11-SL-2.4.1_alpha2 release runs fine, when I install 1.7.0.901, the Xquartz application quits immediately upon launching.
It worked for me, but of course my system is a bit "off" from what's out in the wild, so can you provide some more diagnostic info (like the output in /var/log/system.log)? As you notice, I built the binary on Leopard (hence it's linked against /usr/X11/...) ... maybe there's a hardcoded path in there that I wasn't aware of which is causing problems... but it was working for me... =/ I'll build one against the SL version tomorrow... I was just hoping to avoid building two versions of each release.
On 12 Oct 2009, at 16:34, Jeremy Huddleston wrote:
I just pushed out a second alpha for 2.4.1. This pulls in all the work done at XDC including some fixes for some graphical issues (the "borders" problem), some keymapping issues, scrolling event problems, and many others.
zsh% /opt/X11/bin/xterm dyld: Library not loaded: /usr/X11/lib/libfontconfig.1.dylib Referenced from: /opt/X11/bin/xterm Reason: Incompatible library version: xterm requires version 6.0.0 or later, but libfontconfig.1.dylib provides version 5.0.0 zsh: trace trap xterm Also, as soon as I switch back to X11 after switching away, keyboard and mouse events are no longer delivered (confirmed with xev).
Same here. rxvt would not take commands from the keyboard or mouse after leaving and returning to X11. -John On Mon, Oct 12, 2009 at 9:49 PM, Andrew Farmer <andfarm@gmail.com> wrote:
On 12 Oct 2009, at 16:34, Jeremy Huddleston wrote:
I just pushed out a second alpha for 2.4.1. This pulls in all the work done at XDC including some fixes for some graphical issues (the "borders" problem), some keymapping issues, scrolling event problems, and many others.
zsh% /opt/X11/bin/xterm dyld: Library not loaded: /usr/X11/lib/libfontconfig.1.dylib Referenced from: /opt/X11/bin/xterm Reason: Incompatible library version: xterm requires version 6.0.0 or later, but libfontconfig.1.dylib provides version 5.0.0 zsh: trace trap xterm
Also, as soon as I switch back to X11 after switching away, keyboard and mouse events are no longer delivered (confirmed with xev). _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
13 okt 2009 kl. 06.49 skrev Andrew Farmer:
Also, as soon as I switch back to X11 after switching away, keyboard and mouse events are no longer delivered (confirmed with xev).
I had this problem already in alpha1 (or perhaps somewhere in between, since I build from source). I only realised a few days ago that as soon as I close or minimize all xterm windows, keeping only those from wine, the problem goes away. It is also reproducable with xev and xlogo, but not with xeyes or GTK+ windows. -- Pelle Johansson
On Oct 12, 2009, at 23:06, Pelle Johansson wrote:
13 okt 2009 kl. 06.49 skrev Andrew Farmer:
Also, as soon as I switch back to X11 after switching away, keyboard and mouse events are no longer delivered (confirmed with xev).
I had this problem already in alpha1 (or perhaps somewhere in between, since I build from source). I only realised a few days ago that as soon as I close or minimize all xterm windows, keeping only those from wine, the problem goes away. It is also reproducable with xev and xlogo, but not with xeyes or GTK+ windows.
Is it tied to xterms or any terminals? I don't use xterm, so if that's the case, I would miss it... That being said, it's quite odd that xterm would have that effect. I'll be waiting for more debugging data from someone having this issue... quite bizarre...
On Oct 12, 2009, at 21:49, Andrew Farmer wrote:
On 12 Oct 2009, at 16:34, Jeremy Huddleston wrote:
I just pushed out a second alpha for 2.4.1. This pulls in all the work done at XDC including some fixes for some graphical issues (the "borders" problem), some keymapping issues, scrolling event problems, and many others.
zsh% /opt/X11/bin/xterm dyld: Library not loaded: /usr/X11/lib/libfontconfig.1.dylib Referenced from: /opt/X11/bin/xterm Reason: Incompatible library version: xterm requires version 6.0.0 or later, but libfontconfig.1.dylib provides version 5.0.0 zsh: trace trap xterm
hrm... looks like my attempt to purge the old libs/protos failed for the apps... some are finding /usr/X11 for the "missing" deprecated protocols and linking against those... ugg... These are the affected binaries: xdpyinfo xset xterm And these are affected too, but they should be punted: xtrapchar xtrapin xtrapinfo xtrapout xtrapproto xtrapreset xtrapstats
Also, as soon as I switch back to X11 after switching away, keyboard and mouse events are no longer delivered (confirmed with xev).
You're going to need to be a bit more investigative about that... I can't reproduce, and that seems quite odd...
On 12 Oct 2009, at 23:15, Jeremy Huddleston wrote:
Also, as soon as I switch back to X11 after switching away, keyboard and mouse events are no longer delivered (confirmed with xev).
You're going to need to be a bit more investigative about that... I can't reproduce, and that seems quite odd...
Hard to tell what's going on. Switching back to X11 by any method I've tried triggers the bug, and, once I do so: - Keyboard and mouse events are no longer delivered. - quartz-wm decorations are completely unresponsive. - New X clients can still be launched. - xev still gets FocusIn / FocusOut / Expose / ConfigureNotify / (etc) events, but nothing from the keyboard or mouse. - Weirdly, cycling, minimizing, and closing windows from the menu bar still works, as does moving windows to the front via Expose. More importantly, this behavior seems to be localized to XQuartz.app. Replacing it with an older copy is sufficient to solve the problem.
Can you try running these (from Terminal.app): xinput test keyboard xinput test pointer Just to be certain, can you confirm that: 1) You *DID* logout and back in after the install (just to be safe... you should only need to if you didn't have 2.4.1_alpha1). 2) You are using XQuartz.app, not X11.app. On Oct 12, 2009, at 23:31, Andrew Farmer wrote:
On 12 Oct 2009, at 23:15, Jeremy Huddleston wrote:
Also, as soon as I switch back to X11 after switching away, keyboard and mouse events are no longer delivered (confirmed with xev).
You're going to need to be a bit more investigative about that... I can't reproduce, and that seems quite odd...
Hard to tell what's going on. Switching back to X11 by any method I've tried triggers the bug, and, once I do so:
- Keyboard and mouse events are no longer delivered.
- quartz-wm decorations are completely unresponsive.
- New X clients can still be launched.
- xev still gets FocusIn / FocusOut / Expose / ConfigureNotify / (etc) events, but nothing from the keyboard or mouse.
- Weirdly, cycling, minimizing, and closing windows from the menu bar still works, as does moving windows to the front via Expose.
More importantly, this behavior seems to be localized to XQuartz.app. Replacing it with an older copy is sufficient to solve the problem. _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Oct 13, 2009, at 11:50, Jeremy Huddleston wrote:
Can you try running these (from Terminal.app):
xinput test keyboard xinput test pointer
Just to be certain, can you confirm that: 1) You *DID* logout and back in after the install (just to be safe... you should only need to if you didn't have 2.4.1_alpha1). 2) You are using XQuartz.app, not X11.app.
Also, what is the output of 'xmodmap -pk' ?
participants (5)
-
Andrew Farmer
-
Jack Howarth
-
Jeremy Huddleston
-
John Koren
-
Pelle Johansson