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

Re: [Xquartz-dev] 8bit (256) color
by Jeremy Huddleston 29 Aug '08

29 Aug '08

pixman is supposed to handle the translation from 8bit pixel values + mappings -> TrueColor On Aug 29, 2008, at 07:25, Brandon Allbery wrote: > On 2008 Aug 28, at 22:18, Jeremy Huddleston wrote: >> So this issue has been mentioned a few times on this list, and I've >> never really gotten a good test case to show off the problem. I'm >> heading to XDS next week, and I'd like to show off this bug to >> other X11 developers and maybe work with them to get towards a >> solution. > > I'm wondering how it's supposed to work at all, given that all the > visuals are 24-bit TrueColor. An application requesting 8-bit > PseudoColor should fail to find a compatible visual. > > -- > brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery(a)kf8nh.com > system administrator [openafs,heimdal,too many hats] allbery(a)ece.cmu.edu > electrical and computer engineering, carnegie mellon university > KF8NH > > > > _______________________________________________ > 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

Re: [Xquartz-dev] 2.3.1_rc3
by Jeremy Huddleston 29 Aug '08

29 Aug '08

On Aug 29, 2008, at 06:42, Jack Howarth wrote: > Jeremy, > My previous posting to the xquartz-dev list seems to have > gotten lost. Why exactly are you reintroducing libGLw back into > X11 on Leopard? I thought Apple explicitly removed libGLw > from X11 because they don't ship Motif. I decided to ship a version of libGLw that doesn't depend on Motif to satisfy those of you who were negatively affected by the lack of libGLw before. I would actually prefer not to ship it because I don't want to really be responsible for it, but it build in Mesa-7.1, and I remembered some people complaining about it being gone, so I decided to throw it into the rc and see if the fish bit. ;) > On fink, I have > created mesa-libglw packages using variants for lesstif, > openmotif3 and openmotif4. Since the headers used from > Motif by libGLw are not identical across the various motif > releases, Apple's original decision to depreciate out > libGLw was technically correct.You might want to rethink > the decision to reintroduce libGLw back into X11 on Leopard. > Jack This hasn't been shipped final yet (it's only in this RC). I'll pretty much leave it up to you all here in xquartz-dev... so if anyone has a reason to keep it in, speak up... otherwise it gets the boot for good. --Jeremy

1 0

8bit (256) color
by Jeremy Huddleston 29 Aug '08

29 Aug '08

So this issue has been mentioned a few times on this list, and I've never really gotten a good test case to show off the problem. I'm heading to XDS next week, and I'd like to show off this bug to other X11 developers and maybe work with them to get towards a solution. Can someone who is having problem with X11 applications needing 8bit color please report an easy-to-reproduce test-case of the problem in the bug report: http://xquartz.macosforge.org/trac/ticket/10 I'd like something that is easy to download and compile and run. Tell me the URL where I get the application and instructions on how to use it to trigger the issue. I don't want something like "Get IDL and make an image with it". I know people have mentioned IDL as a program that showcases this bug, so if that's your example, please provide me with the details. What to I run at the bash command line (and subsequent idl command lines) to trigger the bug? Even if I don't get to this next week, it would be nice to have a concrete reproducible testcase for me to use. Thanks, Jeremy

2 1

Fwd: Environment passed to Applications-launched processes
by Brian Bender 29 Aug '08

29 Aug '08

On Fri, Aug 29, 2008 at 9:34 AM, Harald Hanche-Olsen hanche-at-math.ntnu.no |Xquartz-dev/personal| <...> wrote: > I think the problem has nothing to do with what environment X11 gets, > but that your xterms aren't running a login shell. To make sure they > do, they must be started using xterm -ls or you need to have... Right, I know I can work around it. But it is a difference in behavior: launched processes usually inherit my fully set-up user environment, unless X11.app has been started directly from the application bundle (see my reply to myself about that). Thanks, - Brian -- Casey Stengel - "All right everyone, line up alphabetically according to your height."

1 0

2.3.x crashes: SwitchCoreKeyboard and NewCurrentScreen
by Jeremy Huddleston 22 Aug '08

22 Aug '08

I've uploaded an X11 build that includes some debugging information for the 2 reported crashes with 2.3.x (SwitchCoreKeyboard and NewCurrentScreen). If you are hitting either of these crashes, I urge you to install 2.3.1_rc1 and then replace /A/U/X11.app/Contents/MacOS/X11 with this: http://static.macosforge.org/xquartz/downloads/testing/SwitchCoreKeyboard-N… It does not fix the problem, but it will spit out useful debugging information to the system log before it crashes. If you are able to trigger either of these bugs, please download this build and report the messages sent to the system log when you crash. Thanks, Jeremy On Aug 20, 2008, at 08:17, Chris Linstid wrote: > It happens often enough to be annoying, but I haven't figured out > exactly > what I'm doing to trigger it yet. I'll give it a few more tries and > see > what I can find out. > > - Chris > > > On Wed, Aug 20, 2008 at 10:44 AM, Jeremy Huddleston <jeremyhu(a)apple.com > >wrote: > >> Are you able to reliably trigger this crash? You must be if you're >> reverting to 2.2.3. I have not once hit this. Can you please tell >> me >> what you do to trigger this bug reliably? If that fails, then I'll >> try >> putting together a special executable with additional debugging >> spew for you >> to try. >> >> Don't worry about X11 complaining about /usr/X11/share/X11/xkb not >> being >> there. I just haven't silenced that XKB message, but it's harmless. >> >> --Jeremy >> >> On Aug 19, 2008, at 15:25, Chris Linstid wrote: >> >> I'm actually hitting the same crash: >>> >>> However, when I went to remove /usr/X11/share/X11/xkb, I found >>> that that >>> directory didn't exist at all. So, I started looking through >>> console >>> messages and X11 is complaining about it missing: >>> >>> 8/19/08 6:17:32 PM [0x0-0xc40c4].org.x.X11[3071] (EE) XKB: >>> Couldn't open >>> rules file /usr/X11/share/X11/xkb/rules/base >>> >>> I'm running "XQuartz 2.3.1 (xorg-server 1.4.2-apple9)". >>> >>> I had been hitting this crash when 2.3.0 was initially released, >>> but since >>> I'm using X11 at work, I didn't have time to mess around with it >>> and it >>> crashed often enough that I couldn't continue using it (since all >>> my work >>> is >>> done in xterms ssh'ing into a Linux box), so I downgraded to 2.2.3. >>> >>> Any ideas for stuff I can try? >>> >>> For now, I'm going to downgrade to 2.2.3 again so I can continue >>> working. >>> :) >>> >>> Thanks. >>> >>> - Chris >>> >>> >>> On Sun, Aug 3, 2008 at 3:35 PM, Jamie Kennea <jamie(a)pompey.org> >>> wrote: >>> >>> >>>> On 3 Aug 2008, at 12:59 am, Jeremy Huddleston wrote: >>>> >>>> Just as a hunch, can you pleast try nukeing /usr/X11/share/X11/ >>>> xkb (just >>>> >>>>> move it somewhere else, so the server can't find it)? >>>>> >>>>> >>>> Sure I'l try that, but the crash hasn't reoccurred since I last >>>> emailed >>>> this list, so its not very repeatable. >>>> >>>> Jamie >>>> _______________________________________________ >>>> 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/clinstid%40gmail.com >>>> >>>> This email sent to clinstid(a)gmail.com >>>> >>>> _______________________________________________ >>> 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 >>> >> >> > _______________________________________________ > 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 3

2.3.1_beta2
by Jeremy Huddleston 21 Aug '08

21 Aug '08

This release fixes: the first-client-not-connecting bug I added in beta1 3-button mouse emulation stuck modifier keys (atleast all the ones I could reproduce) Please give it a whirl. I think this now tackles most of the major issues that surfaced after the 2.3.0 release. Thanks, Jeremy http://static.macosforge.org/xquartz/downloads/X11-2.3.1_beta2.pkg

9 21

'Screen sharing problem'
by Peter Collinson 21 Aug '08

21 Aug '08

My laptop and main machine are running 2.3.1 rc 1. If I screen share from my laptop to my main machine - I cannot get any control characters through to X apps on the main machine. Typing Ctrl-C on the laptop puts 'c' into an open xterm on the main machine. I think what is happening is KeyPress event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665126062, (78,117), root:(162,507), state 0x0, keycode 67 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: "" KeyRelease event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665127000, (78,117), root:(162,507), state 0x4, keycode 67 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: "" KeyPress event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665127000, (78,117), root:(162,507), state 0x0, keycode 16 (keysym 0x63, c), same_screen YES, XLookupString gives 1 bytes: "c" KeyRelease event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665127073, (78,117), root:(162,507), state 0x0, keycode 16 (keysym 0x63, c), same_screen YES, XLookupString gives 1 bytes: "c" This is from an xev running on the main machine. I didn't release the CTRL button when hitting the 'c'. It looks as if hitting the 'c' provokes a key up event. Odd.

3 4

2.3.1_rc1
by Jeremy Huddleston 18 Aug '08

18 Aug '08

As some of you are aware, after the release of 2.2.0, I decided to just announce release candidates to the xquartz-dev list and final releases to the x11-users list. With the release of 2.3.0, however, that release candidate process didn't catch some show-stopper issues. As a result, I've decided to announce "betas" to xquartz-dev and "rcs" to x11-users. These "rcs" are what I would've released under the old process (no show stoppers found in the releases announced to the xquartz-dev list), but this gives me an expanded user base to catch additional show stoppers before I announce a final update on the website and macupdate.com. I've just uploaded a release candidate for 2.3.1, and I urge everyone who experienced problems with 2.3.0 to give it a try. The following are the main issues addressed: * X11.app now properly notices button clicks with tablets * Fixed xinitrc / launchd-first-client race condition * Re-added old fallback keyboard map detection fallback with extra debugging * Capslock "press ignored" bug is fixed. * Fixed stuck modifier key bug * Fixed 3-button mouse emulation * The list of modifiers allowed in the fake_button{2,3} defaults has been expanded: o fn,{l,r,}{command,alt,shift,control} package: http://static.macosforge.org/xquartz/downloads/X11-2.3.1_rc1.pkg draft release notes: http://xquartz.macosforge.org/trac/wiki/X112.3.1 Thanks, Jeremy

2 4

1.4.2-apple9
by Jeremy Huddleston 17 Aug '08

17 Aug '08

I've just finished building and uploading 1.4.2-apple9. Install 2.3.1_beta2, then drop in this binary update. See http://xquartz.macosforge.org/trac/wiki/Releases#xorg-server for details. Here's the link: http://static.macosforge.org/xquartz/downloads/X11-1.4.2-apple9.bz2 This release addresses the following over 2.3.1_beta2: - Capslock "press ignored" bug is fixed. - modifier keys used to emulate button2/3 are not sent with the click/release - the list of modifiers allowed in the fake_button{2,3} defaults has been expanded: fn,{l,r,}{command,alt,shift,control} So if you want to be able to emulate command-button3 you can change fake_button3 to be fn and hold fn+command+button1. Or you can set it to lcommand and hold lcommand+rcommand+button1 ... hopefully this added flexibility will solve everyone's needs. Please try it out if you've been having modifier key or 3button emulation issues. Thanks, Jeremy

4 6

2.3.1_beta1
by Jeremy Huddleston 14 Aug '08

14 Aug '08

Hi All, I've put together a package containing all the bugfixes I've addressed since 2.3.0's release. Please try this package if you were experiencing any of the following: 1 - Tablet clicks weren't getting noticed 2 - Server doesn't start with certain keyboard layouts (READ BELOW!!!!) I also further addressed the xinitrc race condition with a nearly final solution, so you shouldn't see xterms without window frames any more. A note about the keyboard issue. This is not "fixed"! I simply readded some deprecated code that I had removed. It was a fallback/ failsafe in case the new way failed (which it was for some of you). If you look at the actual commit, you'll see that this code is in place for Leopard only... so we need to figure out the "real" solution for 10.6. If you were having this problem in 2.3.0, it'll probably work for you, but I need some of you to send me logs of the server startup with 2.3.1_beta1. You'll probably see something like this: X11.app: Error detected in determining keyboard layout. Please report this error at http://xquartz.macosforge.org X11.app: Debug Info: currentKeyLayoutRef=#####, chr_data=#### X11.app: Fallback succeeded, but this is still a bug. Please report the above information. X11.app: Debug Info: kKLuchrData fallback failed, trying kKLKCHRData. X11.app: Fallback succeeded, but this is still a bug. Please report the above information. If you see that, PLEASE PLEASE PLEASE report it on this list or in trac! http://static.macosforge.org/xquartz/downloads/X11-2.3.1_beta1.pkg Thanks, Jeremy

8 15