ekklesiaandClaude Opus 5
926668dc9b
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]>
49 lines
1.6 KiB
Plaintext
49 lines
1.6 KiB
Plaintext
# The classroom never sleeps, never dims, and never locks.
|
|
#
|
|
# Two failures on real hardware are behind this file. The power button put
|
|
# a room to sleep; and a machine left alone came back to a password prompt
|
|
# on an account that is meant to have no password, which strands the
|
|
# television until somebody arrives with SSH.
|
|
#
|
|
# PowerDevil decides all of it. It also takes logind's handle-power-key
|
|
# inhibitor while a session is running, so the logind drop-in on its own
|
|
# would be overruled by whatever this says.
|
|
#
|
|
# Every profile is marked immutable at the profile level, not just on the
|
|
# subgroups. PowerDevil loads an idle action only when the profile has a
|
|
# group for it, so what matters here is as much what is absent — no
|
|
# DimDisplay, no DPMSControl, no SuspendSession — as what is present, and
|
|
# a writable profile is one a leftover user file can add those back to.
|
|
# classroom-desktop-reset removes the user's copy at every login for the
|
|
# same reason.
|
|
#
|
|
# Every profile gets the same answer. A classroom machine has no battery,
|
|
# but a profile that exists and disagrees is worse than one that does not
|
|
# exist at all.
|
|
#
|
|
# 0 is no action.
|
|
|
|
[AC][$i]
|
|
icon=battery-charging
|
|
|
|
[AC][HandleButtonEvents][$i]
|
|
powerButtonAction=0
|
|
lidAction=0
|
|
triggerLidActionWhenExternalMonitorPresent=false
|
|
|
|
[Battery][$i]
|
|
icon=battery-060
|
|
|
|
[Battery][HandleButtonEvents][$i]
|
|
powerButtonAction=0
|
|
lidAction=0
|
|
triggerLidActionWhenExternalMonitorPresent=false
|
|
|
|
[LowBattery][$i]
|
|
icon=battery-low
|
|
|
|
[LowBattery][HandleButtonEvents][$i]
|
|
powerButtonAction=0
|
|
lidAction=0
|
|
triggerLidActionWhenExternalMonitorPresent=false
|