Afternoon all,

I'm hoping someone can point me in the right direction:

I turned on my main box (slack 9.1, with the supplied kernel, KDE version,
etc) as usual, logged in and tried to lauch kde in the usual way with the
startx command. It started off as normal, but then, after the Nvidia
splash screen, instead of showing the loading components screen, exited
out, without returning any errors. I really don't know where to start with
trying to fix this, but here's what I know:

All I did the last time the box was running (last night) was all I usually
do - I wasn't tinkering with any settings of anything, apart from
downloading yahoo messenger, doing an 'rpm2tgz' and installing and
configuring it. No errors were reported, but I've since removed it anyway.
Also, using the startxfce4 command, I was able to lauch the fce4 wm as the
same user. I could also start KDE when logged in as a different user (one
i just created). This leads me to suspect it's a config issue somewhere in
my home directory config files - somewhere in ~/.kde/ I suspect, but
looking around, I can't find anything of note or obvious.

Comparing the log files (/var/log/Zfree86.0.log) generated by the
successful startx as a new user, and the failed one, I can see no
differences or errors generated. It's almost as if somewhere there's an
instruction to simply quit kde as soon as it's started!

Here's what comes up, after it's failed to start:

XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.22 i686 [ELF]
Build Date: 16 September 2003
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Sat Jan 15 16:40:41 2005
(==) Using config file: "/etc/X11/XF86Config"
(II) Initializing extension GLX

waiting for X server to shut down
$


I'm completely miffed - can anyone suggest where I should start looking,
and what I should be looking for to sort this out?

As ever, apologies if I'm being really stupid.

Cheers,

sb

On Sat, 15 Jan 2005 16:46:13 +0000, standardblue wrote:

> Afternoon all,
>
> I'm hoping someone can point me in the right direction:
>
snip.
>
> As ever, apologies if I'm being really stupid.
>
> Cheers,
>
> sb

Try three things:

1) check that /etc/X11/xinit/xinitrc.kde exists
2) if so, ln -fs /etc/X11/xinitrc.kde ~/.xinitrc
3) try startx again.

If xinitrc.kde does NOT exist, then try
startx kde (since this will pull in xdm)

In article <pan.2005.01.15.17.24.33.320829>, Peter
<peter> wrote:
> Try three things:
>
> 1) check that /etc/X11/xinit/xinitrc.kde exists
> 2) if so, ln -fs /etc/X11/xinitrc.kde ~/.xinitrc
> 3) try startx again.
>
> If xinitrc.kde does NOT exist, then try
> startx kde (since this will pull in xdm)

That worked Peter, thanks. I had looked at ~/.xinitrc before, and it had
appeared as an empty (text) file, so I'd assumed it was just a container
for x variables that I was just using defaults on, or something.

I assume, therefore, it must have got de-linked. I don't know how - I
centainly didn't do it knowingly!

Anyway, thanks very much! :-)


sb

On Sat, 15 Jan 2005 17:35:43 +0000, standardblue wrote:

> In article <pan.2005.01.15.17.24.33.320829>, Peter
> <peter> wrote:
>> Try three things:
>>
snip
> That worked Peter, thanks. I had looked at ~/.xinitrc before, and it had
> appeared as an empty (text) file, so I'd assumed it was just a container
> for x variables that I was just using defaults on, or something.
>
> I assume, therefore, it must have got de-linked. I don't know how - I
> centainly didn't do it knowingly!
>
> Anyway, thanks very much! :-)
>> sb

Great. Glad it worked!

I don't know about Slackware 9.1, but in 10 USUALLY the default WM is
linked from within /etc. If you use pkgtools and select KDE (for example)
as your default WM, then in /etc, xinitrc ---> xinitrc.kde. Doing it from
~ allows you not to have to sudo each time you want to relink. If you use
a KDM/GDM type login manager, you may not have had this problem.

Here's another workaround if you don't want to link your ~/.xinitrc. You
can execute startx /etc/X11/xinitrc.kde directly (or any other rc file).

Lots of ways to skin this cat, but having an invalid .xinitrc will kill
launching any WM!

Peter wrote:
[..]
> as your default WM, then in /etc, xinitrc ---> xinitrc.kde. Doing it from
> ~ allows you not to have to sudo each time you want to relink. If you use
> a KDM/GDM type login manager, you may not have had this problem.
>
> Here's another workaround if you don't want to link your ~/.xinitrc. You
> can execute startx /etc/X11/xinitrc.kde directly (or any other rc file).
>
> Lots of ways to skin this cat, but having an invalid .xinitrc will kill
> launching any WM!
>

plz. don't skin cats ! :)

cashmir