aboutsummaryrefslogtreecommitdiff
path: root/dotfiles/common/.config/calibre/conversion
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-28 21:37:55 -0500
committerCraig Jennings <c@cjennings.net>2026-07-28 21:37:55 -0500
commit2d9dcc942fc16b8e5bcbe0a6eced5a71f639ae29 (patch)
tree1ec391b1d950bd0be6f922b5b02aa92c9694b727 /dotfiles/common/.config/calibre/conversion
parent8342b74a696addf631bad5d811cfdac8ca722035 (diff)
downloadarchsetup-2d9dcc942fc16b8e5bcbe0a6eced5a71f639ae29.tar.gz
archsetup-2d9dcc942fc16b8e5bcbe0a6eced5a71f639ae29.zip
docs(todo): close the reboot and caffeine fixes, file four findings
The 2026-07-28 reboot cut the session short before two finished tasks could be closed. amdgpu.runpm=0 is confirmed live in /proc/cmdline, and the caffeine readability work shipped, so both close now. Four new entries. Desktop settings didn't survive a session restart. Timer presets should start in one click. hyprlock still exits mid-lock, and its watchdog relaunch left no durable trace. The wireguard gpg convention is inert: the importer globs *.conf only and carries no gpg call, so the stated promise that it decrypts at import is false. That last one is why the newly encrypted wolf config stays untracked for now. The hyprlock grading first read "some users sometimes", which the matrix maps to P3 rather than the [#B] written beside it. The frequency row was the wrong input. On a one-user machine, twice in three days is frequent, so I corrected the input rather than the letter. Also corrected an earlier claim that night light "has likely never worked" from the config. It launches fine by hand and survives. It loses a race against compositor readiness at session start, and nothing relaunches it.
Diffstat (limited to 'dotfiles/common/.config/calibre/conversion')
0 files changed, 0 insertions, 0 deletions