12.05.2017 16:55, Istvan Gabor пишет:
On Thu, 11 May 2017 18:57:10 +0300, Andrei Borzenkov wrote:
11.05.2017 15:52, Istvan Gabor пишет:
On Wed, 10 May 2017 19:59:54 +0300, Andrei Borzenkov wrote:
According to files you sent display manager was stopped. Before "init 3" there was active display-manager.service and Xorg was part of it; after "init 3" there is no display-manager.service and I expect if Xorg survived, service would still be considered present.
Can you actually work when you switch to vt7 or is it possible that just screen content remained?
Could you send "ps -ef" (as root) before and after "init 3" as well as "systemd-cgls"?
Thanks again.
Yes I can work in the remaining graphical desktop, it's a full functional desktop, looks like haven't been affected at all by init 3 events.
I sent ouputs of ps -ef and systemd-cgls to your address.
These are still running after init 3:
root 1742 1 0 14:17 ? 00:00:00 /opt/kde3/bin/kdm user 1859 1816 0 14:17 ? 00:00:00 /bin/sh /usr/bin/startkde3
and other kde3 related processes.
OK, one thing I missed initially.
● display-manager.service - X Display Manager Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled) Active: activating (start) since Wed 2017-05-10 14:59:45 CEST; 1min 5s ago
Note that it says "activating", not "activ" (it is misleading, "Active" != "active". Oh well ...) If for some reasons activation fails, stopping it may have observed effect. Could you please wait for more than 90 seconds (it says "1min 5s ago" here) and check "systemctl -l status display-manager.service" until it changes state to something else. Please post full output. Also after it happened please check content of /var/run/displaymanager.pid and show PID number as well. And "ls -l /var/run/displaymanager.pid".
Here are the outputs:
linux:~ # systemctl -l status display-manager.service ● display-manager.service - X Display Manager Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Fri 2017-05-12 15:44:01 CEST; 2min 31s ago
OK, I finally was able to reproduce it (what confused me initially was missing service after "init 3"). We have combination of systemd behavior with KillMode=process and some problem with creating PID file in KDE3. display-manager script is expected to create link /var/run/displaymanager.pid -> actual PID file of used DM For some reasons this does not happen with KDE3 which also means that when service is stopped, neither display-manager script nor systemd can send signal to main PID (which would be kdm in this case). Due to KillMode=process, systemd does not attempt to explicitly kill all other processes that are part of this service. The fact that service "disappears" if stopped half way through looks like systemd bug. If you wait until it finally failed to start and then do "init 3" you should at least continue to see this service (which makes it less mysterious). ...
linux:~ # ls -l /var/run/displaymanager.pid ls: cannot access '/var/run/displaymanager.pid': No such file or directory
I suggest you contact KDE3 maintainers and try to find out why link is not created. It is created using e.g. lightdm. More general question - should we rely on cooperating DM to clean up after itself or simply use systemd to forcibly terminate everything. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org