On 05.09.2014 17:21, Yamaban wrote:
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)
Yes.
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
$ ps auxf | grep kdm USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1441 0.0 0.0 28752 2036 ? Ss Sep03 0:00 /usr/bin/kdm root 22099 3.0 1.4 292340 118460 tty7 Ss+ 11:10 11:53 \_ /usr/bin/Xorg -br :0 vt7 -nolisten tcp -seat seat0 -auth /var/lib/kdm/AuthFiles/A:0-ypVKia So, X is from this morning, but kdm is two days old.
So without logging out of X11, a restart of the DM (here kdm) is not possible.
Yes.
Should kdm stand on the login screen, the is usually a option to restart kdm / X11 (can be disabled via config).
Otherwise with kdm at the login screen, try to kill kdm from a tty as root with "killall kdm", either kdm respawns (with the fresh binary) or try to use "systemctl stop xdm.service", wait for error messages, and "systemctl start xdm.service" afterwards if no errors are shown.
What I did this morning was 1) installing latest updates (via apper-plasmoid) 2) log out of KDE 3) log in to console 4) sudo zypper ps, which listed kdm 5) sudo systemctl restart xdm.service Normally, this would restart kdm and take me to the graphical login on vt 7. It did not. It did not report anything either. 'zypper ps' still listed kdm I saw this behaviour already two or three days ago. Then, I did the 'kill <pidofkdm>', which pretty much "ruined" my system and I had to reboot. I have no idea, why that happend, but I did not want to do it again. On the graphical console I could get the screen to flash by pressing Ctrl-Alt-Backspace twice, which in my opinion should restart X. But the kdm process stayed. Normally, stopping kdm should disable the graphical login. It did not. Then I tried stopping it. $ sudo systemclt stop xdm.service did not report errors. kdm stays alive. $ systemctl status xdm.service xdm.service - LSB: X Display Manager Loaded: loaded (/etc/init.d/xdm) Active: inactive (dead) since Fri, 2014-09-05 11:10:24 CEST; 6h ago Process: 22085 ExecStop=/etc/init.d/xdm stop (code=exited, status=0/SUCCESS) Process: 21836 ExecStart=/etc/init.d/xdm start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/xdm.service ├ 1441 /usr/bin/kdm └ 22099 /usr/bin/Xorg -br :0 vt7 -nolisten tcp -seat seat0... I did not understand this. Hence, I logged back in KDE and wrote my first mail of this thread. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org