Bug 96416 - xemacs does not start: Error: Couldn't find per display information
Summary: xemacs does not start: Error: Couldn't find per display information
Status: RESOLVED FIXED
Alias: None
Product: XQuartz
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 2.7.9 (xserver-1.17.4)
Hardware: x86-64 (AMD64) Mac OS X (All)
: medium normal
Assignee: Jeremy Huddleston Sequoia
QA Contact: Jeremy Huddleston Sequoia
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-07 05:48 UTC by Gerd Aschemann
Modified: 2016-09-19 01:02 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Gerd Aschemann 2016-06-07 05:48:38 UTC
After installing the latest XQuartz (2.7.9) on OSX (10.8.5) I could not start my Fink based XEmacs (21.4) any longer. After short showing the screen it aborts with the error message 

  Error: Couldn't find per display information

Other X applications worked well. 
Downgrading to 2.7.8 solved the problem.
Comment 1 Jeremy Huddleston Sequoia 2016-06-07 06:34:51 UTC
Please test 2.7.10_beta2.  If the issue persists, please try the 2.7.9 betas and rcs and indicate which pre-release version was the first to introduce the problem.
Comment 2 mrahamgark 2016-06-13 21:20:59 UTC
Same problem. Mac OS X 10.11.5 (El Capitan).
Comment 3 Jeremy Huddleston Sequoia 2016-06-14 00:23:39 UTC
(In reply to mrahamgark from comment #2)
> Same problem. Mac OS X 10.11.5 (El Capitan).

If you are experiencing this issue, please provide some helpful information by responding to comment #1
Comment 4 Brian Jewett 2016-06-20 14:56:44 UTC
(In reply to Jeremy Huddleston Sequoia from comment #1)
> Please test 2.7.10_beta2.  If the issue persists, please try the 2.7.9 betas
> and rcs and indicate which pre-release version was the first to introduce
> the problem.

I had the same error message with a different application that previously worked (idt run locally on the mac).  Upgrading to 2.7.10_beta2 did not fix it.  

What does work:
  xclock run locally
  idt (interactive display tool) run remotely (TACC's stampede) displaying on my mac.

Odd.
Comment 5 Brian Jewett 2016-06-20 14:57:57 UTC
p.s. I am also running El Capitan 10.11.5
uname returns:
   Darwin rfd.atmos.uiuc.edu 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64
Comment 6 tjfarrell123 2016-07-12 03:14:43 UTC
I am also seeing this, running on MacOSX 10.10.5 (Yosemite), emacs 21.4.22 built by fink, running locally to DISPLAY :0.0.  Other X11 applications are ok.

I've worked through the various betas and RCs.

XQuartz 2.7.8 (xorg-server 1.16.4):  xemacs works.

XQuartz 2.7.9_beta1 (xorg-server 1.17.4).  Got a different error:

  =================================================================
  ==30305==ERROR: AddressSanitizer: global-buffer-overflow on address 0x00010118b120   at pc 0x0001014598f1 bp 0x7fff5fbfc790 sp 0x7fff5fbfc788
  READ of size 8 at 0x00010118b120 thread T0


xemacs did not exit or crash, but its window never appeared.


XQuartz 2.7.9_beta2 (xorg-server 1.17.4).  As per beta 1 above:

  =================================================================
  ==30976==ERROR: AddressSanitizer: global-buffer-overflow on address 0x00010118b120 at pc 0x0001013a7b70 bp 0x7fff5fbfd360 sp 0x7fff5fbfd358
  READ of size 8 at 0x00010118b120 thread T0
   

XQuartz 2.7.9_rc1 (xorg-server 1.17.4).   Had the problem as original reported:

    Error: Couldn't find per display information

The xemacs window does appear, and then disappears almost immediately
Comment 7 Jeremy Huddleston Sequoia 2016-09-18 23:37:42 UTC
I just built xemacs in MacPorts and launched it without issue with XQuartz 2.7.10_rc2 plus top-of-tree xserver.  Please try to reproduce with 2.7.10_rc2.  I'm guessing something has since fixed the issue.
Comment 8 Jeremy Huddleston Sequoia 2016-09-18 23:39:38 UTC
Re: the ASan reports, you've left out a ton of valuable data, but they're likely not bugs in XQuartz.  ASan is just helping you find bugs elsewhere.  You should report them on as appropriate.

The mis-filing of such bugs with XQuartz is a reason that I'm considering not building the X11 libraries with -fsanitize=address (just the main executables) in the next betas.
Comment 9 tjfarrell123 2016-09-19 01:02:06 UTC
Yes 2.7.10_rc2 fixed it for me.  (Running on Yosemite, 10.10.5)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.