Date: Fri, 07 Dec 2001 14:12:40 +0100 From: Raf Schietekat <sky92136@skynet.be> To: doc@FreeBSD.org Subject: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11-wm.html Message-ID: <3C10C048.4080608@skynet.be>
next in thread | raw e-mail | index | archive | help
If doc@FreeBSD.org is inappropriate for this kind of comment, please
excuse (and educate) me.
I tried to install kdm by running kcontrol in an su root session in a
Konsole in a KDE session started by xdm started from /etc/ttys in
4.4-RELEASE, but it failed (see output from kcontrol at end of message).
Is there something general about X that should be known at this point to
avoid that? Is this going to cause other problems? If so, it would be
nice to have an explanation right here in the handbook. (When I started
an X server as root anyway (through xdm), kcontrol worked fine.)
"Note: In KDE 2.2 this has changed: kdm now uses its own configuration
files. Please see the KDE 2.2 documentation for details."
Apparently, the main text was written before KDE 2.2, then this note was
quickly added. How about a cleaner restructuring, so the (new) reader
doesn't encounter some stuff that turns out not to apply to his
situation. In particular, in BSD 4.4-RELEASE, there's a Modify button
where you can give kcontrol root privileges while already running it, so
the whole thing about running kcontrol as root is a moot issue.
If running the X Window System as root is considered unsafe, how about
documenting whether it's possible to sidestep it while, say, xdm is
waiting for a user to log in, or any time while a user is currently
logged in (i.e., suspend X). It would probably also be useful to add the
adminishment to the explanation about xdm. Will kdm allow the user to
choose a plain shell instead of X?
In 4.4-RELEASE, kdmdesktop apparently resides at
/usr/local/bin/kdmdesktop, not /usr/X11R6/bin/kdmdesktop (multiple
occurrences, possibly elsewhere as well).
If I change /usr/X11R6/bin/xdm to /usr/local/bin/kdmdesktop, I get an
ordinary shell with messages like (date omitted):
"desktop init: getty repeating too quickly on port /dev/ttyv8, sleeping
30 secs"
What do I have to do to get kdm running? I don't find anything in the
provided KDE documentation.
Raf Schietekat <Raf_Schietekat@ieee.org>
>>>>> output of kcontrol >& errors.txt
kdeinit: Launched DCOPServer, pid = 3154 result = 0
_KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
DCOP: register 'anonymous-3154' -> number of clients is now 1
DCOPServer up and running.
DCOP: unregister 'anonymous-3154'
kdeinit: Launched KLauncher, pid = 3159 result = 0
DCOP: register 'klauncher' -> number of clients is now 1
DCOP: unregister 'klauncher'
DCOP: register 'klauncher' -> number of clients is now 1
DCOP: register 'anonymous-3159' -> number of clients is now 2
DCOP: new daemon klauncher
DCOP: unregister 'anonymous-3159'
kdeinit: Launched KDED, pid = 3161 result = 0
DCOP: register 'kded' -> number of clients is now 1
DCOP: unregister 'kded'
DCOP: register 'kded' -> number of clients is now 1
DCOP: register 'anonymous-3161' -> number of clients is now 2
kio (KDirWatch): KDirWatch: Can't use FAM
kio (KDirWatch): KDirWatch: Can't use FAM
kded: Does not exist! (/root/.kde/share/servicetypes/)
kded: Does not exist! (/root/.kde/share/mimelnk/)
kded: Does not exist! (/root/.kde/share/applnk/)
kded: Does not exist! (/root/.kde/share/services/)
DCOP: register 'anonymous-3162' -> number of clients is now 3
kio (KLauncher): KLauncher: Got kdeinit_exec_wait('kbuildsycoca', ...)
kdeinit: Got EXEC_NEW 'kbuildsycoca' from launcher.
kio (KLauncher): kbuildsycoca (pid 3163) up and running.
DCOP: register 'kbuildsycoca' -> number of clients is now 4
kbuildsycoca: Recreating ksycoca file
DCOP: unregister 'kbuildsycoca'
kdeinit: PID 3163 terminated.
DCOP: unregister 'anonymous-3162'
Xlib: connection to ":0.0" refused by server Xlib: Client is not
authorized to connect to Server kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-3161' to 'kded'
DCOP: unregister 'kded'
ERROR: KUniqueApplication: DCOP communication error!
DCOP: unregister 'anonymous-3161'
kdeinit: PID 3161 terminated.
Xlib: connection to ":0.0" refused by server Xlib: Client is not
authorized to connect to Server kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
DCOP: register 'kcontrol' -> number of clients is now 1
Xlib: connection to ":0.0" refused by server Xlib: Client is not
authorized to connect to Server kcontrol: cannot connect to X server :0.0
DCOP: unregister 'kcontrol'
DCOP: register 'anonymous-3150' -> number of clients is now 1
ERROR: KUniqueApplication: Registering failed!
ERROR: KUniqueApplication: DCOP communication error!
DCOP: unregister 'anonymous-3150'
DCOPServer : slotTerminate() -> sending terminateKDE signal.
klauncher: KLauncher::process ---> terminateKDE
kdeinit: terminate KDE.
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
KLauncher: Exiting on signal 1
DCOP: unregister 'klauncher'
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
<<<<<
After chown root /tmp/.ICE-unix:
>>>>> output of kcontrol >& errors.txt
kdeinit: Launched DCOPServer, pid = 3396 result = 0
DCOP: register 'anonymous-3396' -> number of clients is now 1
DCOPServer up and running.
DCOP: unregister 'anonymous-3396'
kdeinit: Launched KLauncher, pid = 3401 result = 0
DCOP: register 'klauncher' -> number of clients is now 1
DCOP: unregister 'klauncher'
DCOP: register 'klauncher' -> number of clients is now 1
DCOP: register 'anonymous-3401' -> number of clients is now 2
DCOP: new daemon klauncher
DCOP: unregister 'anonymous-3401'
kdeinit: Launched KDED, pid = 3403 result = 0
DCOP: register 'kded' -> number of clients is now 1
DCOP: unregister 'kded'
DCOP: register 'kded' -> number of clients is now 1
DCOP: register 'anonymous-3403' -> number of clients is now 2
kio (KDirWatch): KDirWatch: Can't use FAM
kio (KDirWatch): KDirWatch: Can't use FAM
kded: Does not exist! (/root/.kde/share/servicetypes/)
kded: Does not exist! (/root/.kde/share/mimelnk/)
kded: Does not exist! (/root/.kde/share/applnk/)
kded: Does not exist! (/root/.kde/share/services/)
DCOP: register 'anonymous-3404' -> number of clients is now 3
kio (KLauncher): KLauncher: Got kdeinit_exec_wait('kbuildsycoca', ...)
kdeinit: Got EXEC_NEW 'kbuildsycoca' from launcher.
kio (KLauncher): kbuildsycoca (pid 3408) up and running.
DCOP: register 'kbuildsycoca' -> number of clients is now 4
kbuildsycoca: Recreating ksycoca file
DCOP: unregister 'kbuildsycoca'
kdeinit: PID 3408 terminated.
DCOP: unregister 'anonymous-3404'
Xlib: connection to ":0.0" refused by server Xlib: Client is not
authorized to connect to Server kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-3403' to 'kded'
DCOP: unregister 'kded'
ERROR: KUniqueApplication: DCOP communication error!
DCOP: unregister 'anonymous-3403'
kdeinit: PID 3403 terminated.
Xlib: connection to ":0.0" refused by server Xlib: Client is not
authorized to connect to Server kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
DCOP: register 'kcontrol' -> number of clients is now 1
Xlib: connection to ":0.0" refused by server Xlib: Client is not
authorized to connect to Server kcontrol: cannot connect to X server :0.0
DCOP: register 'anonymous-3392' -> number of clients is now 2
DCOP aborting call from 'anonymous-3392' to 'kcontrol'
DCOP: unregister 'kcontrol'
ERROR: KUniqueApplication: DCOP communication error!
DCOP: unregister 'anonymous-3392'
DCOPServer : slotTerminate() -> sending terminateKDE signal.
klauncher: KLauncher::process ---> terminateKDE
kdeinit: terminate KDE.
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
KLauncher: Exiting on signal 1
DCOP: unregister 'klauncher'
<<<<<
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C10C048.4080608>