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

Where's libGL
by Pelle Johansson 29 Jan '08

29 Jan '08

Hi, seems the list and the repository both went very quiet the same day as I signed up. Guess you're all to busy developing right? :) Anyway, I've noticed there's a few bugs in the libGL currently in Leopard, as well as the server. The sources for libGL came with Apple's X11 server package, so I was able to squish a few. Looking at the freedesktop mesa library it seems much updated, but lacks the Apple specific files (appledri.c). Is there anywhere I can find a more up to date package containing the Apple changes, can I replace it with the mesa library, or should I just stick to the one available from Apple? -- Pelle Johansson

3 8

quartz-wm decorations and 10.5 "look"
by robert delius royar 23 Jan '08

23 Jan '08

Are there plans to upgrade the window decorations (buttons and top curve radius) in quartz-wm so that X11 windows match the new style in 10.5. These are small details, but making the changes to the window manager would make the X11 windows look more like those for other programs. Where would be the best place to file such an enhancement request? I guess I mean what is the best way to phrase the request that it makes sense to the folks reading bugreport at Apple? -- Dr. Robert Delius Royar Associate Professor of English Morehead State University Morehead, Kentucky

3 2

MacUpdate Dev: XQuartz updated
by updates＠macupdate.com 21 Jan '08

21 Jan '08

Freedesktop.org, XQuartz 2.1.2 has just been updated to version 2.1.3 on MacUpdate. Check it out at: http://www.macupdate.com/info.php/id/26593/xquartz Please keep MacUpdate informed of any new Mac version releases of your products, so we can promote them for you. You can update your listing by signing up for a developer tools account: http://www.macupdate.com/developer/ Partner in our 24-hour promotion of your software through mupromo.com: http://www.mupromo.com/ -MacUpdate Team www.macupdate.com [You're being notified of this update because you're listed as the developer of XQuartz. Please email us if you are not the developer: updates(a)macupdate.com]

1 0

2.1.3 security release
by Jeremy Huddleston 18 Jan '08

18 Jan '08

So I just uploaded 2.1.3 and updated all the pages to reflect this release. It's the same as 2.1.3-rc1 that I released two days ago in response to the X.org security advisement. Release notes and links to the security advisement are on the release page: http://trac.macosforge.org/projects/xquartz/wiki/X112.1.3 --Jeremy

1 0

2.1.3-rc1
by Jeremy Huddleston 18 Jan '08

18 Jan '08

X.org just released a security advisory this morning pertaining to certain vulnerabilities in xserver and libXfont (I don't have a link since it's not hit the list archives yet). I am 100% certain we are vulnerable to at least one, and I know we are not vulnerable to at least one. Rather than spend time verifying which we are vulnerable to and which we aren't, I decided to just integrate all the patches (except where I was 100% certain we were not affected) and push out the update. Here are the release notes: http://trac.macosforge.org/projects/xquartz/wiki/X112.1.3 Here is the pkg: http://xquartz.macosforge.org/downloads/X11-2.1.3-rc1.pkg Please test and get back to me. --Jeremy

2 1

Re: X11 2.1.2 freeze with IDL 7.0
by Jeremy Huddleston 17 Jan '08

17 Jan '08

This looks interesting. Can you pleas file a bug report at xquartz.macosforge.org. It looks like it might be a libXplugin issue (so file a bug at bugreport.apple.com as well). Just judging by the top of the stacks, it looks like a deadlock in libXplugin. > 31 > _xp_configure_surface + 31 (in libXplugin.1.dylib) [0x315df5] > 31 __xp_synchronize + > 81 (in libXplugin.1.dylib) [0x310d8e] > 31 > __xp_async_dequeue + 41 (in libXplugin.1.dylib) [0x310cbe] > 31 > ___semwait_signal + 10 (in libSystem.B.dylib) [0x91c38ace] > 31 _xp_configure_window + 1829 (in libXplugin. > 1.dylib) [0x318714] > 31 __xp_do_request + 410 (in libXplugin. > 1.dylib) [0x310fcd] > 31 __xp_synchronize + 81 (in libXplugin. > 1.dylib) [0x310d8e] > 31 __xp_async_dequeue + 41 (in libXplugin. > 1.dylib) [0x310cbe] > 31 ___semwait_signal + 10 (in > libSystem.B.dylib) [0x91c38ace] On Jan 15, 2008, at 06:23, Ricardo Fonseca wrote: > Hi guys > > I'm having problems with IDL 7.0 running under the new X11. Things > have improved greatly with the recent upgrades, but X11.app freezes > more or less randomly, as it did in X11 2.1.1. You can trigger this > freeze if you resize a window 10-20 times. > > Freeze details are below. (Not sure if this is relevant, but IDL > seems to be Motif based - libXm.3.0.2.dylib). Everything works fine > under the old X11. Any thoughts? > > Cheers, Ricardo > > -- > > Date/Time: 2008-01-15 13:59:40 +0000 > OS Version: 10.5.1 (Build 9B18) > Architecture: i386 > Report Version: 4 > > Command: X > Path: /usr/X11/bin/X > Version: ??? (???) > Parent: xinit [707] > > PID: 708 > Event: hang > Time: 7.45s > Steps: 31 > > > Process: X [708] > Path: /usr/X11/bin/X > > ADDRESS BINARY > 00001000 /usr/X11/bin/X > 001f3000 /usr/X11/lib/libXfont.1.dylib > 00268000 /usr/X11/lib/libfreetype.6.dylib > 002fa000 /usr/X11/lib/libXau.6.dylib > 002ff000 /usr/X11/lib/libfontenc.1.dylib > 00309000 /usr/X11/lib/libXdmcp.6.dylib > 00310000 /usr/lib/libXplugin.1.dylib > 0cf31000 /System/Library/CoreServices/RawCamera.bundle/ > Contents/MacOS/RawCamera > > Thread id: 4cf5000 > User stack: > 31 start + 54 (in X) [0x2b76] > 31 _main + 59 (in X) [0x7c30b] > 31 _DarwinHandleGUI + 324 (in X) [0x1a404] > 31 _X11ApplicationMain + 693 (in X) [0xf125] > 31 -[NSApplication run] + 847 (in AppKit) [0x94cf1705] > 31 -[X11Application sendEvent:] + 313 (in X) [0xf579] > 31 _RootlessReorderWindow + 208 (in X) [0x21a40] > 31 _xprRestackFrame + 66 (in X) [0x4eb2] > 31 _xp_configure_window + 1829 (in libXplugin. > 1.dylib) [0x318714] > 31 __xp_do_request + 410 (in libXplugin. > 1.dylib) [0x310fcd] > 31 __xp_synchronize + 81 (in libXplugin. > 1.dylib) [0x310d8e] > 31 __xp_async_dequeue + 41 (in libXplugin. > 1.dylib) [0x310cbe] > 31 ___semwait_signal + 10 (in > libSystem.B.dylib) [0x91c38ace] > Kernel stack: > 5 _deflate_copyright + 2951 [0x3da847] > 5 _cnopen + 114 [0x379289] > 5 _task_create_internal + 667 [0x1397e6] > 5 _task_create_internal + 264 [0x139653] > 5 _stack_alloc_try + 72 [0x1368fe] > 5 _stack_free_stack + 70 [0x13685a] > 5 _thread_stop + 299 [0x135d3a] > 5 _machine_thread_create + 297 [0x1a1aab] > > Thread id: 3c018b8 > User stack: > 31 _thread_start + 34 (in libSystem.B.dylib) [0x91c61f32] > 31 __pthread_start + 321 (in libSystem.B.dylib) [0x91c62075] > 31 _server_thread + 51 (in X) [0x1a2b3] > 31 _main + 1121 (in X) [0x7c731] > 31 _Dispatch + 405 (in X) [0x6dc55] > 31 _ProcConfigureWindow + 145 (in X) [0x67001] > 31 _ConfigureWindow + 2900 (in X) [0x88a74] > 31 _RootlessResizeWindow + 334 (in X) [0x2352e] > 31 _miSlideAndSizeWindow + 3245 (in X) [0x486bd] > 31 _DRIValidateTree + 76 (in X) [0x3dac] > 31 _RootlessValidateTree + 173 (in X) [0x1f68d] > 31 _miValidateTree + 638 (in X) [0x40e0e] > 31 _miComputeClips + 1219 (in X) [0x40713] > 31 _miComputeClips + 1219 (in X) > [0x40713] > 31 _miComputeClips + 1219 (in X) > [0x40713] > 31 _miComputeClips + 1219 (in X) > [0x40713] > 31 _miComputeClips + 1219 (in X) > [0x40713] > 31 _miComputeClips + 1219 (in > X) [0x40713] > 31 _miComputeClips + 898 (in > X) [0x405d2] > 31 _DRIClipNotify + 86 (in > X) [0x3eb6] > 31 _DRIUpdateSurface + 95 > (in X) [0x363f] > 31 > _xp_configure_surface + 31 (in libXplugin.1.dylib) [0x315df5] > 31 __xp_synchronize + > 81 (in libXplugin.1.dylib) [0x310d8e] > 31 > __xp_async_dequeue + 41 (in libXplugin.1.dylib) [0x310cbe] > 31 > ___semwait_signal + 10 (in libSystem.B.dylib) [0x91c38ace] > > > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > X11-users mailing list (X11-users(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/jeremyhu%40freedesktop.org > > This email sent to jeremyhu(a)freedesktop.org

2 2

2.1.2 released
by Jeremy Huddleston 14 Jan '08

14 Jan '08

It's basically the same as the last rc, but I added in a 'login_shell' option that users of tcsh can set to '/bin/tcsh' so applications launched from the Applications menu get the tcsh environment instead of the bash environment: defaults write org.x.X11 login_shell /bin/tcsh http://trac.macosforge.org/projects/xquartz/wiki/X112.1.2 --Jeremy

6 14

X11-2.1.2-rc5
by Jeremy Huddleston 12 Jan '08

12 Jan '08

Ok, I believe I killed off the annoying xauth bug which was the big show-stopper in the way of a 2.1.2 release. Please try out the latest rc, and hopefully we can push this out this weekend. http://xquartz.macosforge.org/downloads/X11-2.1.2-rc5.pkg Cheers, Jeremy

2 2

Re: [Xquartz-dev] 2.1.2 release candidate
by Jeremy Huddleston 12 Jan '08

12 Jan '08

I think I'm just going to release the 'bash --login startx' launchd.plist with startx pushing /usr/X11/bin into PATH if it's not there already. This doesn't assume your users will use bash. It just uses bash because it's there. When the users start xterm from the Applications menu, they'll get their tcsh shell as expected, and they'll get a login tcsh shell because it's started by '/usr/bin/login -fp <username> /usr/X11/bin/xterm' which tells xterm to be a login terminal which tells the shell to be a login shell. Other applications (maybe 'xemacs' as an example) will inherit the BASH environment provided to them. I honestly don't see an easy, robust, clean solution for this, and the 'bash --login' route is what I came up with as the cleanest one, but it provides the BASH environment. Your users could probably change /System/Library/ org.x.X11.plist to something better for their tcsh setup... or even just start a terminal and execute something from there... Now that I think about it, I don't see how this is even a regression. Are you absolutely positive that XQuartz is even getting your tcsh environment with 2.1.1 (or any previous version)? I don't think it should be. You can test this by: mkdir ~/tcsh_only_bin echo "/usr/X11/bin/xterm" > ~/tcsh_only_bin/tcsh_xterm chmod 755 ~/tcsh_only_bin/tcsh_xterm <edit ~/.login ~/.cshrc or whatnot to put ~/tcsh_only_bin in $PATH> restart X Add 'tcsh_only_bin' to the Applications menu (without the full path) Launch that menu item. My bet is that it won't work as I don't believe it should be getting the environment currently. Can you please check that out for me? --Jeremy On Jan 9, 2008, at 06:51, Jamie Kennea wrote: > > On Jan 9, 2008, at 2:55 AM, Martin Costabel wrote: > >> For people who don't have bash as their login shell, this is a >> regression. > > Assuming people are going to use bash is troublesome. Most of our > users are set up to use tcsh, the policy which is set by our LDAP > server which we use to authenticate our users on Linux and Mac. I > know Macs default to bash, but one shouldn't assume the default is > kept, especially in environments like ours. > > Jamie

2 1

Re: 2.1.2 release candidate
by Peter Dyballa 11 Jan '08

11 Jan '08

Am 10.01.2008 um 23:25 schrieb Martin Costabel: > What I care about is the environment transmitted to the programs > run by > the Applications menu of X11. It worked for you, Martin, because you had set up a reasonable environment with ~/.MacOSX/environment.plist. (For next login you can just rename the file.) This one was passed to the clients. And some clients, like xterm, are allowed to launch with a login shell or a shell like in Terminal. Without ~/.MacOSX/environment.plist X clients have only a very rudimentary environment. With some trickery you can have some success – but texdoctk will never run and work completely. This finally made me create my little suite of scripts. -- Greetings Pete The light at the end of the tunnel has been turned off due to budget cuts.

2 1