| Summary: | Suppress systemd wall messages at reboot/poweroff | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | cogebok177 |
| Component: | Session Management | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | kde, kde, nate, smowtenshi |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | 6.0.1 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
cogebok177
2024-03-11 16:13:32 UTC
Hm, maybe. Currently we intentionally show these messages. The question is, can we distinguish between automatic ones vs ones deliberately set by an administrator? I'm personally of the opinion that an administrator is very unlikely to use the GUI power controls in plasma to begin with. Best-case scenario, a conscientious admin will call qdbus org.kde.shutdown in a wrapper script that prints its own wall message anyways. What's much more likely is an admin calling poweroff directly or in a script also printing its own wall message, unaffected by any KDE changes. In either case, the systemd message would still be of little use as systemd - unlike sysv - provides no way to schedule the shutdown built into the command, instead relying on systemd timers or a script. The wall message will always appear too late to be useful in warning a user of an impending shutdown, although this is more a systemd problem. Yeah, you might be right. > The question is, can we distinguish between automatic ones vs ones deliberately set by an administrator?
Unfortunately we cannot
We can apparently turn those off:
> The WallMessage and EnableWallMessages properties reflect the shutdown reason and wall message enablement switch which can be set with the SetWallMessage() method described above.
|