From: Keith Seitz <keiths@redhat.com>
To: "Bhagat, Vivek" <vivek.bhagat@scr.siemens.com>
Cc: "'insight@sources.redhat.com'" <insight@sources.redhat.com>
Subject: RE: insight GUI not working!
Date: Fri, 16 Jul 2004 13:43:00 -0000 [thread overview]
Message-ID: <1089985581.2768.15.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <20B20848358CDA44AB6A2E277D2E1C5E05697245@postoffice.scr.siemens.com>
On Fri, 2004-07-16 at 06:31, Bhagat, Vivek wrote:
> Yes, what I meant about "gdb console window" was command line gdb. No
> there are no errors or anything. I checked all my permissions under
> /opt/insight directory and they are all fine.
Ok, that's a good start.
> But when you say "Is DISPLAY set?" what does that mean? Can you
> explain or point me to the documentation where I could get direction
> on actually going and setting my DISPLAY. I think may be it's this
> display thing that is not configured properly.
DISPLAY is an environment variable used by X Windows to determine what
physical (or virtual) display to use. This is how you can run any X
application (like insight, xterm, xmtr, etc) on one machine and have it
display on a monitor attached to a different workstation.
From your shell, type "echo $DISPLAY". You should see something like
"localhost:0" or something. If not, set DISPLAY according to the
instructions on the X man page ("man X"; look for section "DISPLAY
NAMES").
Of course, the other simple test of whether or not DISPLAY is set is to
run some other X application. Do other X applications work?
Keith
next prev parent reply other threads:[~2004-07-16 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 13:31 Bhagat, Vivek
2004-07-16 13:43 ` Keith Seitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-16 14:07 Bhagat, Vivek
2004-07-16 14:39 ` Keith Seitz
2004-07-16 13:03 Bhagat, Vivek
2004-07-16 13:17 ` Keith Seitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1089985581.2768.15.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=vivek.bhagat@scr.siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).