Re: "The system is going down for suspend NOW!" broadcast messages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On my system (Fedora Rawhide with KDE) I suspend either by holding the power button for a short time where it asks me what action I want to take, or directly from the "start" menu.

On 27. 4. 2022 10:29, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Apr 27, 2022 at 09:36:47AM +0200, Petr Pisar wrote:
V Mon, Apr 25, 2022 at 11:45:44AM -0400, Simo Sorce napsal(a):
On Mon, 2022-04-25 at 16:28 +0200, Petr Pisar wrote:
V Mon, Apr 25, 2022 at 12:54:10PM +0200, Sandro Mani napsal(a):
Since some recent update (can't pinpoint which exactly), everytime the
system suspends, it sends a "The system is going down for suspend NOW!"
broadcast message to all terminals. Any idea anyone how to switch this off?
(Running up-to-date rawhide).
How is the suspend triggered (i.e. by some explicit command, or key press, or
a desktop environment timer…)? Also please describe your enviroment, so it's
easier to reproduce.

What's wrong with the message? Do you not want to notify all the users of your
system that it will be powered down?
On a workstation?
No, you already know you are suspending and there is no need to spam
terminals, you want them to stay as they are so when yo un-suspend the
output is not "corrupted".

On a single-user system no. Ideally the emmitter of the warning should count
users of an interactive sessions.

This message is emitted by shutdown tool. That tool has --no-wall option to
disable the message. You need to find out what executes that command and then
patch it. It could be e.g. systemd/logind.
This message is emitted by logind.

Is this an upstream change?

I have no idea. I do not use suspend. I only know that a similar message is
reported for reboot and poweroff. On Fedora /usr/sbin/shutdown is provided by
systemd. I was unable to find any relevant notice in systemd's NEWS.
I don't think we should emit messages for suspend. This is probably an unintended
effect of recent changes, https://github.com/systemd/systemd/commit/cdf370626f
seems like the most likely culprit.

For some reason, I can't reproduce the issue
(tried 'systemctl suspend' and 'systemctl suspend --message …' and
'sudo busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager Suspend b 0').

Zbyszek
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

--
Marián Konček
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux