System hangs on shutdown with a message

Xoloitzcuintli · 2022-05-23 14:42:06

Hi!
I recently did a fresh install of Arch, and I have came across an odd issue whenever I shutdown my pc.
Whenever I do, a messages pops up saying:

"Broadcast message from march@Mark-Arch (Mon 2022-05-23 06:25:45 UTC):
The system is going down for poweroff NOW!"

Here is a photo of the message: https://imgur.com/a/VZyweek

The message will stay there for a good minute or two before my system finally powers off.
Its an annoyance for me, how would one go about turning this message off?

Thanks!

V1del · 2022-05-23 14:52:02

You are shutting down how exactly? This is normal and expected if you use the "old" shutdown -h now commands/symlinks without the --no-wall argument.

Last edited by V1del (2022-05-23 14:52:26)

Xoloitzcuintli · 2022-05-23 15:24:38

I am shutting down normally through the shut down button in KDE.
I've installed Arch w/KDE before and never had this happen before.

seth · 2022-05-23 18:33:49

Remove the quiet parameter from the boot and any plymouth stuff, resp. check the journal for the previous boot (sudo journalctl -b -1) after the reboot.
If there're some forcefull kwin_x11 terminations at the tail, this is a common issue, see eg. https://bbs.archlinux.org/viewtopic.php?id=269549
You'd then not encouter this when first logging out and then shutting down from the DM (likely SDDM)

arthurflor23 · 2022-05-24 13:24:57

A few days ago, I noticed this same message on shutdown.
I'm using gnome and both the shutdown by the menu and the command directly (gnome-session-quit --power-off) is possible to get the message.

Using the shutdown command with --no-wall parameter, the message is not displayed.

Still, it's strange, as this is new to the system, which it didn't have before.

Zod · 2022-05-24 13:35:04

Looks like it might have been in the works for a while?

https://github.com/systemd/systemd/issues/8424

Edit: I noticed it with plasma's shutdown button.

Last edited by Zod (2022-05-24 13:36:04)

qarkai · 2022-05-24 18:12:33

Same here with Xfce and LightDM. I believe it started after systemd 251 update.

phcerdan · 2022-05-25 08:49:20

Getting the broadcast message after suspending (via gnome GUI / gdm) in 10+ terminals in tmux is incredibly annoying.
Any hint on how to revert it to the old behavior?

seth · 2022-05-25 14:12:08

Downgrade the system to a version w/ systemd < 251

If the message doesn't come from root, running "mesg n" in the terminal should™ block the message.

qarkai · 2022-05-25 18:06:10

For the record: systemd 251.1 doesn't fix issue.

V1del · 2022-05-25 18:25:40

It's technically not an issue, and if we follow the bug report linked earlier then this change was made in order to make the code actually behave as documented in documentation.

You could open a feature request on systemd to make the default behaviour configurable, nag every DE implementor to please call the relevant command with --no-wall, or make your own wrapper script that catches relevant operations and appends the --no-wall into /usr/local/ or so and hope everything just relies on the path (... you probably really only want to do that last one if you know exactly what you are doing and are prepared to repair from an emergency shell/live disk)

seth · 2022-05-25 19:23:23

V1del wrote:

It's technically not an issue

but

The OP wrote:

The message will stay there for a good minute or two before my system finally powers off.

The OP also wrote:

I am shutting down normally through the shut down button in KDE.

=> https://bbs.archlinux.org/viewtopic.php … 7#p2037437

For everyone else who hooked onto this thread, maybe please clarify whether the systemd 251 update got you shutdown hangs or whether you're just annoyed by the (I guess beep from pcspkr and the) message.

Zod · 2022-05-25 19:42:36

I did notice it while I was using plasma/kde . I suppose it was sddm shutdown button.

It did not cause any problem, and only displayed for about ~3 seconds.

I found it interesting enough to track it down to the link I provided.

qarkai · 2022-05-25 20:45:20

seth wrote:

please clarify whether the systemd 251 update got you shutdown hangs or whether you're just annoyed by the (I guess beep from pcspkr and the) message.

It hangs but not for long time, less than a minute.

V1del wrote:

nag every DE implementor to please call the relevant command with --no-wall

xfce4-session issue: https://gitlab.xfce.org/xfce/xfce4-session/-/issues/138.

seth · 2022-05-25 21:15:13

It hangs but not for long time, less than a minute.

That's a wide range - 5 seconds, 25 or 55? And is that tied to the systemd update?
(But the default systemd timeout is 90 seconds, so you're not seeing the OPs issue when it's significantly less)

phcerdan · 2022-05-26 15:45:48

It's incredibly annoying to receive the message in 10+ terminals opened in tmux. The message stay there when I return from suspend, until I clear the console.
So, yes, I understand this is not a bug, but if anyone finds the way to pass `--no-wall` when suspending from Gnome, I will greatly appreciate it.

anasm · 2022-06-08 17:28:23

Donwngrade your systemd to 250.2-1 and downgrade your kernel to older version...
Now there is no broadcast message while shutdown and entropy pool is back to normal.
you can use downgrade tool

V1del · 2022-06-08 19:18:56

pretty sure the broadcast message got cleaned up in 251.2 and the entropy pool situation is normal and expected due to heavy reworks in the 5.18 kernels. Please don't promote bad practices to fix minor short term inconveniences.

qarkai · 2022-06-08 20:33:21

V1del wrote:

pretty sure the broadcast message got cleaned up in 251.2

For the record, I still have those messages on shutdown and probably reboot (didn't try yet). IIUC systemd fixed broadcast messages for hibernate and suspend.
Of course downgrade is not a solution, I agree with that.

marekkloc1 · 2022-09-26 19:49:39

From what I see in the very first post, I guess I'm right here because I have that problem too. I have the same problem, but I don't know how else to fix it I know I should use the journalctl command but I don't know how to export it out as a file like a text document.

But I'll start from the beginning. I already switched to Arch linux in June, and first I used Archcraft to test my unstable computer which is also Arch linux only the name. It worked fine, archcraft was based on openbox and titlebox, only openbox suited me but then I found it too weak. So I decided to switch to the classic Arch itself. And so I did. But after 3 days I had a problem with the computer that it didn't want to shut down at all as it is in the picture someone posted here, I usually solved it by turning it off with the power button, but that is absolutely out of the question because if the computer doesn't want to shut down by itself then somewhere there is a defect in the Linux Arch itself. Someone told me that it is KDE plasma that does it, and someone said Kwim, but I don't know what the truth is.

Does anyone have any idea how this could be fixed without me having to change other computers because of it? Moreover, this problem only does this to Arch KDE and not Archcraft, there it worked almost immediately on shutdown without waiting for anything, only Arch KDE the one takes it like 10 seconds and moreover it keeps getting delayed just to shut down two HDDs. Only when I go to sleep sometimes it doesn't show up and I have to deal with shutting it down via the power button.

In addition, I would share my experience and the problems I have but I do not know if I can share here a link to youtube where I filmed the problem.

seth · 2022-09-27 06:34:06

the picture someone posted here … Someone told me that it is KDE plasma that does it, and someone said Kwim

Could you please try to be more vague?
…

"KWin", specifically kwin_x11 but whether it's the actual trigger isn't clear; but the issue discussed here and the linked threads is plasma related and since the screenshot in the OP is generic and meaningless itr. a reliable way to figure whether you're in the same situation is to log out of KDE and then shutdown from the DM (sddm, I guess)

Also

this problem only does this to Arch KDE and not Archcraft

archcraft was based on openbox

is a strong indicator and

there is a defect in the Linux Arch itself

No

Does anyone have any idea how this could be fixed without me having to change other computers because of it?

Yes: don't use KDE.

marekkloc1 · 2022-09-28 20:03:19

I really want to post this error from journal log but i don't know the exact command for journal log to pastebin, i know only command for journalctl. Also i want to post this error not from previous or this current boot, but from exact date, day and time.

seth · 2022-09-28 20:12:13

https://wiki.archlinux.org/title/System … ing_output and you can use the tip in teh 1st link below to feed it into a pastebin service.
You can also try https://aur.archlinux.org/packages/sddm-git where the problem has reportedly been fixed (but idk that 1st hand)

Arch Linux

#1 2022-05-23 14:42:06

System hangs on shutdown with a message

#2 2022-05-23 14:52:02

Re: System hangs on shutdown with a message

#3 2022-05-23 15:24:38

Re: System hangs on shutdown with a message

#4 2022-05-23 18:33:49

Re: System hangs on shutdown with a message

#5 2022-05-24 13:24:57

Re: System hangs on shutdown with a message

#6 2022-05-24 13:35:04

Re: System hangs on shutdown with a message

#7 2022-05-24 18:12:33

Re: System hangs on shutdown with a message

#8 2022-05-25 08:49:20

Re: System hangs on shutdown with a message

#9 2022-05-25 14:12:08

Re: System hangs on shutdown with a message

#10 2022-05-25 18:06:10

Re: System hangs on shutdown with a message

#11 2022-05-25 18:25:40

Re: System hangs on shutdown with a message

#12 2022-05-25 19:23:23

Re: System hangs on shutdown with a message

#13 2022-05-25 19:42:36

Re: System hangs on shutdown with a message

#14 2022-05-25 20:45:20

Re: System hangs on shutdown with a message

#15 2022-05-25 21:15:13

Re: System hangs on shutdown with a message

#16 2022-05-26 15:45:48

Re: System hangs on shutdown with a message

#17 2022-06-08 17:28:23

Re: System hangs on shutdown with a message

#18 2022-06-08 19:18:56

Re: System hangs on shutdown with a message

#19 2022-06-08 20:33:21

Re: System hangs on shutdown with a message

#20 2022-09-26 19:49:39

Re: System hangs on shutdown with a message

#21 2022-09-27 06:34:06

Re: System hangs on shutdown with a message

#22 2022-09-28 20:03:19

Re: System hangs on shutdown with a message

#23 2022-09-28 20:12:13

Re: System hangs on shutdown with a message

Board footer