sync: auto-sync from GURU-KALI at 2026-05-24 17:55:58
Author: Mike Swanson Machine: GURU-KALI Timestamp: 2026-05-24 17:55:58
This commit is contained in:
@@ -135,3 +135,88 @@ Noted for future rechecks in the coord messenger (to=mike, project=gururmm, msg
|
||||
a254202a-aa33-4736-ba9c-cd5678dbef58): recheck their versions; if still behind latest,
|
||||
force-update via POST /api/agents/{id}/update; durable fix = investigate the client-site
|
||||
firewall/NAT resetting the long-lived WebSocket. All watchers finished; none running.
|
||||
|
||||
---
|
||||
|
||||
## Update: 17:55 MST — Xfce lock-screen disabled + machine-doc note + community how-to published
|
||||
|
||||
### Session Summary
|
||||
|
||||
Disabled the lock screen on idle/screen-timeout on GURU-KALI (Kali/Xfce) per user request,
|
||||
documented it in the machine doc, and published the fix as a how-to on the community site.
|
||||
|
||||
The lock came from `xfce4-screensaver` (the only locker installed — no light-locker /
|
||||
xscreensaver / gnome-screensaver; `xfce4-power-manager` already had
|
||||
`lock-screen-suspend-hibernate=false`). The catch: the screensaver's lock keys were NOT
|
||||
present in xfconf, so the daemon used its compiled default of lock = on. Fixed by creating
|
||||
them set to false (`-n` creates a missing property). Change is live (the running daemon,
|
||||
PID 2566, watches xfconf) and persisted to the per-user XML, surviving reboot. Screen blanking
|
||||
was left intact — only the password prompt is gone.
|
||||
|
||||
Recorded the change in `.claude/machines/guru-kali.md` Notes (flagged "INTENTIONALLY DISABLED —
|
||||
do NOT re-enable" with the exact keys) so a future session does not undo it; committed/pushed
|
||||
(e5c31f8). Then turned it into a public how-to via the `/forum-post` skill — drafted from this
|
||||
session, previewed, and on confirmation inserted into Flarum on IX via paramiko → PHP/PDO.
|
||||
Live as discussion #12.
|
||||
|
||||
### Key Decisions
|
||||
|
||||
- **Disabled the lock only, not screen blanking** — user asked only about the lock prompt; the
|
||||
saver/DPMS still blank the screen on idle.
|
||||
- **Created the xfconf keys with `-n`** rather than expecting them to exist — they default to
|
||||
lock-on when absent, which is why GUI toggles appeared to do nothing.
|
||||
- **Flagged the change "do NOT re-enable" in the machine doc** — it is an intentional deviation a
|
||||
future session/agent might otherwise "fix."
|
||||
- **Published via the forum-post DB-insert path** (paramiko → PHP/PDO on IX), per the skill —
|
||||
external HTTP is Cloudflare-blocked and localhost curl has a redirect issue.
|
||||
|
||||
### Configuration Changes (this update)
|
||||
|
||||
Machine-local (GURU-KALI, not in repo):
|
||||
- `xfce4-screensaver` xfconf: `/lock/enabled=false`, `/lock/saver-activation/enabled=false`,
|
||||
`/lock/sleep-activation=false`. Persisted in
|
||||
`~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-screensaver.xml`.
|
||||
- `xfce4-power-manager`: `lock-screen-suspend-hibernate=false` (confirmed, already set).
|
||||
|
||||
ClaudeTools (committed e5c31f8):
|
||||
- `.claude/machines/guru-kali.md` — Notes entry: lock-on-timeout intentionally disabled, with keys + do-not-re-enable.
|
||||
|
||||
Community site:
|
||||
- Flarum discussion #12 / post #11 inserted (tag 7, How-Tos & Tips).
|
||||
|
||||
### Credentials & Secrets (this update)
|
||||
|
||||
- No new secrets. Used vaulted creds only: IX SSH password `infrastructure/ix-server.sops.yaml`
|
||||
-> `credentials.password`; Flarum DB password is embedded in the forum-post skill
|
||||
(`Fl@rum2026!CGS`, db azcompu_flarum). The local publish script (which embedded the DB
|
||||
password) was deleted from /tmp after posting.
|
||||
|
||||
### Infrastructure & Servers (this update)
|
||||
|
||||
- **IX** `172.16.3.10` (root) — hosts the Flarum community forum (`community.azcomputerguru.com`),
|
||||
MySQL db `azcompu_flarum` (user `azcompu_flarum`), admin user_id 1 (MikeSwanson). Posts inserted
|
||||
via paramiko SSH + PHP/PDO (s9e TextFormatter XML), tags table; default tag 7 = How-Tos & Tips.
|
||||
|
||||
### Commands & Outputs (this update)
|
||||
|
||||
```bash
|
||||
# disable the lock (created the keys; they were absent -> defaulted to on)
|
||||
DISPLAY=:0.0 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus \
|
||||
xfconf-query -c xfce4-screensaver -p /lock/enabled -n -t bool -s false
|
||||
# (+ /lock/saver-activation/enabled, /lock/sleep-activation = false)
|
||||
xfconf-query -c xfce4-screensaver -p /lock/enabled # -> false (daemon picked it up live)
|
||||
|
||||
# publish: /forum-post skill -> rc=0
|
||||
# Discussion ID: 12 / Post ID: 11
|
||||
```
|
||||
|
||||
### Pending / Incomplete Tasks (this update)
|
||||
|
||||
- None for this segment. (Carried over: laggards BB-SERVER + RECEPTIONIST-PC on 0.6.37 noted in
|
||||
coord msg a254202a; GuruRMM issues #15-19 open.)
|
||||
|
||||
### Reference Information (this update)
|
||||
|
||||
- Forum post: https://community.azcomputerguru.com/d/12-disable-the-xfce-screen-lock-on-idle-timeout-without-losing-the-screensaver (discussion 12, post 11, tag 7)
|
||||
- ClaudeTools commit: e5c31f8 (machine-doc note)
|
||||
- xfconf XML: `~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-screensaver.xml`
|
||||
|
||||
Reference in New Issue
Block a user