I'm running Slack 9.1. Since I recently upgraded from slack 9.0 to my
current version, I have no longer been able to get from kdm into any
window managers (kde, twm etc). I can however get into my WM using
"startx" and I can also get into kdm with no problems (I am using
konqueror to do this).

I might add that my server machine, which I also upgraded from slack
9.0 to 9.1, does not have this problem.

my /root/.xsession_errors and /home/me/.xsession_errors do not display
anything - ie presumably no errors.

My /var/log/XFree86.0.log does not show any errors (ie no (EE)) but
there are a few warnings.

/var/log/kdm.log also does not show any errors.

I can send a copy of these logs if needed (but I got reprimanded for
doing this on another newsgroup).

I've been having trouble with this for weeks and am getting
desperate!!

Robert S

On Wed, 05 Nov 2003 01:00:01 -0800, Robert wrote:

> I'm running Slack 9.1. Since I recently upgraded from slack 9.0 to my
> current version, I have no longer been able to get from kdm into any
> window managers (kde, twm etc). I can however get into my WM using
> "startx" and I can also get into kdm with no problems (I am using
> konqueror to do this).

And what happens? Are you thrown back out in console? Does it say "Go mess
yourself"? What is the window manager? _What_?

> I've been having trouble with this for weeks and am getting desperate!!

You must live an emtpy and sad life, if trivial things, such as kdm can
get you into a state of desperation.

--
Erik L
erik@metalab.unc.edu
Sweden

> > I'm running Slack 9.1. Since I recently upgraded from slack 9.0 to my
> > current version, I have no longer been able to get from kdm into any
> > window managers (kde, twm etc). I can however get into my WM using
> > "startx" and I can also get into kdm with no problems (I am using
> > konqueror to do this).
>
> And what happens? Are you thrown back out in console? Does it say "Go mess
> yourself"? What is the window manager? _What_?
>

When I log into any window manager (KDE, TWM etc), the screen goes
momentarily black then I am returned to the KDM/XDM login screen. It
does not seem to be specific to the window manager and it happens with
KDM and XDM.

Do all of these programs use the same /etc/X11/XF86Config file?

> > I've been having trouble with this for weeks and am getting desperate!!
>
> You must live an emtpy and sad life, if trivial things, such as kdm can
> get you into a state of desperation.

I have booked myself into a local clinic to discuss these issues with
my psychiatrist.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert wrote:

> When I log into any window manager (KDE, TWM etc), the screen goes
> momentarily black then I am returned to the KDM/XDM login screen. It
> does not seem to be specific to the window manager and it happens with
> KDM and XDM.

Looks like you've got an iffy config file somewhere, check
/etc/X11/xdm/Xsession for starters (assuming you're using KDM/XDM).

Try running startkde instead of startx, does that work?

> Do all of these programs use the same /etc/X11/XF86Config file?

If you're getting to a KDM/XDM/GDM login screen and startx works then it's
pretty safe to say that the XF86Config file is okay. Your problem seems to
be that whatever window manager you're trying to use is failing to start.
Check the window managers log file(s) if you can, that might give you a
clue.

Blumf

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/qV1AMid3IcxolsoRAjUHAKCOsyv9+Kciluq07JGSb8eHATndWg CfR/ox
p/GSvLMjgUlVci4emh2+KTM=
=3ys4
-----END PGP SIGNATURE-----

> Robert wrote:
>
> > When I log into any window manager (KDE, TWM etc), the screen goes
> > momentarily black then I am returned to the KDM/XDM login screen. It
> > does not seem to be specific to the window manager and it happens with
> > KDM and XDM.
>
> Looks like you've got an iffy config file somewhere, check
> /etc/X11/xdm/Xsession for starters (assuming you're using KDM/XDM).
>
> Try running startkde instead of startx, does that work?
-------------------------------8><--------------------------------
Now we're getting somewhere. Here is what I get when I run startkde:

xset: unable to open display ""
xset: unable to open display ""
xset: unable to open display ""
xsetroot: unable to open display ''
startkde: Starting up...
ksplash: cannot connect to X server
kdeinit: Aborting. $DISPLAY is not set.
Warning: connect() failed: : No such file or directory
ksmserver: cannot connect to X server
startkde: Shutting down...
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!
X11GlobalComm: Can't connect to the XServer - Initial references won't
work.
bad md5 secret-cookie obtained from Arts::X11GlobalComm - replacing it
startkde: Running shutdown scripts...
startkde: Done.

I'm afraid that my understanding of the complexities of XFree86 are
rather rudimentary. This certainly don't look right to me. I've
managed to start KDE using startkde in the past.

Can somebody unravel this problem?

Robert <send_to_me@areujoking.com> wrote:
> Do all of these programs use the same /etc/X11/XF86Config file?

Of course!
They're all "X windows client programs", which means they're using X11
and for Linux X11 is the XFree86 package, which is configured by XF86Config.

Kde, Gnome, Xfce, etc, are just windows MANAGERS (cq environments),
which control the layout and look OF the windows, not the X server
itself (the program X:
root 24227 24225 0 Nov04 ? 01:57:55 /usr/X11R6/bin/X vt5 -auth /var/run/xauth/
from my "ps -ef" list).
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TWA **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************