8f42fc953d
This is a projection, not a development branch. The tree above was constructed from the internal source named below under a manifest that decides which paths may leave, then scanned as a whole tree rather than as a series of patches, and only then published. Public history starts here because the history before it was not admissible, and neither was the tree. What used to stand in this repository included a rescue copy of another machine, a directory of phone handoffs, deployment wired to one house, and a submodule pointing at a forge no stranger can reach. None of that was ever the product. It stays in the private forge, which is allowed to hold the whole working organism, and this is what was deliberately sent out instead. Three mechanisms produced this tree, in decreasing order of trust. A top-level path the manifest does not name never arrives at all, which is the one that catches directories nobody has thought of yet. Named internal files inside admitted roots are dropped. A short, reviewed table replaces deployment defaults that a public build must not carry -- an endpoint aimed at one LAN, a VPN profile belonging to one phone, packaging built from one checkout path. Everything after this commit is an ordinary publication with the same three trailers, so a force push stops being routine and starts meaning that something deliberate happened. The trailers bind the projection to its source without pretending the public SHA is the private one: same lineage, different tree, and the record says so. Source-Sha: 8f27b1e76a8fef560a336aba18e6990713ff1047 Policy-Sha: 6b261d2f3e6e1fb19874846ba4bb1dfe15565d25b8618c1c1afba0419c101d27 Tree-Digest: 18ec3563c5e5ef9a414993a9f6734b251ff9ed3cd56eebdd6cac01e45c6e3067
53 lines
1.9 KiB
QML
53 lines
1.9 KiB
QML
import qs
|
|
import qs.services
|
|
import qs.modules.common
|
|
import qs.modules.common.widgets
|
|
import qs.modules.common.functions
|
|
import QtQuick
|
|
import Quickshell
|
|
import Quickshell.Wayland
|
|
|
|
// Souveraine: on a phone deploy, surface the on-screen keyboard when a polkit
|
|
// prompt appears. The polkit window is a wlr-layer-shell Overlay and the OSK
|
|
// is a separate layer-shell surface (squeekboard), so the OSK won't auto-rise
|
|
// to it. Since both run under this shell, we drive the OSK explicitly.
|
|
// Laptop deploys (souveraine.phone == false) are unchanged — hardware
|
|
// keyboard handles it.
|
|
//
|
|
// This was a poke — `oskOpen = PolkitService.active` on the transition — and
|
|
// a poke is not enough for two reasons, both of which left a password field
|
|
// on screen with no way to type into it:
|
|
//
|
|
// 1. squeekboard hides itself when input-method focus drops, which this
|
|
// layer-shell surface does not reliably hold. The keyboard appeared and
|
|
// then left while the prompt was still waiting.
|
|
// 2. The transition is all a poke sees. pkexec run before Config.ready —
|
|
// an update on login, a boot-time authorization — has its prompt up
|
|
// before this file is even loaded, so no transition ever arrives.
|
|
//
|
|
// A hold fixes both: the keyboard is re-asserted for as long as the prompt
|
|
// is up (GlobalStates.oskHold), and onCompleted takes the hold for a prompt
|
|
// that was already waiting.
|
|
FullscreenPolkitWindow {
|
|
id: root
|
|
contentComponent: Component {
|
|
PolkitContent {}
|
|
}
|
|
|
|
readonly property bool phone: Config.options?.souveraine?.phone ?? false
|
|
|
|
function syncKeyboard() {
|
|
if (!root.phone) return;
|
|
if (PolkitService.active) GlobalStates.oskHold("polkit");
|
|
else GlobalStates.oskRelease("polkit");
|
|
}
|
|
|
|
Component.onCompleted: root.syncKeyboard()
|
|
|
|
Connections {
|
|
target: PolkitService
|
|
function onActiveChanged() {
|
|
root.syncKeyboard();
|
|
}
|
|
}
|
|
}
|