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

XQuartz 2.5.0_rc1
by Christof Wolf 16 Mar '10

16 Mar '10

Jeremy, I have the exact same problem updating like Brian, the dmg file works fine :-) 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.

2 1

System X11 binaries in path ahead of XQuartz
by Adam Mercer 16 Mar '10

16 Mar '10

Hi Just installed the 2.5.0rc1 on SL and found a minor annoyance. The binaries from the system X11 are in the path ahead of the XQuartz binaries: $ which xterm /usr/X11/bin/xterm $ echo $PATH /Users/ram/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/opt/X11/bin $ The DISPLAY variable is correctly set: $ echo $DISPLAY /tmp/launch-3ESeJo/org.macosforge.xquartz:0 $ I imagine that this is due to path_helper reading the files in /etc/paths.d in alphabetical order, as renaming /etc/paths.d/XQuartz to 00XQuartz, for example, results in the XQuartz binaries ahead of the system X11 binaries in the path. I can do this manually but I wonder if this should be done in the installer, otherwise the system X11 binaries are going to be used? Cheers Adam

2 2

Re: [Xquartz-dev] XQuartz 2.5.0_rc1
by Jeremy Huddleston 16 Mar '10

16 Mar '10

Hi Doug. This is probably due to some of the XKB changes. Would you mind filing a bug report at http://xquartz.macosforge.org ... I'll take a look at it before finally releasing 2.5.0. Thanks, Jeremy On Mar 16, 2010, at 08:34, Doug Carter wrote: > > Excellent work Jeremy! > > I just installed via the dmg and it *seems* a lot faster. > > I did find a little bug, that I haven't be able to sort out yet... > > Running xset to disable the bell isn't working. I've tried: > > xset -b > xset b off > xset b 0 > > I've also tried the xset client from 2.4 and it doesn't work either. I've > checked the logs and don't see any errors. It's been awhile since I've > done any X11 development and I've never done any development with X on > a Mac. Any clues on how to debug this? > > NB: xset does work, I was able to rehash the font path successfully. > > Thanks, > > Doug > > > On Mon, Mar 15, 2010 at 11:59:06PM -0700, Jeremy Huddleston wrote: >> We've come a long way since 2.4.0 was released, and the end of the road is in sight for 2.5.0. 2.5.0_rc1 looks quite solid, and I'd like to get more people using it. This is the first pre-release of 2.5.0 that has been built for both Leopard and SnowLeopard. The Leopard version still installs to /usr/X11 and X11.app while the SL version installs to /opt/X11 and XQuartz.app to avoid the Software Update collisions that were so common in the Leopard days. >> >> With this release, I've created a separate Software Update feed that will contain beta versions (as well as final release versions). To switch to this feed rather than the final-release feed, please execute the following: >> >> SnowLeopard: >> defaults write org.macosforge.xquartz.X11 SUFeedURL http://static.macosforge.org/xquartz/downloads/sparkle/beta.xml >> >> Leopard: >> defaults write org.x.X11 SUFeedURL http://static.macosforge.org/xquartz/downloads/sparkle/beta.xml >> >> Assuming you have 2.4.0 on Leopard or one of the earlier 2.5.0 betas for SL, you should see an auto-update notification the next time you start X11 after running the above command. If you don't want to use the SU, you can just download the installer from these links: >> >> SnowLeopard: >> http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.5.0_rc1.dmg >> >> Leopard: >> http://static.macosforge.org/xquartz/downloads/Leopard/X11-2.5.0_rc1.dmg >> >> The full ChangeLog from 2.4.0 can be seen in the draft release notes: >> http://xquartz.macosforge.org/trac/wiki/X112.5.0 >> >> Please hammer this release. I feel confident that it is release quality, but I want to get a wider audience first. >> >> Thanks, >> Jeremy >> > > > >> _______________________________________________ >> 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/dcarter%40mercycorps.org >> >> This email sent to dcarter(a)mercycorps.org > _______________________________________________ > 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

1 0

wacom bug
by Christof Wolf 12 Mar '10

12 Mar '10

On Friday 12 March 2010, xquartz-dev-request(a)lists.macosforge.org wrote: > Can you run 'xinput test pointer' while doing this and observe the output > in that terminal. Jeremy, It's crazy, I cannot even reproduce the message: "You have to enter something in the email address field" Sometimes I can select, sometimes not, sometimes I can scroll down, sometimes not - I have tried different things, but there seems no system behind it. Though I observed one thing, if one pull down menu remains open, because I cannot pick up an email address with the pen, all windows under KDE are frozen - I have to click in the X11 menu, open a terminal, when I put any character in - that character is written in the last focused KDE window and every window is working again. I did, not sure if that helps, because I could net get the error message again. bash-3.2$ xinput test pointer motion a[0]=345 a[1]=809 motion a[0]=345 a[1]=809 motion a[0]=345 a[1]=809 motion a[0]=837 a[1]=680 motion a[0]=837 a[1]=680 motion a[0]=837 a[1]=680 motion a[0]=837 a[1]=680 motion a[0]=647 a[1]=669 motion a[0]=647 a[1]=669 motion a[0]=790 a[1]=673 motion a[0]=790 a[1]=673 motion a[0]=790 a[1]=673 motion a[0]=790 a[1]=673 motion a[0]=737 a[1]=510 motion a[0]=737 a[1]=510 motion a[0]=737 a[1]=510 motion a[0]=737 a[1]=510 motion a[0]=1623 a[1]=603 motion a[0]=1623 a[1]=603 motion a[0]=663 a[1]=614 motion a[0]=663 a[1]=614 motion a[0]=635 a[1]=505 motion a[0]=635 a[1]=505 motion a[0]=718 a[1]=682 motion a[0]=718 a[1]=682 motion a[0]=718 a[1]=682 motion a[0]=718 a[1]=682 motion a[0]=1138 a[1]=602 motion a[0]=1138 a[1]=602 motion a[0]=1590 a[1]=591 motion a[0]=1590 a[1]=591 motion a[0]=1590 a[1]=591 motion a[0]=1590 a[1]=591 motion a[0]=1590 a[1]=591 motion a[0]=1590 a[1]=591 motion a[0]=1590 a[1]=591 motion a[0]=1590 a[1]=591 motion a[0]=1590 a[1]=591 motion a[0]=1590 a[1]=591 motion a[0]=704 a[1]=604 motion a[0]=704 a[1]=604 motion a[0]=638 a[1]=596 motion a[0]=638 a[1]=596 motion a[0]=638 a[1]=596 motion a[0]=638 a[1]=596 motion a[0]=728 a[1]=627 motion a[0]=728 a[1]=627 motion a[0]=967 a[1]=863 motion a[0]=967 a[1]=863 motion a[0]=840 a[1]=520 motion a[0]=841 a[1]=520 motion a[0]=782 a[1]=525 motion a[0]=782 a[1]=525 motion a[0]=628 a[1]=486 motion a[0]=628 a[1]=486 motion a[0]=412 a[1]=1177 motion a[0]=412 a[1]=1177 motion a[0]=612 a[1]=1177 motion a[0]=612 a[1]=1177 motion a[0]=27 a[1]=1151 motion a[0]=27 a[1]=1151 motion a[0]=339 a[1]=880 motion a[0]=339 a[1]=880 motion a[0]=2 a[1]=1121 motion a[0]=2 a[1]=1121 motion a[0]=193 a[1]=1054 motion a[0]=193 a[1]=1054 motion a[0]=358 a[1]=907 motion a[0]=358 a[1]=907 motion a[0]=834 a[1]=775 motion a[0]=834 a[1]=775 motion a[0]=751 a[1]=520 motion a[0]=543 a[1]=573 motion a[0]=543 a[1]=573 motion a[0]=543 a[1]=573 motion a[0]=543 a[1]=573 motion a[0]=729 a[1]=459 motion a[0]=729 a[1]=459 motion a[0]=729 a[1]=459 motion a[0]=729 a[1]=459 motion a[0]=706 a[1]=507 motion a[0]=706 a[1]=507 motion a[0]=524 a[1]=177 motion a[0]=524 a[1]=177 motion a[0]=524 a[1]=177 motion a[0]=524 a[1]=177 motion a[0]=524 a[1]=177 motion a[0]=524 a[1]=177 motion a[0]=1289 a[1]=747 motion a[0]=1289 a[1]=747 motion a[0]=1694 a[1]=1026 motion a[0]=1694 a[1]=1026 motion a[0]=332 a[1]=752 motion a[0]=40 a[1]=128 motion a[0]=40 a[1]=128 motion a[0]=132 a[1]=787 motion a[0]=132 a[1]=787 motion a[0]=41 a[1]=23 motion a[0]=41 a[1]=23 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

wacom bug
by Christof Wolf 11 Mar '10

11 Mar '10

Jeremy, Sorry, I was quite busy, I haven't followed up with the wacom bug, which I reported earlier - but I realized it's still the same (I cannot pick an email address from the drop down list in kmail using the pen, any mouse and even the wacom mouse is fine) - I use SL & 2.5.0 beta2. I've started kmail from a terminal: maybe the output helps. christof -----------------------snip-------------------------------------------- bash-3.2$ kmail: FOO: 1744851117 :: 0x3500810 kmail: Folder found: 0x3500650 kdecore (KConfigSkeleton): Creating KConfigSkeleton (0xbfffd10c) kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Input: aStr Error:You have to enter something in the email address field. kmail: Identity found: 1744851117 kdecore (KConfigSkeleton): Creating KConfigSkeleton (0xbfffd10c) kmail: Command: REM= kmail: Command: - kmail: Command: BLANK kmail: CharFreq returned 4/0 and I chose 7bit kmail: FOO: 1744851117 :: 0x3500810 kmail: KMComposeWin::slotUpdateFont kmail: KMComposeWin::readConfig. ch.wolf(a)lp-muc.com kmail: [QTextCodec* KCharsets::codecForName(const QString&, bool&) const] kmail: Trying to find IBM852 in /usr/share/i18n/charmaps kmail: KMComposeWin::slotUpdateFont kmail: setting PlainText editor kmail: KMComposeWin::rethinkFields kmail: KMComposeWin::rethinkFields kmail: [void KMComposeWin::initAutoSave()] kmail: KMComposeWin::setTransport( "loyolaproductions.com" ) kmail: transport found, it's no. 8 in the list kmail: KMComposeWin::rethinkFields kmail: + Text/Plain kmail: ObjectTreeParser::parseObjectTree( node OK, showOnlyOneMimePart: FALSE ) kmail: partNode::findType() is looking at Text/Plain kmail: KDictSpellingHighlighter::slotSpellReady( 0x4ae2480 ) kmail: KDictSpellingHighlighter::slotRehighlight() kmail: KDictSpellingHighlighter::slotRehighlight() -- public key www.hfph.mwn.de/~chwolf/chwolf.asc Please respect my privacy and do not make my contact information available to third parties.

2 1

XQuartz 2.5.0 beta2 bug...
by John Sutherland 10 Mar '10

10 Mar '10

Hi all.. I just recently stumbled onto a beta bug I'd like to make you aware of.. I run on a up to date Snow Leopard MPB.. I installed the beta last night.. I switch between just the laptop, and having an external monitor plugged in regularly.. When the second monitor is plugged in, I have the external set to the right of the main screen, and set as the "main" screen (the dock and menubar appear on the external montior).. I was using laptop without the external last night, and had X11 running when I put the machine to sleep.. This morning, I opened the laptop, then plugged the external monitor in, and fired up my editor (SlickEdit).. It came up on the laptop screen, which I expected, because that was the last location I used it... But when I attempted to drag it to the external monitor, it just stopped at the edge... I could see part of the window on the external, just where ever I grabbed the window with the mouse, thats the last pixel that would drag over. I couldn't click on the window in the external monitor and have it get focus at all. During this time, I also started a Terminal.app session, and ran xeyes to see what would happen... the xeyes window appeared on the external monitor, but I could not click on the window at all.. It was completely ignoring any mouse clicks, and could not get focus.. The 3 buttons on the title bar just stayed grayed... I was able to click on the SlickEdit window without issue, though still stuck on the laptop screen.. I ended up using "kill xeyes" to get rid of the window.. At this point, I closed my slickedit window, and restarted X.. At this point, things returned to normal... Started Slickedit, and was able to move it where ever I wanted.. I suspect somehow X11 didn't get the message about the new screen size... I've tried to duplicate this by unplugging/plugging the monitor a few times, but haven't been able to.. I suspect it may have something to do with putting the machine sleep.. Or how quickly I plugged in the monitor after waking.. I never saw this with the older X11. (I believe I was running stock since I installed SL.) Its not a huge deal, I don't mind restarting X if I have to.. Just wanted to point this out.. --John

2 1

pymol launches slower under Xquartz/MacPorts X11
by Jack Howarth 06 Mar '10

06 Mar '10

Jeremy, I have noticed an oddity in the launch behavior of X11 pymol when built against the newer Xorg from MacPorts under Xquartz 2.5.0-beta2. If you install pymol from MacPorts and launch it by executing pymol on the terminal, the Pymol viewer window will appear almost immediately but there is very long delay before the upper Pymol tk interface window appears. This contrasts to launching the fink pymol package on the same machine with Xquartz installed. In the fink case, the initial startup of pymol shows a much smaller delay between the appearance of the Pymol viewer window and the Pymol Tk interface window. Since both are running under Xquartz, I assume the difference in launch time is due to the X11 libraries in use. For fink pymol this is... [Macintosh-2:pymol-py26/modules/pymol] howarth% otool -L _cmd.so _cmd.so: /sw/lib/libfreeglut.3.dylib (compatibility version 12.0.0, current version 12.0.0) /usr/X11/lib/libGL.1.dylib (compatibility version 1.2.0, current version 1.2.0) /usr/X11/lib/libGLU.1.dylib (compatibility version 1.3.0, current version 1.3.0) /sw/lib/libpng12.0.dylib (compatibility version 36.0.0, current version 36.0.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0) /usr/X11/lib/libX11.6.dylib (compatibility version 9.0.0, current version 9.0.0) /usr/X11/lib/libXext.6.dylib (compatibility version 11.0.0, current version 11.0.0) but for MacPorts pymol, this is... [Macintosh-2:pymol/modules/pymol] howarth% otool -L _cmd.so _cmd.so: /opt/local/lib/libglut.3.dylib (compatibility version 3.7.0, current version 3.7.0) /opt/local/lib/libGL.1.dylib (compatibility version 1.2.0, current version 1.2.0) /opt/local/lib/libGLU.1.dylib (compatibility version 1.3.0, current version 1.3.0) /opt/local/lib/libpng12.0.dylib (compatibility version 41.0.0, current version 41.0.0) /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.0.0) /opt/local/lib/libX11.6.dylib (compatibility version 10.0.0, current version 10.0.0) /opt/local/lib/libXext.6.dylib (compatibility version 11.0.0, current version 11.0.0) I'll see if I can eliminate this regression by building MacPorts pymol against a MacPorts freeglut package instead of stock libglut from Mesa used in MacPorts. Jack ps This slow launch has been seen before on linux... http://www.mail-archive.com/pymol-users@lists.sourceforge.net/msg05243.html. Note that this is a delay on first launch of pymol and not successive launches for that session.

1 1