Files
Classroom_Desktop/config/systemd/logind-ekklesia-classroom.conf
T
ekklesiaandClaude Opus 5 926668dc9b fix: make an existing classroom converge into the Plasma appliance
A real room upgraded to 0.1.45 and came up as stock Debian Plasma with
the old Waybar across the top, mako still catching notifications, and a
lock screen on an account that has no password.

The cause was one line, and it was in the lab: the harness handed the
session under test XDG_CONFIG_DIRS by hand, so every result it had ever
produced was a result about a machine somebody had already configured.
On a machine SDDM starts the session through PAM, PAM does not read
/etc/environment.d, and Debian's own plasma-workspace env.sh then set the
variable from scratch — so the classroom's settings directory was not in
the cascade at all. No layout, no lock policy, no Kiosk restrictions.

The settings now arrive the way Plasma delivers them, through a file in
/etc/xdg/plasma-workspace/env. Around that: the look and feel is
immutable on its own key so a stale profile cannot answer for it; the
palette is composed into the package, because naming a colour scheme does
not produce one and the dark bar had been coming from a technician's
hand; the desktop reset converges another desktop's appearance state and
keeps the room's own; and classroom-migrate stops, deactivates and masks
the old shell, including the D-Bus activation that brought mako back
while the panel was down — found only by killing the panel on a migrated
machine.

device.conf loses COMPOSITOR and comes off the hyprland channel, which
would otherwise have handed the room the experiment back.

The lab stops flattering the package: it restarts the machine, lets SDDM
actually autologin, and asks a fresh install and a machine upgraded from
the Hyprland package the same sixty questions. Both answer identically,
twice, and the panel still comes back from eight SIGKILLs.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-10 23:06:56 -05:00

41 lines
1.7 KiB
Plaintext

# The classroom's power button does nothing.
#
# A teacher reaching behind a television for a cable, a child leaning on
# the tower, a volunteer tidying the room: none of those should be able to
# take the computer down in the middle of a Sunday morning. Recovering a
# room that has been switched off needs somebody who knows where the
# button is, which is exactly the person who is not there.
#
# This is one of two layers, and both are needed. While a graphical
# session is running, PowerDevil takes logind's handle-power-key
# inhibitor and acts on the button itself, so logind alone would be
# ignored — see the classroom's powermanagementprofilesrc for the other
# half. This layer is what covers the machine before the session starts,
# after it ends, and if PowerDevil is not running at all.
#
# Holding the button for several seconds still cuts the power. That is
# the firmware doing it, below any operating system, and it is left alone
# on purpose: it is the only recovery a person standing at a wedged
# machine has.
[Login]
HandlePowerKey=ignore
HandlePowerKeyLongPress=ignore
HandleSuspendKey=ignore
HandleSuspendKeyLongPress=ignore
HandleHibernateKey=ignore
HandleHibernateKeyLongPress=ignore
HandleRebootKey=ignore
HandleRebootKeyLongPress=ignore
# Classroom machines are desktops, but a laptop pressed into service in a
# room should not sleep when its lid is closed either.
HandleLidSwitch=ignore
HandleLidSwitchExternalPower=ignore
HandleLidSwitchDocked=ignore
# logind's own idle timer, which is separate from PowerDevil's and runs
# whether or not a session is up. ignore is the default, and a classroom
# is not a machine to leave a default of this importance implicit on.
IdleAction=ignore
IdleActionSec=0