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

2.3.0 rc4
by Peter Collinson 16 Jun '08

16 Jun '08

There seems to be a change from previous behaviour - (nearly) all the commands in my Applications menu have stopped working. Most are calls to shells scripts in my ~/bin... and so it looks as if the code has stopped respecting my private PATH. The command that's working calls xterm - so it's picking up the default PATH. Sorry if this has been flagged before. Regards _____________________________________________ Peter Collinson

3 4

Re: [Xquartz-dev] 2.3.0-rc4
by Vincent Morénas 16 Jun '08

16 Jun '08

This is exactly the symptom I've been experiencing (see my preceding post for 2.3.0-rc3) and that I (wrongly) believed to be related to a crash of the server that occured a short time before. I still have the problem with 2.3.0-rc4 on two different PPC macs under 10.5.3 (note that if I deselect the "authenticate connexions" checkbox, the problem disappears). I also installed 2.3.0-rc4 on an intel mac : works as expected there !!! Vincent. Le 15 juin 08 à 20:46, Martin Costabel a écrit : > > Merle Reinhart wrote: > [] >> Could this be caused by something stale being left behind and not >> having been cleaned up in /tmp/ ? > > Not in /tmp/ in any case. I rebooted, which cleaned /tmp/ out and > repopulated it with a couple of launch* things. The problem is still > there. > > Then I installed X11-2.2.1, logout/login: Problem gone; > Then I reinstalled X11-2.3.0-rc4, logout/login: Problem reappears. > > I tried it from a different, completely standard, user account: Same > problem. > > -- > Martin

4 7

2.3.0-rc4
by Jeremy Huddleston 15 Jun '08

15 Jun '08

I'd like to announce a new release candidate for 2.3.0. rc4 furthers the transition to the new startup model by using Mach IPC from the stub to tell the server how to start. The .app no longer starts in the background. Note. I've had a hunch for a long time that this was the cause of the "focus loss" issue where Growl, iCal, etc "steal" focus from X11 momentarily. If you suffer from that bug, please report on whether or not you still see those problems in rc4. Additionally, this includes fixes for some security issues announced earlier today. I am rushing this release a bit in order to get the security fixes in place. I would've liked to have had more time to stress test the new startup model, but I am confident that it is usable since there are no major issues that I've seen. Please report back any issues you have. I intend to put together a 2.2.2 release that includes just changes to the 1.3 server branch (the security fixes and monitor hotplug) tomorrow or Friday. It was just far easier to throw together a 2.3.0 release than the 2.2.2 release... but know that it is a priority as well. http://xquartz.macosforge.org/downloads/X11-2.3.0_rc4.pkg --Jeremy

5 12

Tablet development
by Jeremy Huddleston 15 Jun '08

15 Jun '08

Anyone interested in helping out with tablet support in Xquartz might be interested in Woot's daily special today. You can get a tablet for $33 + $5/shipping. http://www.woot.com --Jeremy

1 0

pressure sensitivity: wacom
by Jonathan Chetwynd 14 Jun '08

14 Jun '08

pressure sensitivity: wacom I had understood there was some progress, was the issue fixed, abandoned, still in progress? cheers Jonathan Chetwynd j.chetwynd(a)btinternet.com http://www.openicon.org/ +44 (0) 20 7978 1764

3 6

X11-2.3.0_rc4.pkg - X protocol error
by Alexander Kappes 14 Jun '08

14 Jun '08

Hi, I'm running with Leopard 10.5.3 on a MacBook Pro. After installing X11-2.3.0_rc4.pkg (I'm not sure whether this already happend with X11-2.3.0_rc3.pkg) I experience a reproducable crash of emacs when running it on a remote machine. I ssh to that machine, then start emacs and as soon as I try to mark something with the mouse (i.e. moving the mouse with left mouse button pressed) emacs crashes with the following error message: X protocol error: BadWindow (invalid Window parameter) on protocol request 38 Because of this problem, I would like to revert back to 2.2.1. Can I just install the 2.2.1 package over what I have now? Best wishes, Alexander

3 3

2.2.2-rc1
by Jeremy Huddleston 12 Jun '08

12 Jun '08

So as promised, I have a release candidate now available for 2.2.2. This version is the same as 2.2.1 with an updated server to include the security issues announced yesterday. It also has a fix for monitor hotplugging that was committed after I released 2.2.1. Release notes (note that the download URL is "broken" to the release filename, not the rc): http://xquartz.macosforge.org/trac/wiki/X112.2.2 and the package: http://xquartz.macosforge.org/downloads/X11-2.2.2_rc1.pkg Due to the small delta, I don't expect any issues with this release... but I'd still like to get a few "works here"s before I release. Thanks, Jeremy

2 1

Re: [Xquartz-dev] Weird situation with 2.3.0-rc3
by Vincent Morénas 11 Jun '08

11 Jun '08

The crash log I attached is the crash log that was written shortly after I resized an X11 window (displayed through a ssh connection) and the server went down. But maybe that was just a coincidence... I don't know. Anyway I think my pulling the resize corner of the window triggered the crash. The other piece of the situation is the X11 launch problem I mentioned. Before the crash, it was working all right but after it, the Xserver doesn't seem to be active as soon as it used to be (see my original mail). That is a little annoying now for everyday use, especially when I ssh on distant machines. Moreover, this also happens now on a clean (I hope) install of 2.3.0-rc3 whereas 2.2.1 works ok. So something must have changed somewhere.... What files could have been modified, apart from the ones in the X112.3.0-rc3 pkg? V. On Jun 10, 2008, at 10:54, Jeremy Huddleston wrote: > Is that crash log the one from the window resize? Or is that crash > log different? I've seen that crash log before when I handed off the > launchd display socket to the X server before the X server was ready > for it, but after I fixed that, I haven't seen the issue come back. > > The only thing that I could think that would be causing a crash there > needs noPanoramixExtension to be set to false, and that happens at > startup. > > On Jun 10, 2008, at 09:28, Vincent Mor?nas wrote: > >> Hello, >> >> I have installed 2.3.0-rc3 and been using it for about a week now... >> flawlessly for my usage. >> But this morning the X11.app crashed while I was resizing a window >> (I was connected to a distant machine through ssh) and since then, >> there's something wrong with the launch mechanism : with the >> terminal app , if I type xlogo for instance, X11 starts and then I >> get this message : >> Xlib: connection to "/tmp/launch-aOgpYn/:0" refused by server >> Xlib: No protocol specified >> If I type xlogo again, with that X11 app freshly launched and >> running, the logo appears and no more error messages.... (racing >> condition?) >> >> I decided to re-install 2.3.0-rc3 from scratch (I hope I erased all >> traces of X11 before : I lsbom-ed the receipts of the installed >> package to see where the files were written and I also erased the >> X11 preferences from my home directory).... same behaviour with the >> new install. >> So I removed X11 2.3.0-rc3 once again and installed 2.2.1... the >> problem didn't appear. >> Finally I re-installed 2.3.0-rc3 over 2.2.1, and the problem >> returned !!! >> >> I don't understand what has changed before and after the crash. Any >> idea ? >> I have attached the crash log for those interested. >> >> Thanks. >> >> Vincent. >> >> <X11.crash> >>

1 0

Weird situation with 2.3.0-rc3
by Vincent Morénas 10 Jun '08

10 Jun '08

Hello, I have installed 2.3.0-rc3 and been using it for about a week now... flawlessly for my usage. But this morning the X11.app crashed while I was resizing a window (I was connected to a distant machine through ssh) and since then, there's something wrong with the launch mechanism : with the terminal app , if I type xlogo for instance, X11 starts and then I get this message : Xlib: connection to "/tmp/launch-aOgpYn/:0" refused by server Xlib: No protocol specified If I type xlogo again, with that X11 app freshly launched and running, the logo appears and no more error messages.... (racing condition?) I decided to re-install 2.3.0-rc3 from scratch (I hope I erased all traces of X11 before : I lsbom-ed the receipts of the installed package to see where the files were written and I also erased the X11 preferences from my home directory).... same behaviour with the new install. So I removed X11 2.3.0-rc3 once again and installed 2.2.1... the problem didn't appear. Finally I re-installed 2.3.0-rc3 over 2.2.1, and the problem returned !!! I don't understand what has changed before and after the crash. Any idea ? I have attached the crash log for those interested. Thanks. Vincent.

2 1

1.4.0-apple14
by Jeremy Huddleston 10 Jun '08

10 Jun '08

I just uploaded new version of the server (1.4.0-apple14). It uses mach IPC to start the server rather than exec(). This will help us be more OSX-paradigm friendly in that there should now never be two instances of the process running at the same time. Please test it out (and keep your 1.4.0-apple13 binary (from 2.3.0-rc3) handy). I've noticed that it seems a bit "sluggish" to startup, and I'm not exactly sure why that is, but any feedback would be greatly appreciated. This should do the trick of installing the update: wget http://xquartz.macosforge.org/downloads/X11-1.4.0-apple14.bz2 wget http://xquartz.macosforge.org/downloads/Xquartz-1.4.0-apple14.bz2 bunzip2 X11-1.4.0-apple14.bz2 bunzip2 Xquartz-1.4.0-apple14.bz2 sudo mv /usr/X11/bin/Xquartz /usr/X11/bin/Xquartz.bak sudo mv /Applications/Utilities/X11.app/Contents/MacOS/X11 / Applications/Utilities/X11.app/Contents/MacOS/X11.bak sudo cp Xquartz-1.4.0-apple14 /usr/X11/bin/Xquartz sudo cp X11-1.4.0-apple14 /Applications/Utilities/X11.app/Contents/ MacOS/X11 Thanks, Jeremy

2 3