Bug 95359 - XQuartz won't launch xterm
Summary: XQuartz won't launch xterm
Status: RESOLVED NOTABUG
Alias: None
Product: XQuartz
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 2.7.8 (xserver-1.16.4)
Hardware: Other Mac OS X (All)
: medium blocker
Assignee: Jeremy Huddleston Sequoia
QA Contact: Jeremy Huddleston Sequoia
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-12 00:47 UTC by Jesse
Modified: 2016-05-12 16:05 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Jesse 2016-05-12 00:47:09 UTC
I recently upgraded to El Capitan on my MacBook Pro (Intel Core i5). Sometime afterward (but I don't think at the same time), XQuartz stopped launching xterm. I can still launch xman and xlogo, but when I launch the package the usual default xterm doesn't show up, and when I choose xterm from the Applications menu nothing happens.

I'm running OS X 10.11.3, and XQuartz 2.7.9 (xorg-server 1.17.4).

Following a suggestion I saw on bug ID 95204, I tried typing "/Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin" into a terminal window. If XQuartz isn't running already, this just hangs. If XQuartz is running, nothing happens -- I get my prompt back immediately, but there's no other response.

I don't have a ~/.profile or ~/.bash_profile file, and I haven't done anything that I know of to change the OS X default shell.

I'm pasting an excerpt from /var/log/system.log that appears when I try to launch xterm from within XQuartz:

May 11 17:43:27 --- last message repeated 1 time ---
May 11 17:43:27 jesses-mbp org.macosforge.xquartz.startx[32030]: /opt/X11/bin/xinit: XFree86_VT property unexpectedly has 0 items instead of 1
May 11 17:43:29 jesses-mbp com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.501): Service "com.apple.xpc.launchd.unmanaged.X11.bin.32071" tried to hijack endpoint "org.macosforge.xquartz.X11" from owner: org.macosforge.xquartz.X11.113312
May 11 17:43:30 --- last message repeated 1 time ---
May 11 17:43:30 jesses-mbp WindowServer[170]: send_datagram_available_ping: pid 439 failed to act on a ping it dequeued before timing out.
May 11 17:43:46 --- last message repeated 1 time ---
May 11 17:43:46 jesses-mbp WindowServer[170]: _CGXRemoveWindowFromWindowMovementGroup: window 0x7baf is not attached to window 0x7bb8
May 11 17:44:05 jesses-mbp CalendarAgent[354]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]
May 11 17:44:29 --- last message repeated 1 time ---
May 11 17:44:29 jesses-mbp WindowServer[170]: send_datagram_available_ping: pid 439 failed to act on a ping it dequeued before timing out.
May 11 17:45:12 --- last message repeated 1 time ---
May 11 17:45:17 jesses-mbp WindowServer[170]: send_datagram_available_ping: pid 439 failed to act on a ping it dequeued before timing out.
May 11 17:45:27 jesses-mbp WindowServer[170]: send_datagram_available_ping: pid 439 failed to act on a ping it dequeued before timing out.
Comment 1 Jeremy Huddleston Sequoia 2016-05-12 06:45:28 UTC
> I tried typing "/Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin" into a terminal

Don't do that.  That was a bad suggestion or was misunderstood.

Launch Terminal.  Try spawning xterm from it.  What happens?
Comment 2 Jesse 2016-05-12 16:05:39 UTC
(In reply to Jeremy Huddleston Sequoia from comment #1)
> > I tried typing "/Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin" into a terminal
> 
> Don't do that.  That was a bad suggestion or was misunderstood.
> 
> Launch Terminal.  Try spawning xterm from it.  What happens?

Thank you. Surely it was misunderstood.

Your suggestion worked -- I was able to spawn xterm from Terminal, with a few seconds delay. And then once I'd done that, I was then able to spawn it from XQuartz as well. I'm not sure what happened, or whether this will "stick," but it seems fixed for now. Thanks!


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.