Description of problem:
After upgrading to Fedora 37 (systemd 251), but laptop started producing an extremely loud and annoying beep when rebooting or shutting down. It's a PC Speaker sound, and as such, it ignores any configuration of the regular speakers, including volume level, mute status, and even headphones plugged in! On my laptop, it's extremely loud and unpleasant, and if it happens during night when my family is sleeping, I'm beginning to see red.
On desktop  and test  lists, I got confirmation from other people that they experience it too.
There are more complaints on the internet:
which seem to point to this issue as a root cause or related to it:
I have to confirm that together with that beep, I also started to see messages like "System is going down NOW" in a VT which briefly flash on the screen during reboot (sometimes too fast to notice). So it seems plausible that these messages cause the beep to occur. (These messages also seem to sometimes break plymouth, the graphical screen during reboot, but that's not the point of this bug report).
It is interesting that the beep is emitted only sometimes. I haven't found a pattern yet. It seems like a race condition of sort. Other people claimed it happens always for them.
Please, abusing the PC speaker needs to stop, at least on graphical desktops! There is zero benefit in flashing the message on the screen for a fraction of a second, and the beep will make users extremely angry. If I were in the same room as my family sleeping when the beep occurred, and were I just a regular user, this would probably be the last day of Linux on my laptop. The beep is that loud and uncomfortable, especially at night.
Version-Release number of selected component (if applicable):
Thinkpad P1 gen3
randomly, in my case (but others claim it beeps every time)
Steps to Reproduce:
1. ask the system to reboot or power off
2. hear a loud PC speaker beep (in my case, sometimes, possibly a race condition)
PC Speaker shouldn't be used on end-user graphical desktops. I have no idea about servers.
I don't expect people to want to block Fedora 37 on this problem, but I'll at least propose it for a freeze exception, in case the freeze starts before this is resolved. I also nominate this as a Prioritized Bug, because I think many of our users will be extremely annoyed if we release in this state.
The solution likely includes a revert in systemd to no longer send the VT announce messages, or possibly blacklisting the pcspkr kernel module (at least on desktops), as an alternative.
Funny thing is, I seem to remember this always used to happen *before* systemd. So it might be that this is sort of restoring an old behaviour rather than a new one. I agree it's kinda annoying and probably silly, though. For desktops at least.
+4 in https://pagure.io/fedora-qa/blocker-review/issue/921 , marking accepted.
Hmm, so the patches from https://github.com/systemd/systemd/issues/23520 are already included in v251.2,
and Kamil reported the issue with systemd-251.4-53.fc37.x86_64. So the that fix is clearly not enough.
In https://github.com/systemd/systemd/issues/23520#issuecomment-1141290377 the following was recommended:
busctl set-property org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager EnableWallMessages b false
Can somebody who can reproduce the issue test if this fixes it? If yes, then most likely we need
to disable those messages altogether by default.
I finally found the reproducer! The beep doesn't occur when I cleanly boot my system and restart it. But when I SUSPEND AND RESUME it, it then beeps during reboot/poweroff! So whatever fix was applied earlier, it doesn't persist through suspend&resume.
> busctl set-property org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager EnableWallMessages b false
This indeed silences the beep, and it persists through suspend&resume.
In today's Prioritized Bugs meeting, we accepted this as a Prioritized Bug.
@zbyszek.pl Can we please get a patch in F37 quickly, now that it's fixed in upstream? It would be great to have this fixed in F37 Final. Thanks!
FEDORA-2022-bb55f82158 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-bb55f82158
(In reply to Fedora Update System from comment #8)
> FEDORA-2022-bb55f82158 has been submitted as an update to Fedora 37.
Beeping is gone! :-)
Beep! I mean thanks for checking.
So… the update has been "pending→stable" for the last three days. Do I need to do something to push it out?
FEDORA-2022-bb55f82158 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #11)
> So… the update has been "pending→stable" for the last three days. Do I need
> to do something to push it out?
To explain: This was because we're in a Final freeze, and during freeze, QA takes care of pushing things stable if they have an approved freeze exception. We wait a while to confirm that it's working well and also consider the risk of breaking something important. So everything was working as intended.