[opensuse] expected behavior when systemctl isolate is run
Hello: I tried to run systemctl isolate commands as it's suggested in a different thread (audio config) and I have a feeling that it doesn't work as expected. I use openSUSE 13.1 with KDE3 desktop and kdm3 login manager. First I tried to run the command in a KDE3 konsole window (I closed all applications before running the command):
su # systemctl isolate multi-user.target
After this the graphical desktop window (on vt7) disappears and the screen becomes blank but the mouse pointer stays on the screen, it doesn't disappear. When switching to other terminal (vt 1-6) by CTRL+ALT+F[1-6] the login message is shown and the mouse pointer is shown too (on each 1-6 terminals). In addition, switching target doesn't log out the user who was logged in to the graphical desktop: # w 17:43:43 up 6 days, 5:40, 3 users, load average: 0.21, 0.61, 0.90 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT user :0 console 13Oct16 ?xdm? 1:40m 0.06s /bin/sh /opt/kde3/bin/startkde user console :0 13Oct16 6days 0.00s 0.06s /bin/sh /opt/kde3/bin/startkde root tty2 17:43 7.00s 0.04s 0.00s w After this I tried to switch back to graphical target: # systemctl isolate runlevel5.target but it doesn't give back the graphical login screen. If I run "killall starkde" the graphical login screen appears on vt7. What happens if I try to change target when graphical state is active but no one is logged in to KDE3? Running "systemctl isolate multi-user.target" turns graphical login screen off, without traces (no mouse pointer on screen). OK. If I try to switch back to graphical target: # systemctl isolate runlevel5.target the graphical window doesn't appear. If I switch to vt7 (CTRL+ALT+F7) only log messages are shown instead of KDE3 login screen and I can not switch away from this screen. I can't get away from this screen (by pressing any keyboard combination). I must press reset button to restart the system. Another thing: after running any systemctl isolate command it takes the cursor 32 seconds to reappear. I think it's too long. What I'd expect from running systemctl isolate commands: -to multi-user: switch to multiuser state and log out user logged in to graphical desktop -come into effect much faster, maximum a few seconds instead of 32 seconds -to runlevel5: switch to graphical target and show login screen -when switching to vt7, not to stick there It used to work like that earlier when init [35] commands changed runlevels. Any comment? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Istvan Gabor <suseuser04@freemail.hu> [10-19-16 13:03]:
Hello:
I tried to run systemctl isolate commands as it's suggested in a different thread (audio config) and I have a feeling that it doesn't work as expected.
I use openSUSE 13.1 with KDE3 desktop and kdm3 login manager.
First I tried to run the command in a KDE3 konsole window (I closed all applications before running the command):
su # systemctl isolate multi-user.target
After this the graphical desktop window (on vt7) disappears and the screen becomes blank but the mouse pointer stays on the screen, it doesn't disappear. When switching to other terminal (vt 1-6) by CTRL+ALT+F[1-6] the login message is shown and the mouse pointer is shown too (on each 1-6 terminals). In addition, switching target doesn't log out the user who was logged in to the graphical desktop:
# w 17:43:43 up 6 days, 5:40, 3 users, load average: 0.21, 0.61, 0.90 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT user :0 console 13Oct16 ?xdm? 1:40m 0.06s /bin/sh /opt/kde3/bin/startkde user console :0 13Oct16 6days 0.00s 0.06s /bin/sh /opt/kde3/bin/startkde root tty2 17:43 7.00s 0.04s 0.00s w
After this I tried to switch back to graphical target:
# systemctl isolate runlevel5.target
but it doesn't give back the graphical login screen. If I run "killall starkde" the graphical login screen appears on vt7.
What happens if I try to change target when graphical state is active but no one is logged in to KDE3?
Running "systemctl isolate multi-user.target" turns graphical login screen off, without traces (no mouse pointer on screen). OK.
If I try to switch back to graphical target:
# systemctl isolate runlevel5.target
the graphical window doesn't appear. If I switch to vt7 (CTRL+ALT+F7) only log messages are shown instead of KDE3 login screen and I can not switch away from this screen. I can't get away from this screen (by pressing any keyboard combination). I must press reset button to restart the system.
Another thing: after running any systemctl isolate command it takes the cursor 32 seconds to reappear. I think it's too long.
What I'd expect from running systemctl isolate commands: -to multi-user: switch to multiuser state and log out user logged in to graphical desktop -come into effect much faster, maximum a few seconds instead of 32 seconds -to runlevel5: switch to graphical target and show login screen -when switching to vt7, not to stick there
It used to work like that earlier when init [35] commands changed runlevels.
Any comment?
yes, you failed to advise: openSUSE 13.1 with KDE3 desktop and kdm3 login manager all bets are off, kde3 is not supported -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-19 19:03, Istvan Gabor wrote:
Hello:
I tried to run systemctl isolate commands as it's suggested in a different thread (audio config) and I have a feeling that it doesn't work as expected.
I use openSUSE 13.1 with KDE3 desktop and kdm3 login manager.
Just try init 3, init 5, those commands are supported. I never run them from inside a graphical terminal. I first log out of X, go to console, login as root, do it - I do not expect a process started on a terminal that is going to be killed to end properly. It is possible that some user processes remain, so I kill them manually. I even have a little script to kill the typical recalcitrants -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. composed on 2016-10-19 19:38 (UTC+0200):
On 2016-10-19 19:03 (UTC+0200), Istvan Gabor wrote:
I tried to run systemctl isolate commands as it's suggested in a different thread (audio config) and I have a feeling that it doesn't work as expected.
I use openSUSE 13.1 with KDE3 desktop and kdm3 login manager.
Just try init 3, init 5, those commands are supported.
I never run them from inside a graphical terminal. I first log out of X, go to console, login as root, do it - I do not expect a process started on a terminal that is going to be killed to end properly.
It is possible that some user processes remain, so I kill them manually. I even have a little script to kill the typical recalcitrants
IOW, runlevel switching in 13.1 using KDE3 is broken now, as it has been ever since 13.1 release, probably since 12.3 or before. Post-11.4 I've always just rebooted when wishing to get to 3 from 5. It's simpler than figuring out what didn't get stopped and dealing with it. -- "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 2016-10-19 19:58, Felix Miata wrote:
Carlos E. R. composed on 2016-10-19 19:38 (UTC+0200):
On 2016-10-19 19:03 (UTC+0200), Istvan Gabor wrote:
I tried to run systemctl isolate commands as it's suggested in a different thread (audio config) and I have a feeling that it doesn't work as expected.
I use openSUSE 13.1 with KDE3 desktop and kdm3 login manager.
Just try init 3, init 5, those commands are supported.
I never run them from inside a graphical terminal. I first log out of X, go to console, login as root, do it - I do not expect a process started on a terminal that is going to be killed to end properly.
It is possible that some user processes remain, so I kill them manually. I even have a little script to kill the typical recalcitrants
IOW, runlevel switching in 13.1 using KDE3 is broken now, as it has been ever since 13.1 release, probably since 12.3 or before. Post-11.4 I've always just rebooted when wishing to get to 3 from 5. It's simpler than figuring out what didn't get stopped and dealing with it.
I guess that what is broken is kdm3, so the solution would be to use a different one. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. composed on 2016-10-19 20:03 (UTC+0200):
Felix Miata wrote:
IOW, runlevel switching in 13.1 using KDE3 is broken now, as it has been ever since 13.1 release, probably since 12.3 or before. Post-11.4 I've always just rebooted when wishing to get to 3 from 5. It's simpler than figuring out what didn't get stopped and dealing with it.
I guess that what is broken is kdm3, so the solution would be to use a different one.
If you can get by on the feature subset all the others offer. One of these days I need to take notice whether TDM produces the same problem, both in openSUSE, and in the other systemd distros on which I have TDE installed. Were it not for https://bugzilla.mozilla.org/show_bug.cgi?id=1269274 were TDM working as expected there would probably induce me to upgrade to 42.2 and from KDE3 to TDE soon. -- "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
19.10.2016 20:38, Carlos E. R. пишет:
On 2016-10-19 19:03, Istvan Gabor wrote:
Hello:
I tried to run systemctl isolate commands as it's suggested in a different thread (audio config) and I have a feeling that it doesn't work as expected.
I use openSUSE 13.1 with KDE3 desktop and kdm3 login manager.
Just try init 3, init 5, those commands are supported.
init 3 or init 5 under systemd are exact equivalent (aliases) to "systemctl isolate multi-user.target" and "systemctl isolate graphical.target"
I never run them from inside a graphical terminal. I first log out of X, go to console, login as root, do it - I do not expect a process started on a terminal that is going to be killed to end properly.
It is possible that some user processes remain, so I kill them manually. I even have a little script to kill the typical recalcitrants
Istvan Gabor composed on 2016-10-19 13:03 (UTC-0400):
What I'd expect from running systemctl isolate commands: -to multi-user: switch to multiuser state and log out user logged in to graphical desktop -come into effect much faster, maximum a few seconds instead of 32 seconds -to runlevel5: switch to graphical target and show login screen -when switching to vt7, not to stick there
It used to work like that earlier when init [35] commands changed runlevels.
Any comment?
Be thankful KDE3 is still available at all, and reboot when you need to switch to 3 rather than expecting systemd to work like sysvinit with KDM3. Virtually all KDE3 devs have moved to TDE - by now maybe it's 100%. Dev activity on BOO for KDE3 bugs last seen >4 months ago and all from then are GCC6 build failure reports. :-( My virtually blind friend is stuck with 13.1 and 13.2 because KTTSMgr's Festival sounds won't work in 42.1: https://bugzilla.opensuse.org/show_bug.cgi?id=981271 -- "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
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
Felix Miata -
Istvan Gabor -
Patrick Shanahan