March 2010 - Xquartz-dev - lists.macosforge.org

Google Summer of Code 2010 Project
by Marcelo Galvão Póvoa 05 Apr '10

05 Apr '10

Hello, I'm a student interested in participating in GSoC 2010 and I would like to submit an idea for a coding project to X.org. I've already suggested it on their mailing list but I don't know yet if it is feasible because of technical difficulties or proprietary source code issues with Apple. My project would concern in providing a better Mac OS and X server integration in some key user-oriented aspects such as: - Separate every application window in its own dock icon and make it fully featured, including drag and drop files, exposé, etc. - Transform X windows into "native" windows, so they accept features such resize and move using Universal Access and dragging content into it. - Provide smoother scrolling via mouse/trackpad. - Maybe some other nice features :) This would benefit mostly users of GTK or wine applications like me. I don't know about X11 implementation. Does someone know if it a reasonable project? Any comment will be appreciated. Regards, -- Marcelo Galvão Póvoa

2 3

XQuartz 2.5.0
by Jeremy Huddleston 31 Mar '10

31 Mar '10

XQuartz-2.5.0 is done! Thanks to everyone who helped out with testing the alphas, betas, and release candidates. Without your feedback, support, and responsiveness, many issues would've slipped through the cracks. 2.5.0 is a pretty sizable update from our last release (2.4.0) way back in September. The long release cycle has been mainly due to my desire to wait for fixes to land in a SnowLeopard SU which would prevent our updates from breaking the system X11. Those updates landed in 10.6.3, so SnowLeopard users will need to update to 10.6.3 first. As with all Leopard versions, the Security Update that was released today will overwrite some of the files this package installs, so we recommend you install the SecUpdate first (and reinstall X11 after any future SecUpdates). There are really too many changes to list here, but the big ones include moving to the 1.7.x server codebase and syncing up with all other Xorg modules bringing us up to X11R7.5. libXplugin and quartz- wm have seen a bit of work as well (most of which landed in the 10.6.3 release from Apple) to fix GLX performance for ATI cards and address some odd behavior when using Exposé or wine (like Codeweavers Crossover). Full release notes: http://xquartz.macosforge.org/trac/wiki/X112.5.0 And disk images with the installers: Leopard: http://xquartz.macosforge.org/downloads/Leopard/X11-2.5.0.dmg SnowLeopard: http://xquartz.macosforge.org/downloads/SL/XQuartz-2.5.0.dmg Users of previous versions should be able to update by selecting "Check for X11 Updates" from the X11 menu. Please report any issues you come across to our bug tracker (http://xquartz.macosforge.org/trac/newticket ). Thanks, and enjoy! --Jeremy

2 10

OSX 10.6.3 - X11 Updates
by Jeremy Huddleston 29 Mar '10

29 Mar '10

OSX 10.6.3 comes with some updates to X11 which I've been waiting for before releasing the final XQuartz-2.5.0. libXplugin, quartz-wm, and the server have all been updated along with a handful of other libraries. fontconfig was bumped to the same version as shipping with 2.5.0 which should make their caches compatible and solve some of the instabilities with the 2.6.x series that was in SnowLeopard. quartz-wm and libXplugin should have better support for the new Exposé (especially when using wine / Codeweavers Crossover). The server was bumped to 1.4.2-apple53 which pulls in a sizable number of fixes (including X11.app being able to startup when another application [XQuartz.app] owns $DISPLAY): Ben Byer (1): Add (ok, fix) support for DTrace under OS X Jeremy Huddleston (69): XQuartz: Cleanup keymap locking, fix a possible synchro bug XQuartz: Allow more than 3 OSX displays XQuartz: Cleanup getGlCapabilities to avoid hardcoding the number of displays XQuartz: Localization updates XQuartz: Initial support for automatic updates through Sparkle XQuartz: Added a "Check for X11 Updates..." menu item. XQuartz: Set can_quit to true during a Sparkle-initiated relaunch. XQuartz: Change handling of Windows menu to workaround a bug triggered by mixing Sparkle and X11 windows XQuartz: Rever the "Set can_quit to true during a Sparkle-initiated relaunch." change XQuartz: xpr: Added missing include for RootlessHideAllWindows XQuartz: Avoid namespace collission for BOOL in Sparkle XQuartz: Avoid a possible spinlock in applicationWillTerminate XQuartz: Define DDXRingBell XQuartz: no DirectColor XQuartz: Dead code removal for StaticColor visual XQuartz: Unify how we set our bitmasks for visuals XQuartz: Added a reminder not to purge a stub that can lead to a crash XQuartz: Purge redundant QuartzBell XQuartz: Don't use location delta for tablets since NSEvent does not give a precise delta. XQuartz: Use mouseLocation rather than locationInWindow when setting lastpt XQuartz: Only save lastpt on mouse/tablet events XQuartz: GLX: Update visualConfigs.c to look more like the 1.5 server's for easier patching. CheckWindowOptionalNeed: Ensure w->optional is set to avoid SEGFAULT XQuartz: Use --with-launchd-id-prefix for consistency with xinit XQuartz: Check the DISPLAY environment variable to see if the socket at startup is ours. If not, ignore it and fork/exec startx. XQuartz: Check NSINTEGER_DEFINED to make sure the NSInteger and NSUInteger types are defined. XQuartz: Fix a strcpy/strcmp typo XQuartz: pbproxy: 64bit fixes: Properly process an array of Atoms XQuartz: Fix "warning: function declaration isn’t a prototype" noise XQuartz: launchd: Fallback on :0 if prefix:0 gives an error for the socket name XQuartz: pbproxy: Remove debugging XBell() XQuartz: GLX capabilities: Allow 16bit accumulation buffers XQuartz: bundle version 2.3.5 XQuartz: Stop checking version numbers of the bundle because CFBundleGetVersionNumber is gimpish XQuartz: Force a keymap resync on the first keypress to workaround XKB mucking with our keymap. XQuartz: Fix inverse map from mode_switch to alt XQuartz: Nuke TSM XQuartz: Fix a bunch of compilation warnings about style XQuartz: Query the BundleIdentifier from the bundle in X11.bin rather than using the configure option. XQuartz: Remove the redundant xquartz_resetenv_display XQuartz: Push kXquartzReloadKeymap into DarwinEventHandler XQuartz: Cleaned up keymap setting for easier maintenance XQuartz: Set the proper bitmap for key repeats... XQuartz: Dead code removal: quartzPasteboard.[hc] XQuartz: Send mouse location with scroll events. XQuartz: Fix a possible minor memory leak Rootless: Abstract some of the Xplugin specific stuff which has crept into rootlessWindow.c Rootless: src drawable window can now be NULL XQuartz: Run xmodmap after programatically updating the keymap. dix: Properly detect if the other device is frozen XQuartz: Controller thread launches clients XQuartz: Don't weed out duplicates in generated keymap XQuartz: Cleanup X11Controller.m compilation warnings. XQuartz: GLX: Cleanup AIGLX dispatch XQuartz: Buildfix for Leopard and older XQuartz: pbproxy: Wait for the server to finish starting up, so display is valid. XQuartz: Allow better compatability with older versions of xinit XQuartz: pbproxy: Fix building of standalone xpbproxy executable XQuartz: Setup the modifier map in the quartz thread Revert "XQuartz: Don't weed out duplicates in generated keymap" XQuartz: Update Info.plist.cpp copyright dates Peter Hutterer (2): dix: add SetBit(arr, bit) and ClearBit(arr, bit) to include/inputstr.h render: rename SetBit to RenderSetBit.

1 0

Re: [Xquartz-dev] crazy behavior in kmail
by Jeremy Huddleston 29 Mar '10

29 Mar '10

I wonder if this is related to the weird "border issue" where the window is drawn properly, but not if you move it... Is it 100% reproducible? If so, can you please find out what server version introduced the issue: http://static.macosforge.org/xquartz/downloads/SL (download the X11.bin-<version>.bz2, decompress, replace XQuartz.app/Contents/MacOS/X11.bin, and relaunch XQuartz.app). Please try versions: X11.bin-1.7.5.bz2 X11.bin-1.7.5.901.bz2 X11.bin-1.7.5.901.bz2 X11.bin-1.7.6.bz2 If 1.7.6 works, then it means some of our patches that didn't make the final 1.7.6 tarball are the cause of the problem. I don't see anything terribly suspicious in the change log from 1.7.5 (which was included in rc1): http://cgit.freedesktop.org/~jeremyhu/xserver/log/?h=server-1.7-apple On Mar 28, 2010, at 09:42, Christof Wolf wrote: > Jeremy, > > If I want to compose a new email and do not move the window of the composer > everything seems fine. If I move it the thing goes crazy, I can't put > anything in the To field, nor do the menus work properly. Sometimes if the > pull down menu pops up, there is the bottom line missing. I have attached > some screenshots :-) this just happend with the rc2 > > any idea? > > ciao > christof > > -- > public key www.hfph.mwn.de/~chwolf/chwolf.asc > > Please respect my privacy and do not make my contact information > available to third parties. > <X11_001.jpg><X11_002.jpg><X11_003.jpg>

3 5

kmail 2
by Christof Wolf 28 Mar '10

28 Mar '10

Jeremy, the other thing I noticed, if I drag and drop anything in kmail, the mouse cursor is one line below the selected item. See screenshot. It did not happen before rc2 christof -- public key www.hfph.mwn.de/~chwolf/chwolf.asc Please respect my privacy and do not make my contact information available to third parties.

1 0

crazy behavior in kmail
by Christof Wolf 28 Mar '10

28 Mar '10

Jeremy, If I want to compose a new email and do not move the window of the composer everything seems fine. If I move it the thing goes crazy, I can't put anything in the To field, nor do the menus work properly. Sometimes if the pull down menu pops up, there is the bottom line missing. I have attached some screenshots :-) this just happend with the rc2 any idea? ciao christof -- public key www.hfph.mwn.de/~chwolf/chwolf.asc Please respect my privacy and do not make my contact information available to third parties.

1 0

Will you be making a Leopard version of rc2?
by Dave Ray 27 Mar '10

27 Mar '10

Will you be making a Leopard version of rc2?

2 1

Cancel my question: Will you be making a Leopard version of rc2?
by Dave Ray 27 Mar '10

27 Mar '10

Very sorry it's late. You already answered my question in your post.

1 0

XQuartz 2.5.0_rc2
by Jeremy Huddleston 27 Mar '10

27 Mar '10

I've uploaded an updated release candidate which addresses most of the reported issues brought up with rc1. Some of the issues which weren't terribly serious and aren't regressions will wait for 2.5.1. I only built a 2.5.0_rc2 package for SnowLeopard, so if you're on Leopard, you'll need to sit patient for the final release. If you're on SL, please update to 2.5.0_rc2 by using the "Check for X11 Updates" menu item or directly installing the pkg: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.5.0_rc2.dmg Some changes since 2.5.0_rc1: No longer building ppc bits into the libraries Fixed a modifier key issue with the 'Unicode Hex Input' keyboard layout Fixed an issue when the display layout changed /opt/X11/bin should come before /usr/X11/bin in $PATH Xephyr and Xnest should work better now Updated the installer to poke users to log out to make XQuartz.app default If there are any remaining issues, please let me know. Otherwise, this will likely become the released version. Thanks, Jeremy

1 2

Re: [Xquartz-dev] Bugfixes for 2.5.0_rc1
by Eeri Kask 22 Mar '10

22 Mar '10

Am 03/20/2010 03:00 PM, xquartz-dev-request(a)lists.macosforge.org schrieb: >> (1) Each time I log in (and launch X11) I am asked (sorry for sloppy >> English translation) something about ... "Do I want to allow remote >> applications to access X11, an option which can be tuned in firewall >> options too" ... or something. So each day in the office begins >> with a click on "yes, I do". How to automate this buttonclick? > > > My guess is that you have a 3rd party firewall installed, > and you should check that software. I'll take a look at it later, but the fact is, this behaviour appeared only a week ago after installing 2.5.0_rc1. (I am running OSX 10.5.8 --- each time I am even asked for a root password to make a change to somewhere but it apparently is discarded after each session.) >> (2) xmodmap, which in previous X11-versions configured some keys out >> of .xinitrc now doesn't do it from there anymore, out of no apparent >> reason. So each day in the office now begins with running this >> xmodmap by hand out of some xterm; e.g. in order to change >> left-alt-option from mode-switch back to Alt_L, and few others. How >> to revert this change? > > > xmodmap is run every time the key layout changes (including on startup). > There are internal issues which make it difficult to support the > old way. > As it is now, if you put your changes into ~/.Xmodmap, it should be run > whenever the keyboard layout gets updated (such as on startup). > My guess is you were doing this differently. If I remember correctly, Xorg 1.6.x (or 1.5.x, I don't know anymore) had this or analogous 'behaviour' too (i.e. on other OS'es than MacOSX) but after installing 1.7.x the 'old' behaviour appeared recovered which was a really good advancement. One of the problems with the above suggestion is, I don't know how to implement if test "Darwin" = "`uname -s`" then echo 'keycode 66 = Alt_L' | xmodmap - echo 'keycode 69 = Alt_R' | xmodmap - else echo 'keycode 115 = Meta_L' | xmodmap - echo 'keycode 116 = Meta_R' | xmodmap - fi and things like this by means of the $HOME/.Xmodmap file. >> (3) This is older bug: after logging in X11 starts xterm at >> top-left, despite the presence of ${HOME}/.xinitrc which is run too >> and sets up the session correctly. How to disable this xterm-starting? > > > 1) Please transition to using ~/.xinitrc.d rather than ~/.xinitrc, so you can inherit any fixes from us. > > 2) defaults write org.macosforge.xquartz.X11 app_to_run /usr/bin/true The variant (2) above would be the ultimate solution if it only worked on OSX-10.5.8... The problem with (1) is, that on all other OS'es I am working with the .xinitrc (which is NFS-mounted to everywhere here) method works well (and has always worked well), and they together out-vote OSX's method of now by their sole number. Nurturing two X11-startup methods in parallel is not favourable. >> (4) New bug: Starting remote X11 applications by >> >> ssh -f remotehost remote-application >> >> now apparently succeeds only with the first remote application, >> further applications often result in something like >> >> Warning: No xauth data; using fake authentication data >> for X11 forwarding. >> /usr/bin/xauth: error in locking authority file >> /home/eeri/.Xauthority >> X11 connection rejected because of wrong authentication. >> Error: cannot open display: localhost:11.0 > > > This works for me. It looks like your remote filesystem does not > support locking. I added a fix for that last year. > What version of libXau is installed on your remote system? > Try updating to libXau 1.0.3: The NFS-server (from where the $HOME filesystem comes from) has libXau 1.0.4 so it cannot be this. It looks like both ssh-parties access the same $HOME/.Xauthority file. Looking hypothetically, what happens if they both decide to exclusively lock that file, and proceed only if they both succeed, which cannot be achieved? >> (6) Some applications leave clutter on screen analogous to the bug I >> reported >> >> http://lists.freedesktop.org/archives/xorg/2008-August/037802.html >> >> but now without xcompmgr running. So it appears it is probably Xorg >> but not a compositing-extension issue... > > > Please file a bug report with your sample app (http://xquartz.macosforge.org) > > When did you start seeing this behavior? At that time 2008 I was not yet using MacOSX, and after reporting then I forgot about it. Now while upgrading to Xquartz 2.5.0_rc1 I was looking for something else but stepped in (this report and) that little program again. So I don't know if the bug is present in 2.4.x too. If it is helpful I'll put 2.4.0 back again and test. I'll tweak that little test program and then file a bug. >> (7) Something like once per week or few weeks the old server 2.4.? >> could be crashed by the ancient xless, if this has changed now >> remains to be observed. :-) > > > Do you recall the backtrace? Look in /Library/Logs/CrashReporter Here I count twenty crash-report-files to this bug since 2009-09-29, I'll pack them together and file a bug in few days. Greetings, Eeri Kask P.S. Now with 2.5.0_rc1 the xclipboard (i.e. cut+paste) works even across remote ssh-tunneled X11-applications which is really great, huge thanks! :-)

2 1