
On 09/05/2014 11:21 AM, Yamaban wrote:
On Fri, 5 Sep 2014 16:19, mararm <mararm@...> wrote:
On 05.09.2014 16:06, Anton Aylward wrote:
On 09/05/2014 09:14 AM, mararm wrote:
kdm.log shows
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again.
but this seems to be an older message. The now existing /tmp/.X0-lock is dated today, 11:10, which is roughly the time I tried to restart kdm.
*sigh*
Then remove it and try again.
The 'try again' part is what bothers me. kdm won't stop. And rebooting is no option for the moment (this is @work).
To give a little light into the display-manager workings:
Start: the DM (here kdm) starts, pulls up and starts X11, waits for login. Login: DM validates the creditales (Account / pw), starts the user session (here possible start_kde) Logout: The user session ends, DM takes over X11 displays login again. Stop: Only possible during wait for login, kills X11, ends DM (here kdm)
Take-out from running session, using "ps auxf", here lxdm / xfce : USER PID TTY STAT TIME COMMAND root 1969 ? Ss 0:00 /usr/bin/lxdm -d root 1971 tty7 Ss+ 1124:46 \_ /usr/bin/X :0 vt07 -nolisten tcp mf 2213 ? Ss 0:00 \_ /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc
So without logging out of X11, a restart of the DM (here kdm) is not possible.
While there is a similar structure for running KDE root 1365 0.0 0.0 24616 444 ? Ss Sep04 0:00 /usr/bin/kdm root 1380 1.8 4.5 397256 180056 tty7 Ss+ Sep04 29:15 \_ /usr/bin/Xorg -br :0 vt7 -nolisten tcp -auth /var/lib/kdm/AuthFiles/A:0-ztNU1b root 1389 0.0 0.0 76100 836 ? S Sep04 0:00 \_ -:0 anton 1475 0.0 0.0 13092 388 ? Ss Sep04 0:00 \_ /bin/sh /usr/bin/startkde anton 1671 0.0 0.0 17056 304 ? Ss Sep04 0:02 \_ /usr/bin/gpg-agent --sh --daemon --write-env-file /home/anton/.gnupg/agent.info /etc/X11/xinit/xinitrc anton 1785 0.0 0.0 4224 48 ? S Sep04 0:00 \_ kwrapper4 ksmserver I disagree about the need to log out of X11. Man times after a zypper update I've simply restarted 'xdm.service', which is how my DM is controller, even though it is named kdm. What happens is that the signal propagates down to shut down all the applications running under KDE, then KDE shuts down, certainly cleanly enough to allow the apps to be restarted, then X11 shuts down then kdm shuts down, and then restarts. How do I kow this? After the zypper update I run 'zypper ps' and it tells me that many running binaries need to be restared AMONG THEM KDM. After doing the 'systemctl restart xdm.xervice' I run 'zypper ps' again and it gives me an all clear. so the 'new' version of kdm is running. Not need to use 'kill' or 'killall'. Systemctl manages things quite well thank you. Of course you may have unit files miconfigured to the dependency tree isn't aware of things, but that's a different problem. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ - -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org