Repository navigation
Merge upstream quattro (T3 Code AppImage, Snapdragon cameras, platform fingerprint readers) - #88
Merged
Merged
Conversation
* Install T3 Code as its self-updating AppImage T3 Code came from the t3code-bin package, which T3 Code's own updater cannot touch: on Linux it only updates an AppImage or a .deb. The app still offered an update that then failed, and Nightly needed a second package. The installer now asks for Stable or Nightly and installs the official AppImage under ~/.local/share/t3code, verified against the sha512 in the feed the app's updater reads. The file name carries no version, so the updater replaces it in place and the launcher stays valid. fuse3 provides the setuid fusermount the AppImage runtime mounts through. The launcher entry and icons come from upstream's entry inside the AppImage, which carries the t3code:// handlers, and ~/.local/bin/t3 links to the launcher the app writes on start. The palette is still selected before the first launch, through the CLI bundled in the mounted AppImage, the same way the package's /usr/bin/t3 ran it. A migration replaces t3code-bin with Stable and t3code-nightly-bin with Nightly for a user who has run T3 Code, keeping ~/.t3, and drops the package only once the app is in place. Removal also takes the app, both launcher entries, the icons, the updater cache and the t3 link. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Finish T3 Code's setup before its AppImage counts as installed The migration and the Install menu treat an installed AppImage as a finished install. It used to be moved into place before the launcher, icons and `t3` link were written, so a setup that stopped in between left a retry dropping the package without a launcher. The verified download now provides the launcher entry and icons, and moves into place last. The launcher's Exec doubles a literal % in the AppImage path, since launchers expand %-field codes there. An install interrupted while T3 Code's CLI runs from the mounted AppImage now unmounts it on the way out: the mounter is a background job, which ignores Ctrl-C. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Snapdragon cameras run through libcamera, which apps reach through PipeWire. Install pipewire-libcamera for the whole Qualcomm family and turn on Chromium's WebRtcPipeWireCamera, which Chromium leaves off. The feature editing moves out of omarchy-install-video-decode into omarchy-chromium-add-feature, which both helpers use.
* Find fingerprint readers a platform names omarchy-hw-fingerprint only scanned USB, so a reader the kernel drives another way, such as a Mac's Touch ID behind its Secure Enclave, was never found: no first-run invitation, and the setup stopped at "No fingerprint sensor detected". A platform package now names such readers in /usr/share/omarchy-platform/fingerprint-readers, each as a file and the value it reads once the reader is usable. Ported from omacom/omarchy-mac 916a912, detection only. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * Say how fingerprint-readers matches, and keep USB readers found beside it The docs now say the comparison drops trailing newlines, a space splits a line's fields and the file is read as the session user. A platform file that matches nothing must never hide a USB reader, so the test pairs one with a real USB reader both ways. lifecycle-dispatch.md lists the file with the others. Ported from omacom/omarchy-mac d94c8d7. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * Test Touch ID's other values and note the reader file's kernel names diag/touchid also reads not-ready, unknown and failed, and not-ready contains ready, so the test now rejects each one and finds a USB reader beside a not-ready Touch ID. file-layout.md says the value is the whole file, that the file is 0444 root:root, and that the line follows the kernel's apple_sep and diag/touchid names, so a rename stops detection without an error. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upstream
quattromoved from60f5b496(already on the fork via #87) to81fd2d23(2026-10-19 02:13 UTC). 3 upstream commits, applied on top of forkquattro. Cursor stays on the official tarball, not a mise tool. Face, Grok Bot, and Cursor menu entries stay. The power-profile menu provider stays out.T3 Code installs as its own AppImage (omacom#15907)
T3 Code no longer comes from
t3code-bin. That package cannot be updated by T3 Code's own updater, which on Linux only replaces an AppImage or a.deb, so the in-app update failed and Nightly needed a second package.Install asks for Stable or Nightly and puts the official AppImage in
~/.local/share/t3code, checked against the sha512 in the feed the updater reads. The file name has no version, so an update replaces it in place and the launcher stays valid.fuse3supplies the setuidfusermountthe AppImage runtime mounts through. The launcher entry and icons come from the entry inside the AppImage, including thet3code://handlers, and~/.local/bin/t3links to the launcher the app writes on start. The palette is still chosen before the first launch, through the CLI inside the mounted AppImage.The verified download writes the launcher and icons first and moves the AppImage into place last, so a setup that stops halfway is not treated as installed. A
%in the AppImage path is doubled in the launcherExecline. An install interrupted while the CLI is running unmounts the AppImage on the way out.Migration
1792345511replacest3code-binwith Stable andt3code-nightly-binwith Nightly for a user who has already run T3 Code, keeps~/.t3, and drops the package only once the app is in place. A user who never ran it keeps the package. Removal takes the app, both launcher entries, the icons, the updater cache, and thet3link, and leaves at3the user put there themselves.Chromium can use Snapdragon cameras (omacom#15895)
Snapdragon cameras go through libcamera, which apps reach through PipeWire.
pipewire-libcamerais now installed for the whole Qualcomm family, and Chromium'sWebRtcPipeWireCamerais turned on (Chromium leaves it off). Feature editing moved out ofomarchy-install-video-decodeintoomarchy-chromium-add-feature, which both helpers use. Migration1792359308does this for an existing Snapdragon install and asks for a logout so the PipeWire camera backend loads. Other machines are unchanged.A platform can name a fingerprint reader (omacom#14675)
omarchy-hw-fingerprintonly scanned USB, so a reader the kernel drives another way (a Mac's Touch ID, behind its Secure Enclave) was never found: no first-run invitation, and setup stopped at "No fingerprint sensor detected". A platform package can now name such readers in/usr/share/omarchy-platform/fingerprint-readers. Each line is a file (a shell glob) and the value that file reads once the reader is usable. Comparison drops trailing newlines, a space splits the fields, and the file is read as the session user. A platform file that matches nothing, or that reads not-ready, unknown, or failed, still leaves a USB reader detectable. Detection only; ported from the omarchy-mac packages.