[opensuse] init 3 in openSUSE Leap 42.2
Hello: In openSUSE Leap 42.2 in a terminal (vt1-vt6) init 3 (run by root) doesn't have effect. It gives back cursor but doesn't turn off graphical interface. Was this option removed in 42.2, if yes, where is it documented? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
09.05.2017 20:18, Istvan Gabor пишет:
Hello:
In openSUSE Leap 42.2 in a terminal (vt1-vt6) init 3 (run by root) doesn't have effect. It gives back cursor but doesn't turn off graphical interface. Was this option removed in 42.2, if yes, where is it documented?
I do not understand what "gives back cursor" means nor how do you determine that graphical interface is on or off. When I do "init 3" on vt1 I see that display manager is stopped together with X server. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 9 May 2017 20:47:17 +0300, Andrei Borzenkov wrote:
09.05.2017 20:18, Istvan Gabor пишет:
Hello:
In openSUSE Leap 42.2 in a terminal (vt1-vt6) init 3 (run by root) doesn't have effect. It gives back cursor but doesn't turn off graphical interface. Was this option removed in 42.2, if yes, where is it documented?
I do not understand what "gives back cursor" means nor how do you determine that graphical interface is on or off. When I do "init 3" on vt1 I see that display manager is stopped together with X server.
Thank you Andrei. I try to describe it. After starting the computer the system boots into graphical mode and shows a graphical login window on vt7. I login here to my graphical desktop (KDE3). Then I switch to vt1 by ctrl+alt+F1. I login here into vt1 as root. I get the cursor and I type init 3: # init 3 # After typing init 3 nothing happens, # and blinking cursor is shown in a new line. I can switch back to vt7 by ctrl+alt+7 to where I left off my desktop. I would expect the X server turned off and a blank black screen on vt7. According to your answer this is not normal. How to investigate it? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
09.05.2017 21:03, Istvan Gabor пишет:
On Tue, 9 May 2017 20:47:17 +0300, Andrei Borzenkov wrote:
09.05.2017 20:18, Istvan Gabor пишет:
Hello:
In openSUSE Leap 42.2 in a terminal (vt1-vt6) init 3 (run by root) doesn't have effect. It gives back cursor but doesn't turn off graphical interface. Was this option removed in 42.2, if yes, where is it documented?
I do not understand what "gives back cursor" means nor how do you determine that graphical interface is on or off. When I do "init 3" on vt1 I see that display manager is stopped together with X server.
Thank you Andrei.
I try to describe it. After starting the computer the system boots into graphical mode and shows a graphical login window on vt7. I login here to my graphical desktop (KDE3). Then I switch to vt1 by ctrl+alt+F1. I login here into vt1 as root. I get the cursor and I type init 3:
# init 3 #
After typing init 3 nothing happens, # and blinking cursor is shown in a new line.
You get back shell prompt. What else did you expect here?
I can switch back to vt7 by ctrl+alt+7 to where I left off my desktop. I would expect the X server turned off and a blank black screen on vt7.
According to your answer this is not normal.
Correct, that is not what I expect and see here.
How to investigate it?
Start with checking "journalctl -b" - was shutdown of display manager attempted? If in doubt - upload result to e.g. http://susepaste.org/. In this case "systemctl show '*'" and probably "systemctl status '*'" before and after "init 3" would be useful as well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 9 May 2017 21:13:23 +0300, Andrei Borzenkov wrote:
09.05.2017 21:03, Istvan Gabor пишет:
On Tue, 9 May 2017 20:47:17 +0300, Andrei Borzenkov wrote:
09.05.2017 20:18, Istvan Gabor пишет:
Hello:
In openSUSE Leap 42.2 in a terminal (vt1-vt6) init 3 (run by root) doesn't have effect. It gives back cursor but doesn't turn off graphical interface. Was this option removed in 42.2, if yes, where is it documented?
I do not understand what "gives back cursor" means nor how do you determine that graphical interface is on or off. When I do "init 3" on vt1 I see that display manager is stopped together with X server.
Thank you Andrei.
I try to describe it. After starting the computer the system boots into graphical mode and shows a graphical login window on vt7. I login here to my graphical desktop (KDE3). Then I switch to vt1 by ctrl+alt+F1. I login here into vt1 as root. I get the cursor and I type init 3:
# init 3 #
After typing init 3 nothing happens, # and blinking cursor is shown in a new line.
You get back shell prompt. What else did you expect here?
I can switch back to vt7 by ctrl+alt+7 to where I left off my desktop. I would expect the X server turned off and a blank black screen on vt7.
According to your answer this is not normal.
Correct, that is not what I expect and see here.
How to investigate it?
Start with checking "journalctl -b" - was shutdown of display manager attempted? If in doubt - upload result to e.g. http://susepaste.org/. In this case "systemctl show '*'" and probably "systemctl status '*'" before and after "init 3" would be useful as well.
Thank you Andrei. I tried to paste the outputs into susepaste but it did not accept all outputs. Therefore I sent the output results to your email address. Thanks again, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
10.05.2017 16:44, Istvan Gabor пишет:
On Tue, 9 May 2017 21:13:23 +0300, Andrei Borzenkov wrote:
09.05.2017 21:03, Istvan Gabor пишет:
On Tue, 9 May 2017 20:47:17 +0300, Andrei Borzenkov wrote:
09.05.2017 20:18, Istvan Gabor пишет:
Hello:
In openSUSE Leap 42.2 in a terminal (vt1-vt6) init 3 (run by root) doesn't have effect. It gives back cursor but doesn't turn off graphical interface. Was this option removed in 42.2, if yes, where is it documented?
I do not understand what "gives back cursor" means nor how do you determine that graphical interface is on or off. When I do "init 3" on vt1 I see that display manager is stopped together with X server.
Thank you Andrei.
I try to describe it. After starting the computer the system boots into graphical mode and shows a graphical login window on vt7. I login here to my graphical desktop (KDE3). Then I switch to vt1 by ctrl+alt+F1. I login here into vt1 as root. I get the cursor and I type init 3:
# init 3 #
After typing init 3 nothing happens, # and blinking cursor is shown in a new line.
You get back shell prompt. What else did you expect here?
I can switch back to vt7 by ctrl+alt+7 to where I left off my desktop. I would expect the X server turned off and a blank black screen on vt7.
According to your answer this is not normal.
Correct, that is not what I expect and see here.
How to investigate it?
Start with checking "journalctl -b" - was shutdown of display manager attempted? If in doubt - upload result to e.g. http://susepaste.org/. In this case "systemctl show '*'" and probably "systemctl status '*'" before and after "init 3" would be useful as well.
Thank you Andrei.
I tried to paste the outputs into susepaste but it did not accept all outputs. Therefore I sent the output results to your email address.
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"? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov composed on 2017-05-11 18:57 (UTC+0300):
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".
Thu May 11 14:19:06 EDT 2017 big41:~ # grep RETT /etc/*lease /etc/os-release:PRETTY_NAME="openSUSE Leap 42.2" big41:~ # 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 Thu 2017-05-11 14:20:16 EDT; 36s ago Process: 1131 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS) Tasks: 4 (limit: 512) CGroup: /system.slice/display-manager.service ââ1158 /opt/kde3/bin/kdm ââ1164 /usr/bin/Xorg -br -nolisten tcp :0 vt7 -auth /var/lib/xdm/authdir/authfiles/A:0-lwsuVy ââ1167 -:0 ââ1168 /opt/kde3/bin/kdm_greet May 11 14:18:46 big41 display-manager[1131]: Starting service kdm..done May 11 14:18:46 big41 systemd[1]: display-manager.service: PID file /var/run/displaymanager.pid not readable (yet?) after start: No such file or directory May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'AllowRootLogin' in section [X-*-Core] of /opt/kde3/share/config/kdm/kdmrc May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'AllowNullPasswd' in section [X-:*-Core] of /opt/kde3/share/config/kdm/kdmrc May 11 14:20:16 big41 systemd[1]: display-manager.service: Start operation timed out. Terminating. May 11 14:20:16 big41 systemd[1]: Failed to start X Display Manager. May 11 14:20:16 big41 systemd[1]: display-manager.service: Unit entered failed state. May 11 14:20:16 big41 systemd[1]: display-manager.service: Failed with result 'timeout'. big41:~ # init 3 big41:~ # ps -A | grep dm 1158 ? 00:00:00 kdm 1167 ? 00:00:00 kdm 1168 ? 00:00:00 kdm_greet big41:~ # cat /proc/cmdline root=LABEL=s422p10sv5 ipv6.disable=1 net.ifnames=0 noresume vga=791 video=1440x900@60 5 big41:~ # systemctl get-default multi-user.target big41:~ # ll /var/run/displaymanager.pid /var/run/kdm.pid ls: cannot access '/var/run/displaymanager.pid': No such file or directory -rw-r--r-- 1 root root 5 May 11 14:18 /var/run/kdm.pid big41:~ # cat /var/run/kdm.pid 1158 big41:~ # 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 Thu 2017-05-11 14:20:16 EDT; 8min ago Process: 1131 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS) Tasks: 4 (limit: 512) CGroup: /system.slice/display-manager.service ââ1158 /opt/kde3/bin/kdm ââ1164 /usr/bin/Xorg -br -nolisten tcp :0 vt7 -auth /var/lib/xdm/authdir/authfiles/A:0-lwsuVy ââ1167 -:0 ââ1168 /opt/kde3/bin/kdm_greet May 11 14:18:46 big41 display-manager[1131]: Starting service kdm..done May 11 14:18:46 big41 systemd[1]: display-manager.service: PID file /var/run/displaymanager.pid not readable (yet?) after start: No such file or directory May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'AllowRootLogin' in section [X-*-Core] of /opt/kde3/share/config/kdm/kdmrc May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'AllowNullPasswd' in section [X-:*-Core] of /opt/kde3/share/config/kdm/kdmrc May 11 14:20:16 big41 systemd[1]: display-manager.service: Start operation timed out. Terminating. May 11 14:20:16 big41 systemd[1]: Failed to start X Display Manager. May 11 14:20:16 big41 systemd[1]: display-manager.service: Unit entered failed state. May 11 14:20:16 big41 systemd[1]: display-manager.service: Failed with result 'timeout'. big41:~ # ps -A | grep dm 1158 ? 00:00:00 kdm 1167 ? 00:00:00 kdm 1168 ? 00:00:00 kdm_greet big41:~ # killall kdm big41:~ # ps -A | grep dm big41:~ # 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 Thu 2017-05-11 14:20:16 EDT; 10min ago Process: 1131 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 512) May 11 14:18:46 big41 display-manager[1131]: Starting service kdm..done May 11 14:18:46 big41 systemd[1]: display-manager.service: PID file /var/run/displaymanager.pid not readable (yet?) after start: No such file or directory May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'AllowRootLogin' in section [X-*-Core] of /opt/kde3/share/config/kdm/kdmrc May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc May 11 14:18:46 big41 kdm_config[1159]: Multiple occurrences of key 'AllowNullPasswd' in section [X-:*-Core] of /opt/kde3/share/config/kdm/kdmrc May 11 14:20:16 big41 systemd[1]: display-manager.service: Start operation timed out. Terminating. May 11 14:20:16 big41 systemd[1]: Failed to start X Display Manager. May 11 14:20:16 big41 systemd[1]: display-manager.service: Unit entered failed state. May 11 14:20:16 big41 systemd[1]: display-manager.service: Failed with result 'timeout'. big41:~ # ll /var/run/displaymanager.pid /var/run/kdm.pid ls: cannot access '/var/run/displaymanager.pid': No such file or directory -rw-r--r-- 1 root root 5 May 11 14:18 /var/run/kdm.pid big41:~ # cat /var/run/kdm.pid 1158 big41:~ # kill -9 1158 -bash: kill: (1158) - No such process big41:~ # cat /var/run/kdm.pid 1158 big41:~ # ps -A | grep dm big41:~ # -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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 Process: 1595 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 512) CGroup: /system.slice/display-manager.service ├─1689 /opt/kde3/bin/kdm └─1755 /usr/bin/Xorg -br -nolisten tcp :0 vt7 -auth /var/lib/xdm/authdir/authfiles/A:0-35oK4O May 12 15:42:34 linux kdm_config[1751]: Multiple occurrences of key 'Language' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc May 12 15:42:34 linux kdm_config[1751]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc May 12 15:42:34 linux kdm_config[1751]: Multiple occurrences of key 'UseBackground' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc May 12 15:42:34 linux kdm_config[1751]: Multiple occurrences of key 'AllowShutdown' in section [X-:*-Core] of /opt/kde3/share/config/kdm/kdmrc May 12 15:42:34 linux kdm_config[1751]: Multiple occurrences of key 'AutoLoginEnable' in section [X-:0-Core] of /opt/kde3/share/config/kdm/kdmrc May 12 15:42:48 linux kdm[1763]: :0[1763]: pam_unix(xdm:session): session opened for user user by (uid=0) May 12 15:44:01 linux systemd[1]: display-manager.service: Start operation timed out. Terminating. May 12 15:44:01 linux systemd[1]: Failed to start X Display Manager. May 12 15:44:01 linux systemd[1]: display-manager.service: Unit entered failed state. May 12 15:44:01 linux systemd[1]: display-manager.service: Failed with result 'timeout'. linux:~ # ls -l /var/run/displaymanager.pid ls: cannot access '/var/run/displaymanager.pid': No such file or directory linux:~ # cat /var/run/displaymanager.pid cat: /var/run/displaymanager.pid: No such file or directory Looks the ~same as Felix' output. Thanks again, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 09/05/2017 19:18, Istvan Gabor wrote:
Hello:
In openSUSE Leap 42.2 in a terminal (vt1-vt6) init 3 (run by root) doesn't have effect. It gives back cursor but doesn't turn off graphical interface. Was this option removed in 42.2, if yes, where is it documented?
Thanks,
Istvan
You have to enable "Multi User System" to get this feature back. The easiest way is in Yast2 Services Manager it's under "Default System Target" top left. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 11 May 2017 08:59:20 +0200, Dave Plater wrote:
On 09/05/2017 19:18, Istvan Gabor wrote:
Hello:
In openSUSE Leap 42.2 in a terminal (vt1-vt6) init 3 (run by root) doesn't have effect. It gives back cursor but doesn't turn off graphical interface. Was this option removed in 42.2, if yes, where is it documented?
Thanks,
Istvan
You have to enable "Multi User System" to get this feature back. The easiest way is in Yast2 Services Manager it's under "Default System Target" top left. Dave P
Hi Dave, This doesn't work in my system. The default system target originally was Graphical Interface and I changed it according to your note to Multi-User System. After restarting the computer the graphical interface did not start automatically. I logged in on vt1 and could start the graphical interface by typing "init 5" but I did not get back the cursor for long time, I had to hit ctrl+C which gave back the cursor. The graphical system stayed on after interrupting init 5 by ctrl+C. But "init 3" still did not turn the graphical interface off. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Istvan Gabor
On Thu, 11 May 2017 08:59:20 +0200, Dave Plater wrote:
On 09/05/2017 19:18, Istvan Gabor wrote:
Hello:
In openSUSE Leap 42.2 in a terminal (vt1-vt6) init 3 (run by root) doesn't have effect. It gives back cursor but doesn't turn off graphical interface. Was this option removed in 42.2, if yes, where is it documented?
Thanks,
Istvan
You have to enable "Multi User System" to get this feature back. The easiest way is in Yast2 Services Manager it's under "Default System Target" top left. Dave P
Hi Dave,
This doesn't work in my system. The default system target originally was Graphical Interface and I changed it according to your note to Multi-User System. After restarting the computer the graphical interface did not start automatically. I logged in on vt1 and could start the graphical interface by typing "init 5" but I did not get back the cursor for long time, I had to hit ctrl+C which gave back the cursor. The graphical system stayed on after interrupting init 5 by ctrl+C. But "init 3" still did not turn the graphical interface off.
Thanks,
Istvan
What do you see when you type this command: # ls -l /usr/lib/systemd/system|grep graph lrwxrwxrwx 1 root root 16 Apr 25 08:38 default.target -> graphical.target -rw-r--r-- 1 root root 558 Apr 25 08:38 graphical.target drwxr-xr-x 2 root root 4096 May 6 22:24 graphical.target.wants lrwxrwxrwx 1 root root 16 Apr 25 08:38 runlevel5.target -> graphical.target Or # ls -l /usr/lib/systemd/system|grep runlevel lrwxrwxrwx 1 root root 15 Apr 25 08:38 runlevel0.target -> poweroff.target lrwxrwxrwx 1 root root 13 Apr 25 08:38 runlevel1.target -> rescue.target drwxr-xr-x 2 root root 4096 Apr 25 08:38 runlevel1.target.wants lrwxrwxrwx 1 root root 17 Apr 25 08:38 runlevel2.target -> multi-user.target drwxr-xr-x 2 root root 4096 Apr 25 08:38 runlevel2.target.wants lrwxrwxrwx 1 root root 17 Apr 25 08:38 runlevel3.target -> multi-user.target drwxr-xr-x 2 root root 4096 Apr 25 08:38 runlevel3.target.wants lrwxrwxrwx 1 root root 17 Apr 25 08:38 runlevel4.target -> multi-user.target drwxr-xr-x 2 root root 4096 Apr 25 08:38 runlevel4.target.wants lrwxrwxrwx 1 root root 16 Apr 25 08:38 runlevel5.target -> graphical.target drwxr-xr-x 2 root root 4096 Apr 25 08:38 runlevel5.target.wants lrwxrwxrwx 1 root root 13 Apr 25 08:38 runlevel6.target -> reboot.target -rw-r--r-- 1 root root 761 Apr 25 08:38 systemd-update-utmp-runlevel.service You could try using telinit instead of init, but I think they do the same thing. Or you could try: # systemctl stop graphical.target -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Richmond
# systemctl stop graphical.target
Actually I think that's wrong, it should be: systemctl multi-user.target I don't want to try it at the moment, too many windows open. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-11 08:59, Dave Plater wrote:
On 09/05/2017 19:18, Istvan Gabor wrote:
Hello:
In openSUSE Leap 42.2 in a terminal (vt1-vt6) init 3 (run by root) doesn't have effect. It gives back cursor but doesn't turn off graphical interface. Was this option removed in 42.2, if yes, where is it documented?
You have to enable "Multi User System" to get this feature back. The easiest way is in Yast2 Services Manager it's under "Default System Target" top left.
No, that would be to have it permanent. Not the case. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Dave Plater -
Felix Miata -
Istvan Gabor -
Richmond