>
> > > My question iswhen X Windows starts doing this, how the hell do we
> > > debug it?
> >
> > look at the :0.log file in /var/gdm
>
> THANK YOU! It was complaining about not being able to connect to some
> socket. I found the socket in /tmp; it looked like an old copy. I
> removed a
On Tue, Jun 20, 2000 at 10:33:05AM -0700, Steven Boswell wrote:
> But I can't get X Windows to work reliably in 6.2! (I don't remember
> having ANYWHERE this much trouble with X Windows in previous Red Hat
> releases.) When I start it, it looks like it's trying to start X
> Windows, fails, and t
Steven Boswell wrote:
> THANK YOU! It was complaining about not being able to connect to some
> socket. I found the socket in /tmp; it looked like an old copy. I
> removed all the old X-related stuff from /tmp (e.g. .X11-Unix,
> .ICE-Unix, .font-unix, and a few others), and now X Windows will s
> > My question iswhen X Windows starts doing this, how the hell do we
> > debug it?
>
> look at the :0.log file in /var/gdm
THANK YOU! It was complaining about not being able to connect to some
socket. I found the socket in /tmp; it looked like an old copy. I
removed all the old X-relate
This can happen if you "su" to root using a user id that is separate
from root but uses the same home directory. For instance instead of
sharing root we give out individual root. For instance mine reads:
rootmf:x:0:0:Super Matt Fahrner:/home/matt:/bin/csh
If I "su" under certain circumstance
Bootup in runlevel 3.
eg:
LILO boot: linux 3
--- "Eric H. Majzoub" <[EMAIL PROTECTED]> wrote:
> On Tue, 20 Jun 2000, Steven Boswell wrote:
>
> > releases.) When I start it, it looks like it's
> trying to start X
> > Windows, fails, and then loops back and tries to
> do it again. So it
> > just
On Tue, 20 Jun 2000, Steven Boswell wrote:
> releases.) When I start it, it looks like it's trying to start X
> Windows, fails, and then loops back and tries to do it again. So it
> just gets itself into a loop where it constantly fails, and there's no
> way to stop it. Even worse, I can't swi
* Steven Boswell <[EMAIL PROTECTED]> [06/20/00 14:00]:
> My question iswhen X Windows starts doing this, how the hell do we
> debug it?
look at the :0.log file in /var/gdm
I've had this happen on 3 different boxes over the last 2-3 weeks.
they're development machines, so they get rebooted con
On Tue, 20 Jun 2000, Steven Boswell wrote:
> My question iswhen X Windows starts doing this, how the hell do we
> debug it?
Switch your run level to 3. This way X won't start automatically. Log
in on the console, and 'startx' to see why X isn't starting correctly.
The behavior you gave is
-Original Message-
From: Steven Boswell [mailto:[EMAIL PROTECTED]]
Sent: 20 June 2000 18:33
To: [EMAIL PROTECTED]
Subject: X Windows in 6.2 is VERY fragile!
I've been running RedHat 6.2 for a few months now (and I've been running
Red Hat Linux in general for several years now)
I've been running RedHat 6.2 for a few months now (and I've been running
Red Hat Linux in general for several years now). I've got it running on
three machines; two of them have X Windows installed.
But I can't get X Windows to work reliably in 6.2! (I don't remember
having ANYWHERE this much t
11 matches
Mail list logo
