• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: running legacy xview X11 applications via terminal app vs xterm
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: running legacy xview X11 applications via terminal app vs xterm


  • Subject: Re: running legacy xview X11 applications via terminal app vs xterm
  • From: Jeremy Huddleston <email@hidden>
  • Date: Mon, 21 Mar 2011 17:28:54 -0700

On Mar 21, 2011, at 17:05, Frank Delaglio wrote:

> I would have guessed that the problem is caused by environment variable
> settings relating to one of the issues above.  But as our users have noted,
> resetting environment variables does not seem to help.

What do they mean "resetting environment variables"?  Can you please provide the output of 'env' in the working or not-working case.  This really sounds like an environment issue, and I wouldn't be so quick to accept your users claims that it is not.

> The last adjustment to our Mac OS X version of XView
> was made around July 2010.  At that time, the XQuartz folks released
> three versions of X11 in about 30 days.

Right.  That was due to a slew of security advisories released by freetype and the png project, but as far as your code is concerned, those three versions (2.5.1 through 2.5.3) should look pretty much the same.

> Our XView adjustment involved
> replacing multiple calls to XAllocID() with a single call to XAllocIDs()
> to fix a crash which manifested in xcb_io().  This was not unexpected,
> we had to make this same XView fix earlier for linux implementations of X11.

Yeah, this was because 2.5.1 was the version that started building libX11 with --with-xcb, thus exposing the same bug in XView that was exposed on Linux.

> The crash log includes libXau ... is it possible that there is some
> difference in the X11 authorization environments for xterm and
> Terminal.app?

They should be using the launchd socket, which doesn't use xauth.

Still, all this would be much cleared if we could see the output of 'env' for a working and non-working case and work from there...

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list      (email@hidden)

This email sent to email@hidden

  • Follow-Ups:
    • Re: running legacy xview X11 applications via terminal app vs xterm
      • From: Ben Eisenbraun <email@hidden>
References: 
 >Re: running legacy xview X11 applications via terminal app vs xterm (From: Frank Delaglio <email@hidden>)

  • Prev by Date: Re: running legacy xview X11 applications via terminal app vs xterm
  • Next by Date: (no subject)
  • Previous by thread: Re: running legacy xview X11 applications via terminal app vs xterm
  • Next by thread: Re: running legacy xview X11 applications via terminal app vs xterm
  • Index(es):
    • Date
    • Thread