on Fri, Dec 15, 2000 at 09:38:05AM -0800, Erik Steffl ([EMAIL PROTECTED]) wrote:
> Joey Hess wrote:
> >
> > Shao Zhang wrote:
> > > xdm on my machine(laptop) takes about 50 seconds to start.
> >
> > > If no one knows why, then I am going to fire up a bug report against it.
> >
> > I've already t
Am Freitag, 15. Dezember 2000 18:38 schrieb Erik Steffl:
> Joey Hess wrote:
> > Shao Zhang wrote:
> > > xdm on my machine(laptop) takes about 50 seconds to start.
> > >
> > > If no one knows why, then I am going to fire up a bug report against
> > > it.
> >
> > I've already tracked down this bug an
Jaye Inabnit ke6sls wrote:
>
> Erik,
>
> Not sure if this will help at all, but if you are running kde, there may
> be a problem with xdm as window manager - I didn't read long on it, but
> kde is a "session-manager" and therefore requires I guess kdm to run.
>
> So, if you are running kde,
Joey Hess wrote:
>
> Shao Zhang wrote:
> > xdm on my machine(laptop) takes about 50 seconds to start.
>
> > If no one knows why, then I am going to fire up a bug report against it.
>
> I've already tracked down this bug and filed a report, so please don't
> bother.
any news on this? xdm still
Most commonly, DNS lookup or reverse lookup. This was a frequently
iterated bug in early RedHat releases, particularly sendmail timeouts on
startup.
A cow-orker reported inability to start X on a laptop due to a missing
localhost or hostname entry in his /etc/hosts file, or similar. The
machine
Shao Zhang wrote:
> xdm on my machine(laptop) takes about 50 seconds to start.
> If no one knows why, then I am going to fire up a bug report against it.
I've already tracked down this bug and filed a report, so please don't
bother.
--
see shy jo
"Andre" == Andre Berger <[EMAIL PROTECTED]> writes:
Andre> I'm not sure if it will help you, but check your
Andre> /etc/X11/Xresources/* files, and your ~/.Xresources. If you
Andre> have something very long like a complete netscape language
Andre> localization in it, xrdb -merge can take a very lo
Shao Zhang <[EMAIL PROTECTED]> writes:
I'm not sure if it will help you, but check your /etc/X11/Xresources/*
files, and your ~/.Xresources. If you have something very long like a
complete netscape language localization in it, xrdb -merge can take a
very long time, esp. on slow machines.
-- Andr
Me too!
xdm on my machine(laptop) takes about 50 seconds to start.
These are the last few lines in my xdm.log:
(==) ATI(0): Backing store disabled
(**) Mouse0: Protocol: "PS/2"
(**) Mouse0: Core Pointer
(==) Mouse0: Buttons: 3
(II) Keyboard "Keyboard0" handled by legacy driver
(II) XINPUT: Adding
I have the same problem. what kind of DNS issues? I can ping
localhost, jojda (which is my hostanme), 127.0.0.1 just fine...
also, sometime when I restarted X (the old 3.x) when using xdm, it
would take a long time (minutes!) to restart. but never when it was
started for the first time...
a
"Andy" == Andy Bastien <[EMAIL PROTECTED]> writes:
MAS> 1. xdm now takes over a minute from when the daemon is started, either
MAS> by init or manually, to when the login widget appears. Is this
MAS> normal now, or is there anything I can do to speed it up?
Andy> I don't know. Maybe it's trying
on Sun, Nov 05, 2000 at 04:02:18AM -0800, Michael Abraham Shulman ([EMAIL
PROTECTED]) wrote:
> I wrote:
>
> MAS> Okay, it appears to be working now.
>
> Well, more or less. Everything runs fine with `startx', but I'm
> having some peculiar difficulties with xdm. Specifically,
>
> 1. xdm now t
There are those who would have you believe that Michael Abraham Shulman wrote:
> I wrote:
>
> MAS> Okay, it appears to be working now.
>
> Well, more or less. Everything runs fine with `startx', but I'm
> having some peculiar difficulties with xdm. Specifically,
>
> 1. xdm now takes over a min
I wrote:
MAS> Okay, it appears to be working now.
Well, more or less. Everything runs fine with `startx', but I'm
having some peculiar difficulties with xdm. Specifically,
1. xdm now takes over a minute from when the daemon is started, either
by init or manually, to when the login widget ap
"Phillip" == Phillip Deackes <[EMAIL PROTECTED]> writes:
MAS> I just upgraded all the X packages to 4+ versions in unstable, and now
MAS> my X server won't run.
Phillip> When I did 'apt-get -u dist-upgrade' I noticed that
Phillip> task-x-window-system-core was maked as held back. After the
Philli
Michael Abraham Shulman <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I just upgraded all the X packages to 4+ versions in unstable, and now
> my X server won't run. It dies with the error message
>
> *** None of the configured devices were detected.***
>
> Fatal server error:
> no screens found
>
> I
Hi,
I just upgraded all the X packages to 4+ versions in unstable, and now
my X server won't run. It dies with the error message
*** None of the configured devices were detected.***
Fatal server error:
no screens found
It was working yesterday and the only thing I changed was installing
the n
17 matches
Mail list logo
