Kleinere Probleme seit KDE3 Installation

[inka]

Vor kurzem habe ich KDE3 installiert und KDE2.2 deinstalliert. Dummerweise startete dann KDM nicht mehr, den ich eigentlich als Loginmanager verwenden wollte. In der Konsole schien folgende Meldung auf: ID "x" respawning too fast.... . Das habe ich gelöst indem ich ind der /etc/inittab folgendes geändert habe:
#x:5:respawn:/etc/X11/prefdm -nodaemon --auskommentiert
x:5:respawn:/opt/kde3/bin/kdm --hinzugefügt
Kdm startet jetzt zwar und KDE3 auch, nur dummerweise wird in der Konsole immer noch die gleiche Meldung ausgegeben. Dürfte eigentlich nicht mehr passieren, oder ?
Hier meine gesamte /etc/inittab:
#
# inittab This file describes how the INIT process should set up
# the system in a certain run-level.
#
# Author: Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
# Modified for RHS Linux by Marc Ewing and Donnie Barnes
#

# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
#
id:5:initdefault:

# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit

l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6

# Things to run in every runlevel.
ud::once:/sbin/update

# Trap CTRL-ALT-DELETE
ca::ctrlaltdel:/sbin/shutdown -t3 -r now

# When our UPS tells us power has failed, assume we have a few minutes
# of power left. Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"

# If power was restored before the shutdown kicked in, cancel it.
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"


# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6

# Run xdm in runlevel 5
# xdm is now a separate service
#x:5:respawn:/etc/X11/prefdm -nodaemon
x:5:respawn:/opt/kde3/bin/kdm


Ein weiteres kleines Problem habe ich im Kpanel. Wenn ich die Slick Symbole auswähle werden sie auch angezeigt( sind sehr schön! ). Nur sind nach einem Logout die alten KDE2 Symbole wieder da. Wenn ich aber mit der Maus auf ein SYmbol ziehe sehe ich wieder die neuen Symbole! Seltsam.
Weiß jemand vielleicht eine Lösung? Benutze Mandrake 8.2..

mfg
inka

[ml]

Hallo!

Hab das gleiche Problem unter LM8.2 aber noch keine Lösung gefunden ;-(

[schnebeck]

Ich zitiere das KDM-README:
HTH

Bye

Thorsten

--

$Id: README,v 2.13 2001/12/03 12:01:54 ossi Exp $

This is the KDE Display Manager (kdm) v0.93 for KDE 3.0,
the KDE replacement for the X Display Manager (xdm).


How to setup kdm
----------------

KDM's config files are all located in ${kde_confdir}/kdm.
"make install" will install an example configuration if the directory
does not exist yet.

You can change the configuration from the KDE Control Center.
You will find the Login Manager module in "System" -> "Login Manager".

Have a look at README.pam in the kdebase top level directory if your
system uses PAM.


Running KDM from init
---------------------

NOTE, that this description applies to RedHat and must be adapted for
other distributions/systems.

Edit (as root) /etc/inittab.

Look for the line:

x:5:respawn:/usr/X11/bin/xdm -nodaemon

Replace it with:

x:5:respawn:/opt/kde/bin/kdm -nodaemon

This tells init(8) to respawn KDM, the KDE display manager, when
the system is in run level 5.

To start KDM, either run (as root) /sbin/telinit 5 (to switch to
run level 5), or (this is risky! don't do it until you _know_ you
want the system to boot into this every time!) edit /etc/inittab
and change the line:

id:3:initdefault:

to

id:5:initdefault:

If you do the latter step, then every time your system boots
successfully it will go into run level 5 and run KDM,
presenting you the exceedingly cute KDE login screen.


The command FiFos
-----------------

This is a feature you can use to remote-control KDM. It's mostly intended
for use by ksmserver and kdesktop from a running session, but other
applications are possible as well.
There are two types of FiFos: the global one (xdmctl) and the per-display
ones (xdmctl-<display>).
The global one is owned by root, the per-display ones are owned by the user
currently owning the session (root or the logged in user). Group ownership
of the FiFos can be set via FifoGroup=, otherwise it's root. The file
permissions of the FiFos are rw--w---- (0620). The FiFos are created in the
directory specified by FifoDir=.
The fields of a command are separated by tabs (\t), the fields of a list
are separated by spaces. The command is terminated by a newline (\n).

Global FiFo commands:

"shutdown" ("reboot"|"halt") ("forcenow"|"trynow"|"schedule")
- same functionality as the shutdown dialog

"login" display ("now"|"schedule") user password session_arguments
- login user at specified display. if "now" is specified, a possibly
running session is killed, otherwise the login is done after the session
exits.

Per-display Fifo commands:

"shutdown" ("reboot"|"halt") ["forcenow"|"trynow"|"schedule"]
- Same functionality as the shutdown dialog. It takes effect when the
session at this display exits.

"lock"
- The display is marked as locked. If the x-server crashes in this state,
no auto-relogin will be performed even if the option is on. If all local
displays are locked and reserve displays are specified in Xservers, a
new login screen is started.

"unlock"
- Reverse the effects of "lock". Re-enable auto-relogin and remove the
reserve login screen, if it's not used.

"reserve"
- Start a reserve login screen. If nobody logs in within one minute, the
display is removed again. When the session on the display exits and there
are other non-locked local displays, the display is removed.

"suicide"
- The currently running session is forcibly terminated. No auto-relogin is
attempted, but a scheduled "login" command will be executed.


Random rambings and license information
---------------------------------------

Version 0.1 of kdm is copyright
Matthias Ettrich <ettrich@trolltech.com>
All later versions copyright:
(C) 1997-2000 Steffen Hansen <hansen@kde.org>
Since version 0.90 (KDE 2.1) copyright:
(C) 2000-2001 Oswald Buddenhagen <ossi@kde.org>

The files in the backend directory are licensed under the X licence
(see www.xfree86.org for more info).
The files in the chooser and kfrontend directories are licensed under
the GNU GPL.

Thanks to (in no particular order):
Michael Bach Jensen and Torsten Rahn for drawing icons.
Duncan Haldane for investigation of PAM issues.
Stephan Kulow for helping me with the autoconf stuff.
Martin Baehr for intensive testing and writing the sample Xsession scripts.
Harald Hoyer <Harald.Hoyer@redhat.de> for the chooser
... and _many_ others ...


"It doesn't work!!"
-------------------

More input! ;-)

KDM accepts two command line options related to logging. These options
_must_ come first on the command line, if they are used:

-debug <n>
<n> is a decimal or hexadecimal (prefix 0x) number.
The number is a bitfield, i.e., it is formed by summing up the
required values from this table:
1 (0x1) - core debugging. probably the most useful one.
2 (0x2) - config reader debugging.
4 (0x4) - greeter debugging.
8 (0x8) - ipc debugging. this logs _all_ communication between the
core, the config reader and the greeter - including the
passwords you type - so edit the log before showing it to
somebody.
16 (0x10) - wait after forking session sub-daemon.
32 (0x20) - wait after starting config reader.
64 (0x40) - wait after starting greeter.
the wait options are only useful, if you need to attach a debugger
to a process but it crashes before you are able to do so without
the delay.
256 (0x100) - core Xauth debugging.
512 (0x200) - don't fork session sub-daemon, but manage one session
in the master daemon. not for real-world use.

-logfile <file>
<file> is the file to log various messages to.
For internal reasons there is no option in kdmrc to permanently specify
another log file location. If you redirect KDM's standard error output
to a file, KDM will log there.
If KDM is configured to use syslog, all internally generated messages
are logged to the "daemon" facility. The log usually can be found in
/var/log/debug.log and /var/log/daemon.log; make sure, that daemon.*
is logged (look at /etc/syslog.conf).

Send me the logs together with a detailed description what you did and
what happened. If your problem is related to a specific configuration,
you should also attach a tar.gz archive of your kdm config directory.


--
Have fun with it (and feel free to comment),

Oswald Buddenhagen <ossi@kde.org>