x11 (xterm) does not start, no window appears

  • Follow


Hi,

I have Leopard and I installed X11 from the Leopard installation DVD.

So, I can just type xterm in the terminal, and it will start X11 and
xterm, right? But it doesn't work here. It's a fresh Leopard
installation. When I type xterm nothing happens. When I look at top it
shows that X11 and xterm are being executed, but no window shows up.

Am I missing something?

Thanks!
Markus
0
Reply markus.dehmann (142) 2/26/2008 3:05:06 PM

On Tue, 26 Feb 2008 07:05:06 -0800 (PST), Markus Dehmann wrote:
> Hi,

> I have Leopard and I installed X11 from the Leopard installation DVD.

> So, I can just type xterm in the terminal, and it will start X11 and
> xterm, right? But it doesn't work here. It's a fresh Leopard
> installation. When I type xterm nothing happens. When I look at top it
> shows that X11 and xterm are being executed, but no window shows up.

> Am I missing something?

> Thanks!
> Markus

You need to launch X11.app (in /Applications/Utilities).  


-- 
Dave Seaman
Oral Arguments in Mumia Abu-Jamal Case heard May 17
U.S. Court of Appeals, Third Circuit
<http://www.abu-jamal-news.com/>
0
Reply dseaman (1172) 2/26/2008 3:27:57 PM


Markus Dehmann <markus.dehmann@gmail.com> writes:

> Hi,
> 
> I have Leopard and I installed X11 from the Leopard installation DVD.
> 
> So, I can just type xterm in the terminal, and it will start X11 and
> xterm, right? But it doesn't work here. It's a fresh Leopard
> installation. When I type xterm nothing happens. When I look at top it
> shows that X11 and xterm are being executed, but no window shows up.
> 
> Am I missing something?

On my Leopard installation, if I type xterm at a terminal window,  I
get X11 starting up, and an xterm appearing.

Do you have the X11 icon showing up in your dock?  If so, click on
that, then select preferences, and make sure "Full Screen Mode" under
"Output" isn't selected.

If it _is_ selected, then X11 will be running, but putting its output
on some virtual window you aren't seeing.  (To see it, type
Command-Option-A.)

0
Reply ethelthelogremovethis2 (773) 2/26/2008 4:03:47 PM

On Feb 26, 11:03=A0am, Doug Anderson <ethelthelogremovet...@gmail.com>
wrote:
> Markus Dehmann <markus.dehm...@gmail.com> writes:
> > Hi,
>
> > I have Leopard and I installed X11 from the Leopard installation DVD.
>
> > So, I can just type xterm in the terminal, and it will start X11 and
> > xterm, right? But it doesn't work here. It's a fresh Leopard
> > installation. When I type xterm nothing happens. When I look at top it
> > shows that X11 and xterm are being executed, but no window shows up.
>
> > Am I missing something?
>
> On my Leopard installation, if I type xterm at a terminal window, =A0I
> get X11 starting up, and an xterm appearing.
>
> Do you have the X11 icon showing up in your dock? =A0If so, click on
> that, then select preferences, and make sure "Full Screen Mode" under
> "Output" isn't selected.
>
> If it _is_ selected, then X11 will be running, but putting its output
> on some virtual window you aren't seeing. =A0(To see it, type
> Command-Option-A.)

No, the X11 icon does not show up. But as I said, I can see it running
as reported by the top command. I think it's running in some wrong
display. I don't see it when I do Command-Option-A.

On this site: http://forums.macosxhints.com/showthread.php?t=3D80171
it says:

"In brief, don't run X11.app from the Dock. Or, at all, manually.
Ensure that you are not explicitly setting $DISPLAY in any
configuration files, verify that 'echo $DISPLAY' in Terminal.app
reports something that starts with '/tmp/launchd', and then just run
'xterm &' from Terminal. This will work with any X11 client
application that links with the standard libX11.dylib."

But my DISPLAY variable has the following content:
/tmp/launch-jBoCTO/:0
So, nothing with launchd (or is that supposed to be launch instead of
launchd?)

The only non-standard thing in my system is that I chose during
installation that terminal starts a bash rather than a shell.

Markus

0
Reply markus.dehmann (142) 2/26/2008 4:11:20 PM

Markus Dehmann <markus.dehmann@gmail.com> writes:

> On Feb 26, 11:03�am, Doug Anderson <ethelthelogremovet...@gmail.com>
> wrote:
> > Markus Dehmann <markus.dehm...@gmail.com> writes:
> > > Hi,
> >
> > > I have Leopard and I installed X11 from the Leopard installation DVD.
> >
> > > So, I can just type xterm in the terminal, and it will start X11 and
> > > xterm, right? But it doesn't work here. It's a fresh Leopard
> > > installation. When I type xterm nothing happens. When I look at top it
> > > shows that X11 and xterm are being executed, but no window shows up.
> >
> > > Am I missing something?
> >
> > On my Leopard installation, if I type xterm at a terminal window, �I
> > get X11 starting up, and an xterm appearing.
> >
> > Do you have the X11 icon showing up in your dock? �If so, click on
> > that, then select preferences, and make sure "Full Screen Mode" under
> > "Output" isn't selected.
> >
> > If it _is_ selected, then X11 will be running, but putting its output
> > on some virtual window you aren't seeing. �(To see it, type
> > Command-Option-A.)
> 
> No, the X11 icon does not show up. But as I said, I can see it running
> as reported by the top command. I think it's running in some wrong
> display. I don't see it when I do Command-Option-A.
> 
> On this site: http://forums.macosxhints.com/showthread.php?t=80171
> it says:
> 
> "In brief, don't run X11.app from the Dock. Or, at all, manually.

Right.  But the X11 will still show up in the Dock if you run X11 by
starting an X application (like xterm).

> Ensure that you are not explicitly setting $DISPLAY in any
> configuration files, verify that 'echo $DISPLAY' in Terminal.app
> reports something that starts with '/tmp/launchd', and then just run
> 'xterm &' from Terminal. This will work with any X11 client
> application that links with the standard libX11.dylib."
> 
> But my DISPLAY variable has the following content:
> /tmp/launch-jBoCTO/:0
> So, nothing with launchd (or is that supposed to be launch instead of
> launchd?)
> 
> The only non-standard thing in my system is that I chose during
> installation that terminal starts a bash rather than a shell.

Hmm.  It sounds to me like X11 is getting hung up someplace early in
startup.  The icon for X11 appears immediately in my dock when I start
an xterm from the terminal command line.

If I were you, I'd make a new user, and try to start X11 from there.

Then, if it works,  I would start investigating appropriate "." files.
0
Reply ethelthelogremovethis2 (773) 2/26/2008 5:10:10 PM

In article <26lk57prt9.fsf@ethel.the.log>,
 Doug Anderson <ethelthelogremovethis@gmail.com> wrote:

> Markus Dehmann <markus.dehmann@gmail.com> writes:
> > But my DISPLAY variable has the following content:
> > /tmp/launch-jBoCTO/:0
> > So, nothing with launchd (or is that supposed to be launch instead of
> > launchd?)
> > 
> > The only non-standard thing in my system is that I chose during
> > installation that terminal starts a bash rather than a shell.
> 
> Hmm.  It sounds to me like X11 is getting hung up someplace early in
> startup.  The icon for X11 appears immediately in my dock when I start
> an xterm from the terminal command line.
> 
> If I were you, I'd make a new user, and try to start X11 from there.
> 
> Then, if it works,  I would start investigating appropriate "." files.

Well, launching xterm works for me on a MacPro 10.5.2 that until today I 
don't think had ever launch X11.

$ /usr/X11/bin/xterm

And xterm starts up, X11 shows int eh dock, etc.  If I quit X11, then I 
get:

xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server 
"/tmp/launch-4f7oKM/:0"

which seems about right, since I basically killed the xterm process.

-- 
Bart: This is the worst day of my life.
Homer: This is the worst day of your life SO FAR.
0
Reply gkreme (545) 2/26/2008 6:03:29 PM

On 2008-02-26 07:05:06 -0800, Markus Dehmann <markus.dehmann@gmail.com> said:

> Hi,
> 
> I have Leopard and I installed X11 from the Leopard installation DVD.
> 
> So, I can just type xterm in the terminal, and it will start X11 and
> xterm, right? But it doesn't work here. It's a fresh Leopard
> installation. When I type xterm nothing happens. When I look at top it
> shows that X11 and xterm are being executed, but no window shows up.
> 
> Am I missing something?
> 
> Thanks!
> Markus

I had that problem with MATLab (which uses X11).  I just reinstalled 
X11 and MATLab and everything worked properly.  So ... I suggest 
reinstalling both.  There is a seperate X11 installer on the Leopard 
disk.

Laters...
-- 
Adobe - Preventing the case-sensitive revolution everyday

0
Reply nospam21 (11322) 2/26/2008 9:36:57 PM

In <mvzltnd7rw.fsf@ethel.the.log>, Doug Anderson wrote:

> On my Leopard installation, if I type xterm at a terminal window,  I
> get X11 starting up, and an xterm appearing.

Mine too.  I didn't know that.  Up until now, I've been launching X11 
before starting any X apps.  But I've just tested with a couple and 
noticed that starting them will start the X11 server if needed.

I don't know what to suggest to the original poster.

-j


-- 
Jeffrey Goldberg                     http://www.goldmark.org/jeff/
  I rarely read top-posted, over-quoting or HTML postings.
  http://improve-usenet.org/
0
Reply nobody30 (1816) 2/27/2008 12:59:18 AM

Jeffrey Goldberg wrote:

> Mine too.  I didn't know that.  Up until now, I've been launching X11 
> before starting any X apps.  But I've just tested with a couple and 
> noticed that starting them will start the X11 server if needed.

When I moved to OS-X, I read about this when trying to find
documentation about the X server on OS-X.

HOWEVER, if you have X applications on remote machines, they cannot
target their display to your OS-X machine until the OS-X has started its
X11 software

In particular, starting X11 causes it to read the  /private/etc/X0.hosts
file that contains the hosts authorized to target their X display onto
your machine.  I have not tested whether manually executing the XHOST
command without starting the X11 server would cause X11 to start
automatically upon reception of a call on port 6000 (the X window
protocol port).
0
Reply jfmezei.spamnot (8838) 2/27/2008 10:18:33 PM

8 Replies
55 Views

(page loaded in 0.125 seconds)

Similiar Articles:













7/2/2012 3:32:43 AM


Reply: