[opensuse-kde3] Leap 15 w/kdm Hang on shutdown (old issue back?)
All, I have had hangs on shutdown with kdm off and on with releases over the past decade (at least back to 11.4). When I choose "Shutdown", the desktop shuts down, X shuts down, the filesystem appears to have been properly unmounted, but then the terminal hangs and I have to resort to a hard poweroff to complete the shutdown. (I'll have to enable a persistent journal to make sure the filesystem is unmounted, but it has been on all prior shutdown hangs) I know this has been discussed somewhere before, but I can't recall where. I think this may have to do with the sequence for the X server shutdown (which opensuse triggers a restart of X after all logouts), so it may be an issue where X is both shutdown and attempting to restart, resulting in a block or hold being placed on final system shutdown. How would I drill down to figure out what is causing the hang? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 08/09/2018 08:36 PM, David C. Rankin wrote:
All,
I have had hangs on shutdown with kdm off and on with releases over the past decade (at least back to 11.4). When I choose "Shutdown", the desktop shuts down, X shuts down, the filesystem appears to have been properly unmounted, but then the terminal hangs and I have to resort to a hard poweroff to complete the shutdown. (I'll have to enable a persistent journal to make sure the filesystem is unmounted, but it has been on all prior shutdown hangs)
I know this has been discussed somewhere before, but I can't recall where. I think this may have to do with the sequence for the X server shutdown (which opensuse triggers a restart of X after all logouts), so it may be an issue where X is both shutdown and attempting to restart, resulting in a block or hold being placed on final system shutdown.
How would I drill down to figure out what is causing the hang?
The odd thing (and this has always been the case), a reboot works perfectly, it is only the full shutdown that hangs after: systemd[1]: Stopped target Graphical Interface. What this misses is: systemd[1]: Stopped target Multi-User System. systemd[1]: Stopping Command Scheduler... sshd[1026]: Received signal 15; terminating. systemd[1]: Stopping Login Service... systemd[1]: Stopping OpenSSH Daemon... (and the final kernel messages stopping guest services and main) Earlier, with this install, I didn't have a problem with lightdm as the display manager, so I think it is kdm related. I have attached the log entries for a short session where I login, and then shutdown prompting the hang. If anybody has any ideas, let me know. -- David C. Rankin, J.D.,P.E.
David C. Rankin composed on 2018-08-09 20:36 (UTC-0500):
I have had hangs on shutdown with kdm off and on ...> How would I drill down to figure out what is causing the hang?
No idea, but FWIW, you're not alone, and not just with KDM3. And, it (sometimes) happens to me with TDM too. ISTR there have been trinity-users mailing list thread(s?) about it, but not whether any cause was ever found. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 2018-08-09 20:36:33 David C. Rankin wrote:
All,
I have had hangs on shutdown with kdm off and on with releases over the past decade (at least back to 11.4). When I choose "Shutdown", the desktop shuts down, X shuts down, the filesystem appears to have been properly unmounted, but then the terminal hangs and I have to resort to a hard poweroff to complete the shutdown. (I'll have to enable a persistent journal to make sure the filesystem is unmounted, but it has been on all prior shutdown hangs)
I know this has been discussed somewhere before, but I can't recall where. I think this may have to do with the sequence for the X server shutdown (which opensuse triggers a restart of X after all logouts), so it may be an issue where X is both shutdown and attempting to restart, resulting in a block or hold being placed on final system shutdown.
How would I drill down to figure out what is causing the hang?
-- David C. Rankin, J.D.,P.E.
I seem to remember seeing this a long time ago, and I think that I fixed it by tweaking the Halt setting in the Login Manager -> Shutdown pane? -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Does this happen also if you first logout from the session and then shutdown? What if you switch to the terminal with "Ctrl+Alt+F1 or F2", login as root and then enter `poweroff`? Gianluca On Fri, 10 Aug 2018, Felix Miata wrote:
David C. Rankin composed on 2018-08-09 20:36 (UTC-0500):
I have had hangs on shutdown with kdm off and on ...> How would I drill down to figure out what is causing the hang?
No idea, but FWIW, you're not alone, and not just with KDM3. And, it (sometimes) happens to me with TDM too. ISTR there have been trinity-users mailing list thread(s?) about it, but not whether any cause was ever found. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://gianluca.today/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Gianluca Interlandi composed on 2018-08-10 10:31 (UTC-0700):
Does this happen also if you first logout from the session and then shutdown? What if you switch to the terminal with "Ctrl+Alt+F1 or F2", login as root and then enter `poweroff`?
It's not a routine problem. Just now on 15.0 host big31 shutdown from greeter succeeded very quickly, unlike booting, which took 239 seconds just to load the initrd.[1] I often use the following rather than Ctrl-AltF7 and using mouse: # alias | grep ff alias Off='cd; umount -a; shutdown -h now' IIRC, it reduces the frequency of my encountering any shutdown hang, which I'm not sure only happens from trying to shutdown using greeter. I don't remember having such hang recently, only that they're very frustrating. Often I react by holding down Ctrl-Alt-Del until I see Dracut's response about KB repeats. Poweroff is a command I can't recall using more than experimentally. [1] https://www.linuxquestions.org/questions/linux-general-1/grub-legacy-delay-o... -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hi Felix, Does the slow booting have anything to do with KDE3? `poweroff` should be the same as `shutdown -h now` just like `reboot` should be the same as `shutdown -r now`. At least, I get the same behavior, but I don't know whether there are any differences between them. Curiosity, why do you umount the filesystem manually? I thought that shutdown does it for you. Gianluca On Fri, 10 Aug 2018, Felix Miata wrote:
Gianluca Interlandi composed on 2018-08-10 10:31 (UTC-0700):
Does this happen also if you first logout from the session and then shutdown? What if you switch to the terminal with "Ctrl+Alt+F1 or F2", login as root and then enter `poweroff`?
It's not a routine problem. Just now on 15.0 host big31 shutdown from greeter succeeded very quickly, unlike booting, which took 239 seconds just to load the initrd.[1] I often use the following rather than Ctrl-AltF7 and using mouse:
# alias | grep ff alias Off='cd; umount -a; shutdown -h now'
IIRC, it reduces the frequency of my encountering any shutdown hang, which I'm not sure only happens from trying to shutdown using greeter. I don't remember having such hang recently, only that they're very frustrating. Often I react by holding down Ctrl-Alt-Del until I see Dracut's response about KB repeats. Poweroff is a command I can't recall using more than experimentally.
[1] https://www.linuxquestions.org/questions/linux-general-1/grub-legacy-delay-o... -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://gianluca.today/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Gianluca Interlandi composed on 2018-08-10 12:29 (UTC-0700):
Does the slow booting have anything to do with KDE3?
Only insofar as it stifles any desire to use the PC for any kind of troubleshooting that induces or involves rebooting or shutting down, or trying to do something that should take only seconds taking 10 or more minutes twiddling thumbs due to the stalls.
`poweroff` should be the same as `shutdown -h now` just like `reboot` should be the same as `shutdown -r now`. At least, I get the same behavior, but I don't know whether there are any differences between them.
Curiosity, why do you umount the filesystem manually? I thought that shutdown does it for you.
Inexplicable remote filesystem dismounting delays many moons ago induced my jumpstarting their disconnects at reboot/shutdown times. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
I thought systemd would make booting faster. I have also noted that UEFI seems to make startup also slower. This is independent of the installed operating system. It seems to take a lot longer until you get to the very first screen after powering on a PC than it used to with BIOS. Gianluca On Fri, 10 Aug 2018, Felix Miata wrote:
Gianluca Interlandi composed on 2018-08-10 12:29 (UTC-0700):
Does the slow booting have anything to do with KDE3?
Only insofar as it stifles any desire to use the PC for any kind of troubleshooting that induces or involves rebooting or shutting down, or trying to do something that should take only seconds taking 10 or more minutes twiddling thumbs due to the stalls.
`poweroff` should be the same as `shutdown -h now` just like `reboot` should be the same as `shutdown -r now`. At least, I get the same behavior, but I don't know whether there are any differences between them.
Curiosity, why do you umount the filesystem manually? I thought that shutdown does it for you.
Inexplicable remote filesystem dismounting delays many moons ago induced my jumpstarting their disconnects at reboot/shutdown times. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://gianluca.today/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 08/10/2018 12:31 PM, Gianluca Interlandi wrote:
Does this happen also if you first logout from the session and then shutdown? What if you switch to the terminal with "Ctrl+Alt+F1 or F2", login as root and then enter `poweroff`?
Yes, It doesn't matter if you choose Logout and then choose Shudown from the DM screen, or whether you simply choose shutdown from the context menu in KDE, the result is the same. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 08/10/2018 03:58 AM, J Leslie Turriff wrote:
I seem to remember seeing this a long time ago, and I think that I fixed it by tweaking the Halt setting in the Login Manager -> Shutdown pane?
Hmm.... That gave me an idea. (it shouldn't matter as '/sbin/halt' should be linked to '/bin/systemctl poweroff'), but I made the replacement in the dialog anyway. We also need to fix the "Miscellaneous" -> Boot manager: listbox entries on the same page. There are *2* Grub entries (I suspect one should be Grub2). -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 08/11/2018 05:01 PM, David C. Rankin wrote:
Hmm....
That gave me an idea. (it shouldn't matter as '/sbin/halt' should be linked to '/bin/systemctl poweroff'), but I made the replacement in the dialog anyway.
'/bin/systemctl poweroff' did not work, but '/sbin/shutdown -h now' did... (No, I can't explain why -- yet.) When '/bin/systemctl poweroff' was set, it behaved like logout ("End Current Session"), and simply restarted X. This may be related to the /bin or /sbin being setuid in some manner that allows shutdown to run with escalated permission to actually shutdown the system, while /bin/systemctl refuses to poweroff (I guess I could try "kdesu /bin/systemctl poweroff")?? At least 'shutdown' worked on 15! -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
participants (4)
-
David C. Rankin
-
Felix Miata
-
Gianluca Interlandi
-
J Leslie Turriff