I have just upgraded all of my packages with Slackware Current. I do
this upgrade regularly, so this time my KDE has been upgraded from 3.2.1
to 3.2.2. When I start in runlevel 4 the system automatically starts op
KDM, but I cannot get KDM to work (in the new version). I enter my
username and password, but no desktops start. - KDM just starts op again
without any error-messages. It does not matter which desktop or username
I choose.

When I instead start up in runlevel 3, my new KDE (3.2.2) works
perfectly (started with the standard startx-command), so I imagine the
problem lies in KDM.

Any help will be appreciated...

On 2004-04-23, Jacob Tranholm <jacob_tranholm@hotmail.com> wrote:
> I have just upgraded all of my packages with Slackware Current. I do
> this upgrade regularly, so this time my KDE has been upgraded from 3.2.1
> to 3.2.2. When I start in runlevel 4 the system automatically starts op
> KDM, but I cannot get KDM to work (in the new version). I enter my
> username and password, but no desktops start. - KDM just starts op again
> without any error-messages. It does not matter which desktop or username
> I choose.
>
> When I instead start up in runlevel 3, my new KDE (3.2.2) works
> perfectly (started with the standard startx-command), so I imagine the
> problem lies in KDM.
>
> Any help will be appreciated...

check you logs in /var/logs/XFree-xx.xxxx


ken

Kenneth skrev:
> On 2004-04-23, Jacob Tranholm <jacob_tranholm@hotmail.com> wrote:
>
>>I have just upgraded all of my packages with Slackware Current. I do
>>this upgrade regularly, so this time my KDE has been upgraded from 3.2.1
>>to 3.2.2. When I start in runlevel 4 the system automatically starts op
>>KDM, but I cannot get KDM to work (in the new version). I enter my
>>username and password, but no desktops start. - KDM just starts op again
>>without any error-messages. It does not matter which desktop or username
>>I choose.
>>
>>When I instead start up in runlevel 3, my new KDE (3.2.2) works
>>perfectly (started with the standard startx-command), so I imagine the
>>problem lies in KDM.
>>
>>Any help will be appreciated...
>
>
> check you logs in /var/logs/XFree-xx.xxxx
>
>
> ken

As far as I can see, it is not an xfree86-problem. There are no
(important) error-messages in XFree86.0.log. There is however
error-messages in syslog:

Can't execute "/opt/kde/share/config/kdm/Xstartup": No such file or
directory
Cannot execute startup script "/opt/kde/share/config/kdm/Xstartup"
Can't execute "/opt/kde/share/config/kdm/Xreset": No such file or directory

These files are all mentioned in my /opt/kde/share/config/kdm/kdmrc file
and they have not been created during the installation of the kdebase
package. I probably have to create these files, but I don't know what to
write in them.

On 2004-04-23, Jacob Tranholm <jacob_tranholm@hotmail.com> wrote:
> Kenneth skrev:
>> On 2004-04-23, Jacob Tranholm <jacob_tranholm@hotmail.com> wrote:
>>
>>>I have just upgraded all of my packages with Slackware Current. I do
>>>this upgrade regularly, so this time my KDE has been upgraded from 3.2.1
>>>to 3.2.2. When I start in runlevel 4 the system automatically starts op
>>>KDM, but I cannot get KDM to work (in the new version). I enter my
>>>username and password, but no desktops start. - KDM just starts op again
>>>without any error-messages. It does not matter which desktop or username
>>>I choose.
>>>
>>>When I instead start up in runlevel 3, my new KDE (3.2.2) works
>>>perfectly (started with the standard startx-command), so I imagine the
>>>problem lies in KDM.
>>>
>>>Any help will be appreciated...
>>
>>
>> check you logs in /var/logs/XFree-xx.xxxx
>>
>>
>> ken
>
> As far as I can see, it is not an xfree86-problem. There are no
> (important) error-messages in XFree86.0.log. There is however
> error-messages in syslog:
>
> Can't execute "/opt/kde/share/config/kdm/Xstartup": No such file or
> directory
> Cannot execute startup script "/opt/kde/share/config/kdm/Xstartup"
> Can't execute "/opt/kde/share/config/kdm/Xreset": No such file or directory
>
> These files are all mentioned in my /opt/kde/share/config/kdm/kdmrc file
> and they have not been created during the installation of the kdebase
> package. I probably have to create these files, but I don't know what to
> write in them.

Some of these items are scripts some are not....they all there in the
orginal kdebase on the slackware cd... I suppose it's possible that the
files were deleted during the update...not likely...however, if you can get
your hands on the orginal kdebase, the file are there in the correct
directory etc, just copy and move them over to your new update and work from
there as a starting point.

However, you might want to run locate for the missing files, not the
pathname and filenames, just the filenames, there may be copies somewhere on
your hd you don't know about.

below are the files I pulled from the cd...don't forget to chmod 755 the files

Sorry I should have kept my mouth shut...I don't use kde, haven't for
sometime, therefore, my experience is at best, outdated.

ken

#Xstartup
#! /bin/sh
# Xstartup - run as root before session starts

# By convention, both xconsole and xterm -C check that the
# console is owned by the invoking user and is readable before attaching
# the console output. This way a random user can invoke xterm -C without
# causing serious grief; still, it can cause havoc, so xconsole is started
# by Xsetup usually.
# This is not required if you use PAM with the pam_console module.
#
#chown $USER /dev/console

exec sessreg -a -l $DISPLAY $USER

#Xsetup
#! /bin/sh
# Xsetup - run as root before the login dialog appears

#xconsole -geometry 480x130-0-0 -notify -verbose -fn fixed -exitOnFail -file /dev/xconsole &

#Xreset
#! /bin/sh
# Xreset - run as root after session exits

# Reassign ownership of the console to root, this should disallow
# assignment of console output to any random users's xterm. See Xstartup.
#
#chown root /dev/console
#chmod 622 /dev/console

exec sessreg -d -l $DISPLAY $USER

I had exactly the same problem. Copying the files Xstartup and Xreset
from the old kdebase-3.2.1-i486-1.tgz to /opt/kde/share/config/kdm
solved the problem.

Message posted via:
=====================
www.linuxpackages.net/forum
www.linuxpackages.net
Expanding the world of Slackware
=====================

bsc skrev:
> I had exactly the same problem. Copying the files Xstartup and Xreset
> from the old kdebase-3.2.1-i486-1.tgz to /opt/kde/share/config/kdm
> solved the problem.
>
> Message posted via:
> =====================
> www.linuxpackages.net/forum
> www.linuxpackages.net
> Expanding the world of Slackware
> =====================

Thanks... That did the trick. My KDM is now working again.

Kenneth skrev:
>
> Some of these items are scripts some are not....they all there in the
> orginal kdebase on the slackware cd... I suppose it's possible that the
> files were deleted during the update...not likely...however, if you can get
> your hands on the orginal kdebase, the file are there in the correct
> directory etc, just copy and move them over to your new update and work from
> there as a starting point.

The files do not exist in the 3.2.2 version of kdebase. - It must be an
error in the compilations. I have copied them from the 3.2.1 version of
kdebase and now my KDM works once again.

>
> However, you might want to run locate for the missing files, not the
> pathname and filenames, just the filenames, there may be copies somewhere on
> your hd you don't know about.
>

The files were deleted from my harddisk during the update and they were
not located somewhere else.

Jacob Tranholm a écrit :
> bsc skrev:
>
>> I had exactly the same problem. Copying the files Xstartup and Xreset
>> from the old kdebase-3.2.1-i486-1.tgz to /opt/kde/share/config/kdm
>> solved the problem.
>>
>> Message posted via:
>> =====================
>> www.linuxpackages.net/forum
>> www.linuxpackages.net
>> Expanding the world of Slackware
>> =====================
>
>
> Thanks... That did the trick. My KDM is now working again.

same problem here... and same solution thx for all

On Fri, 23 Apr 2004 22:36:55 +0200, _Hitek_ wrote:

> Jacob Tranholm a écrit :
>> bsc skrev:
>>
>>> I had exactly the same problem. Copying the files Xstartup and Xreset
>>> from the old kdebase-3.2.1-i486-1.tgz to /opt/kde/share/config/kdm
>>> solved the problem.
>>>
>>> Message posted via:
>>> =====================
>>> www.linuxpackages.net/forum
>>> www.linuxpackages.net
>>> Expanding the world of Slackware
>>> =====================
>>
>>
>> Thanks... That did the trick. My KDM is now working again.
>
> same problem here... and same solution thx for all

For people who don't have the kdebase-3.2.1 anymore for some reason (like
me): The files *are* in the kdebase-3.2.2-package, but are not getting
copied while installing, so you can copy them from there.

Kaj

On Fri, 23 Apr 2004 22:36:55 +0200, _Hitek_ wrote:

> Jacob Tranholm a écrit :
>> bsc skrev:
>>
>>> I had exactly the same problem. Copying the files Xstartup and Xreset
>>> from the old kdebase-3.2.1-i486-1.tgz to /opt/kde/share/config/kdm
>>> solved the problem.
>>>
>>> Message posted via:
>>> =====================
>>> www.linuxpackages.net/forum
>>> www.linuxpackages.net
>>> Expanding the world of Slackware
>>> =====================
>>
>>
>> Thanks... That did the trick. My KDM is now working again.
>
> same problem here... and same solution thx for all

Shouldn't this be reported to Patrick?