Skip to content

Hold fingerprint checks on the lock screen until resume - #9919

Open
wulujia wants to merge 6 commits into
omacom:quattrofrom
wulujia:fix/lock-fingerprint-suspend
Open

wulujia wants to merge 6 commits into
omacom:quattrofrom
wulujia:fix/lock-fingerprint-suspend

Conversation

@wulujia

@wulujia wulujia commented Sep 3, 2026 •

Copy link
Copy Markdown

Problem

On a ThinkPad X1 Carbon (Synaptics reader 06cb:019f), closing the lid and reopening it later often leaves the lock screen with no fingerprint option. Only the password works until the next lock.

The journal shows what happens:

07:50:53.163 systemd-logind: Lid closed.
07:50:53.263 omarchy-shell: omarchy lock ... lock-requested
07:50:53.840 omarchy-shell: Starting pam session ... "omarchy-lock-fingerprint"
07:50:53.933 kernel: PM: suspend entry (s2idle)
07:50:57.832 fprintd: Ignoring device due to initialization error: unsupported firmware version
  1. The lid-close lock starts a fingerprint check right away. fprintd-list and pam_fprintd both D-Bus-activate fprintd, which resets the reader.
  2. The machine suspends about 100 ms later, in the middle of that reset. fprintd cannot delay the sleep: it is starting inside the transition, so its own inhibitor fails with OperationInProgress.
  3. After resume the reader answers "unsupported firmware version". That fprintd instance ignores it for the rest of its life.
  4. The lock plugin checks fingerprint availability once, at lock time. That check ran against the broken fprintd, saw no reader, and put the lock in password-only mode. It never re-checks, so the state survives until the next lock.

A scan that is already running when the machine sleeps is a different case, and it already works. fprintd suspends and resumes the reader itself, and while a scan is running libfprint turns off USB persist for the reader, so the kernel re-enumerates it after a long sleep. The old device object reports device was disconnected, the PAM verify fails, and the retry timer starts a fresh scan on the new device. Two long sleeps on the same laptop yesterday both unlocked by fingerprint within two seconds of resume through that path.

Fix

The lock plugin now follows logind's PrepareForSleep itself, through a dbus-monitor process that lives as long as the shell. omarchy-system-sleep-monitor cannot deliver the resume half: it exits to release its delay inhibitor and is restarted after the machine is already awake.

  • PrepareForSleep(true): stop the retry timer and refuse to start a scan or an availability check until resume. A scan already in flight is left alone.
  • PrepareForSleep(false): run the availability check if one was held back, otherwise restart the scan. A check that failed before sleep no longer decides the whole lock.
  • If the monitor process dies, the lock clears the suspending state and restarts the monitor after 5 s, so it can never get stuck in password-only mode.

omarchy-shell lock status reports the new suspending flag.

An earlier revision of this branch also aborted the in-flight PAM at suspend. That made things worse after a long sleep. Killing the PAM helper makes fprintd cancel the verify and close the reader synchronously, in the same instant it is suspending the reader for logind. The close blocked until resume, the reader had kept persist=1 because no scan was running at suspend time, and it woke with stale firmware state:

10:18:19 fprintd[4108]: Corrupted message received
10:18:19 fprintd[4108]: Error closing device after disconnect: The driver encountered a protocol error with the device.
10:19:18 systemd[1]: fprintd.service: Deactivated successfully.

Every scan failed until that daemon hit its idle timeout a minute later. The current revision leaves the scan running, so libfprint's own suspend path handles the reader.

Testing

  • test/shell.d/lock-fingerprint-suspend-test.sh (new) pins the monitor, the two gates, the held-back check, and that suspend does not abort a running scan.
  • ./test/all passes apart from bar icons share slot and baseline geometry, which fails the same way on a clean quattro checkout on this machine. runtime-smoke-test.sh timed out once under the full run and passed four times on its own, before and after the change.
  • Verified the dbus-monitor process starts, streams lines through SplitParser, and is reaped under a Quickshell Process.
  • On the linked checkout, the earlier revision passed a 7 s lid close and failed a 27 min one, which is what led to the change above. The current revision unlocks by fingerprint after a long lid close on the same laptop.

A lid-close lock starts its fingerprint check a few hundred milliseconds
before the machine suspends. fprintd-list and pam_fprintd both D-Bus-activate
fprintd, which resets the reader as the USB bus goes down; fprintd cannot
delay the sleep because it is starting inside the transition. A Synaptics
reader then comes back "unsupported firmware version" and that fprintd ignores
it for the rest of its life. The lock plugin checked availability once, at lock
time, so a check against that broken daemon left the lock password-only until
the next lock.

Follow logind's PrepareForSleep from the lock plugin itself, since the sleep
monitor exits to release its inhibitor and misses the resume half. On suspend,
stop retries and refuse new fprintd calls; on resume, run the check that was
held back, or restart the scan.

A scan already in flight is left alone. fprintd suspends and resumes the
reader itself, and libfprint only lets the kernel re-enumerate the reader
after sleep while a scan is running. Aborting the scan at suspend made fprintd
close the reader mid-transition: the close blocked until resume, the reader
woke with stale firmware state, and every scan failed until the daemon exited
a minute later.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015HE2TCjo1j9HnXq83cqsUX
@andershfranzen

Copy link
Copy Markdown

Tested on an HP EliteBook 8 G1i (Lunar Lake) with a Synaptics Prometheus 06cb:0106 press sensor (firmware 10.01.4443061): the same failure as the X1 Carbon in the description.

Setup: quattro at 9c5482c with this PR cherry-picked (applies cleanly; lock-fingerprint-suspend-test.sh and the existing lock tests pass), lock plugin loaded from that checkout. fprintd 1.94.5, libfprint 1.94.100, quickshell 0.3.1, Hyprland 0.56.2, locally built 7.2.2 kernel.

Baseline on stock quattro (journal, Sep 11–17): after every lid-open resume (7 of 7) the unlock went through omarchy-lock-password. fprintd had been activated during sleep entry (Failed to install a sleep delay inhibitor), the verify failed on resume (device was disconnected / transfer failed) and the reader re-enumerated. Once, the resume failed outright (usb_dev_resume returns -5, then Ignoring device due to initialization error: unsupported firmware version) and fprintd kept a stale claim: Device was already claimed 13,325 times over 37 hours, with fingerprint dead for the lock screen, sudo and polkit until a reboot.

With this PR, two lid close/open cycles:

cycle 1 cycle 2
fprintd activated during sleep entry no no
resumed → reader prompting 0.39 s 0.44 s
USB disconnect or fprintd errors on resume none none
unlocked by fingerprint, 7.8 s after lid open fingerprint, 4.6 s after lid open

The reader was armed within half a second both times; the rest of the time to unlock was the finger read itself.

Tested and written up by Claude Opus 5 via Claude Code.

@omarchybot omarchybot added bug Something isn't working compatibility Make Omarchy work better on everything! labels Sep 27, 2026
@omarchybot

Copy link
Copy Markdown
Collaborator

Reviewed at 2696e7b, merged locally onto current quattro (f45461a, merges cleanly). Claude Opus 5.5 reviewed it, with a second opinion from Codex Medium.

What ran, on a disposable Omarchy VM booted onto the merged tree. The lock tests in test/shell.d (including the new lock-fingerprint-suspend-test.sh, the sleep-lock and sleep-monitor tests) pass. ./test/cli fails only vscode generated theme references current theme file, which fails the same way on plain quattro. The VM has no fingerprint reader, so fprintd-list was replaced with a logging stub and the fingerprint PAM file with a pam_exec logger, and the machine was suspended through logind with an RTC wake:

  • On quattro, the lock ran fprintd-list 2 ms after lock-requested and started a fingerprint PAM session 105 ms before PM: suspend entry, which is the window this pull request describes.
  • On this branch, suspending reached the lock 14 ms before lock-requested, nothing touched fprintd until resumed (9 ms after PM: suspend exit), and then the held-back check ran and the scan started 20 ms later.

That proves the timing change, not the hardware outcome: whether a Synaptics reader survives the suspend can only be shown on one.

One gap, not a regression. bin/omarchy-system-lid-close locks on Hyprland's lid switch, deliberately before logind announces suspend, so on a lid close the shell's PrepareForSleep(true) and the lock request race. On the VM (a systemctl suspend, not a lid) the signal won. When the lock wins, fprintd-list is already running when suspending goes true, it is not held back, and a "no" from it still leaves that lock password-only after resume, exactly as on quattro today. Codex found this; I confirmed it against the source. Closing it would mean holding the check from the lid-close lock request itself, which is a design choice for the author and the maintainer rather than something to push here. The new test only matches source text: Codex reports all eight assertions still pass with suspending = sleeping removed, which matches what the regexes check.

Related. The race is the one @knordum describes in #12993 (06cb:0123), and @andershfranzen's results above match it. #9456, #10393, #12420 and #11273 change the same fingerprint start and retry paths for other causes. None of them holds fprintd back across suspend, so they overlap rather than compete, but whichever lands second will need its guards merged with this one.

Waiting on a reporter. A hardware fix counts as confirmed by the person who reported the bug or by a maintainer. @efecege, if you can, please test the exact commit on your ThinkPad and say here whether fingerprint still works after several lid-close suspends, naming the commit you ran:

git clone https://github.com/basecamp/omarchy.git ~/omarchy-9919
cd ~/omarchy-9919
git fetch origin pull/9919/head
git merge --no-edit 2696e7b41bf7996e9f03bd210dcef4c9202176f0
omarchy dev link ~/omarchy-9919

omarchy dev link reboots onto the checkout, and omarchy dev unlink puts the packaged install back.

@omarchybot

Copy link
Copy Markdown
Collaborator

Merged #7158 supplies post-resume daemon recovery and preserves fingerprint enrollment through failed availability probes. Deferring new fprintd activity during PrepareForSleep remains a distinct pre-suspend change and is not part of that merge. Keeping this open for that remaining mechanism; the shared lock code needs a rebase.

GPT-6 in Codex and Claude Opus 5.5 Medium checked the coverage against the landed source; Claude's agreement does not guarantee independence. This closure review was read-only and did not rerun runtime tests.

omarchybot and others added 2 commits October 7, 2026 15:04
…orSleep

omacom#7158 added a sleep watch that notices resume from a wall-clock gap, restarts fprintd through a resume hook, and aborts a scan that rode through the sleep. Left beside this branch's PrepareForSleep handling, the watch would notice the same resume up to a second later and abort the scan started on resume. Resume now runs the watch's recovery once, from the logind signal, and marks the watch as having seen it.

The availability probe is tri-state on quattro: an unknown answer keeps a known enrollment and starts nothing. Resume therefore restarts the scan even when it also runs a held-back check, since suspend stopped the retry that would otherwise have carried it.

The lock fingerprint service fixture now drives suspend and resume through the real QML service.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reach timeout omacom#7158 added aborts an attempt that has not prompted within 20 seconds. Left running after PrepareForSleep(true), it could fire in the window before sleep and abort the scan mid-transition, the close this branch exists to avoid. Stop it with the retry timer; resume already settles a scan that rode through.

omacom#7158 also reads an unreachable fprintd as an unknown enrollment rather than none, so the comment no longer claims a failed check leaves the lock password-only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Codex Medium <noreply@openai.com>
@omarchybot

Copy link
Copy Markdown
Collaborator

#7158 landed on quattro and this branch no longer merged, so I merged quattro into it and pushed two commits on top of 2696e7b: the merge (3558865) and one fix (c312fc4). Nothing was rebased or force-pushed. Claude Opus 5.5 did the work and Codex Medium reviewed it over two rounds.

What the merge changes. #7158 detects resume on its own: a sleep watch notices the wall-clock gap, restarts fprintd through a resume hook, and aborts a scan that rode through the sleep. Put next to this branch's resume handling unchanged, that watch would catch the same resume about a second later and abort the scan this branch had just started. Now prepareForSleep(false) runs #7158's recovery once (restartFingerprintAfterSleep(), which also opens its grace window) and marks the watch as having seen the resume. On quattro the enrollment probe can now answer "unknown", which keeps a known enrollment and starts nothing, so resume restarts the scan even when it also runs the check it held back.

What Codex found, fixed in c312fc4. #7158's 20-second reach timeout was still running after PrepareForSleep(true). If it fired before the machine slept, it would abort the scan mid-transition, the reader close this pull request exists to avoid. Suspend now stops it, and resume settles the scan as before. The comment above prepareForSleep no longer says a failed check leaves the lock password-only, because on quattro that answer reads as unknown.

What ran, on a disposable Omarchy VM running this branch's shell. All 26 lock, sleep and fingerprint tests in test/shell.d pass, and so does ./test/cli. #7158's real-QML lock service fixture now also runs this branch's suspend and resume: the reach timeout is stopped, a running scan is left alone, the check waits for resume, and resume opens the grace window and does not trigger the sleep watch's recovery a second time. With fprintd-list and the fingerprint PAM file stubbed out, and the VM suspended through logind with an RTC wake:

  • On quattro (d9b970d), the lock ran fprintd-list 2 ms after lock-requested and started a fingerprint PAM session 107 ms before PM: suspend entry.
  • On c312fc4's tree, suspending reached the lock 11 ms before lock-requested, and nothing touched fprintd until resumed. The held-back check ran 6 ms after resume, a scan started 13 ms after that, and the resume grace window opened.

That shows the timing, not the hardware outcome.

Still open.

  • The race from the earlier review still stands. When a lid-close lock beats PrepareForSleep(true), its check is already running and is not held back.
  • Codex's second round raised three narrow paths in the window before sleep. Codex went no further than reading the source and running the service's JavaScript with PAM and timers mocked; none of them ran on a machine that suspended. I left all three alone:
    • The sleep watch could still abort a scan, but only after a stall of more than 3 s inside a ~100 ms window.
    • A probe already running could still abort a scan, but only by coming back with a definite "no prints enrolled" while that scan is running.
    • A dbus-monitor exit is treated as resume. That is the deliberate never-get-stuck choice in this branch.

Waiting on a hardware test. Earlier results on real readers were against a tree without #7158. @wulujia, @andershfranzen, @efecege: if you can, please test c312fc4 through several lid-close suspends, and say here whether fingerprint unlock works after each one, naming the commit you ran:

git clone https://github.com/basecamp/omarchy.git ~/omarchy-9919
cd ~/omarchy-9919
git fetch origin pull/9919/head
git checkout --detach c312fc428bd8651a0488ae6fe2c7c7ca0299f5db
omarchy dev link ~/omarchy-9919

omarchy dev link reboots onto the checkout, and omarchy dev unlink puts the packaged install back.

@greptile-apps

greptile-apps Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 4/5

[Medium impact] The change affects fingerprint sign-in in the desktop lock workflow.

The PR still needs to prevent fingerprint startup from overlapping suspend before it is safe to merge.

Findings

  1. P1 Fingerprint startup still overlaps sleep ▶

Summary

The PR holds new fingerprint checks and scans while logind prepares to sleep.

  • Fingerprint checks wait until the laptop resumes.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A["PrepareForSleep(true)"] --> B["Stop retry and reach timers"]
  B --> C["Block new checks and scans"]
  C --> D["Leave an active scan running"]
  E["PrepareForSleep(false)"] --> F["Recover the previous attempt"]
  F --> G["Run any held-back check"]
  G --> H["Start or schedule the next scan"]
  I["Sleep monitor exits"] --> E
  I --> J["Restart monitor after 5 seconds"]
Loading

Reviews (2) · Last reviewed commit: "Stop the startup fingerprint probe befor..." · Reviewed by Greptile

Comment on lines +146 to 150
if (suspending) {
fingerprintCheckDeferred = true
return
}
if (!fingerprintCheckProc.running) fingerprintCheckProc.running = true

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Fingerprint startup still overlaps sleep

omarchy-system-lid-close requests the lock before PrepareForSleep, and beginLock() immediately schedules refreshFingerprintStatus(). If reader initialization is still running when the sleep signal arrives, prepareForSleep(true) leaves that check running. The sleep inhibitor waits only for sessionLock.secure, so sleep can still interrupt the reader reset and leave fingerprint unlock unavailable after waking.

Coordinate fingerprint startup with the lid-close path, or hold sleep until an already-started initialization finishes, without aborting a running scan.

Knowledge Base Used: Shell UI and desktop interactions

@omarchybot

Copy link
Copy Markdown
Collaborator

Checked Greptile's two findings on c312fc4 against the source. Claude Opus 5.5 did the review and Codex Medium gave a second opinion. Codex reached the same reading on both findings, though its independence is not guaranteed. Nothing was pushed and the head is unchanged, so the hardware test requested above still applies to c312fc4.

  • Startup still overlaps sleep: this is real. It is the same lid-close race the earlier review reported, and it is not a regression. bin/omarchy-system-lid-close locks before logind sends PrepareForSleep(true), so a check that started on that lock keeps running. quattro starts the same check unconditionally, and this branch holds back only the checks that come after the signal. Closing the window would mean coordinating the lid-close lock with the fingerprint gate before logind announces sleep, including closes that never suspend. That is a design decision for the author and the maintainer, so it was not pushed here.
  • Resume test misses process startup: this is partly right. The QML fixture checks only that fingerprintCheckDeferred clears on resume, and it never observes the check process starting. Removing the call would not go unnoticed, though: test/shell.d/lock-fingerprint-suspend-test.sh:58 requires refreshFingerprintStatus() inside the held-back branch of prepareForSleep. That test reads the source text and does not exercise the behaviour at runtime. A fixture assertion on the process would be stronger, but adding one would move the head the reporters were just asked to test, so it was not pushed.

This is still waiting on a test on a real fingerprint reader.

@prabhatCH

Copy link
Copy Markdown

Hardware report: Dell XPS 15 9500, Goodix 27c6:533c, Omarchy 4.0.6-1, fprintd 1.94.5-2, libfprint-tod 1.95.2+tod1-1, and libfprint-goodix-53xc 0.0.6-2.

This overlaps with a suspend/resume failure we investigated today. Immediately after resume, the journal recorded:

Authorization denied ... ListEnrolledFingers ... Not Authorized: net.reactivated.fprint.device.verify

The reader worked after interacting with the lock screen, but initially would not unlock on a direct finger touch. A local lock-plugin workaround now pauses new attempts during sleep preparation, retains the known enrollment instead of probing it immediately on resume, and waits 1.5 seconds after PrepareForSleep(false) before clearing the sleep/blanked flags, waking the display, and rearming scanning. The owner confirmed lid-open followed by a finger touch works without clicking or pressing a key.

This is a combined workaround, not an isolated test of this PR: the display blank timeout was also increased from 5 to 30 seconds, retries are paced at 5 seconds, and fprintd is kept resident with --no-timeout, started at boot, and configured with Restart=on-failure. Its sleep-delay inhibitor was verified active. Earlier, a daemon activated during sleep preparation failed to register its inhibitor; a later crash was inside the proprietary Goodix driver.

Our local workaround currently aborts the PAM scan during sleep preparation. Your warning about that behavior on Synaptics is valuable: we have only confirmed short lid-close tests on this Goodix so far, not overnight sleep or cold boot. This should not be treated as evidence that aborting active scans is safe across readers.

Sharing the hardware result in support of the resume coordination work here; happy for this report to inform testing rather than suggesting these local defaults be copied wholesale.

@prabhatCH

Copy link
Copy Markdown

I prepared an updated branch to help move this forward: https://github.com/prabhatCH/omarchy/tree/fix/9919-upstream-update

@wulujia: you are welcome to merge this branch into fix/lock-fingerprint-suspend; it retains your existing history and adds two commits:

  • 4933ce3d1: merge current upstream quattro (087f73d89). Resolve the startFingerprint() conflict by retaining both upstream's fingerprintPaused gate and this PR's suspending gate.
  • 0d20c4be4549a2903099fe3c2a6db6a88113f9d8: strengthen the existing real-QML fixture with a controlled probe command. It checks that the process does not start during sleep preparation, starts on resume, and actually produces output. Removing the resume refreshFingerprintStatus() call makes the runtime test fail on both process-start and execution assertions. This addresses the runtime coverage gap from review.

The earlier lid-close startup race is still unresolved: when the early lid-close lock beats PrepareForSleep(true), initialization may already be in progress. This update is conflict resolution plus test coverage, not a claim that the PR is ready to merge or that the race is fixed.

Validation on this machine:

  • All 10 lock-*-test.sh files passed with the checkout's bin/ on PATH, including the real-QML service fixture and suspend test.
  • The missing-resume-call mutation fails the real-QML test, as described above.
  • git diff --check origin/quattro..HEAD passed.
  • ./test/all ran to completion: CLI passed; shell reported 18 failures among 468 test files, with 10 files containing skipped checks. Each failing file was rerun on both this branch and a separate clean 087f73d89 worktree, using each checkout's bin/ on PATH. Three passed in both (system-power, keybindings-menu, brave-widevine); the other 15 failed in both. These are baseline/environment failures, not a green full-suite result. The baseline comparison did not reveal an additional failing test introduced by this update.
Failures persisting in both trees

background-instant-reload, background-intro-clone, battery-status, crash-capture, elsewhen-migration, hyprland-workspace-layout, i18n, menu-plugin, migrate-notify, provision-user, screenrecording, screenrecording-wf-audio, screenshot-sanity, sleep-lock, update-restart-kernel.

@efecege @andershfranzen: if you have time, could you test the exact updated commit 0d20c4be4549a2903099fe3c2a6db6a88113f9d8 on your readers, including several short lid-close cycles and a longer sleep? Please name the commit, reader USB ID, driver versions, and whether direct fingerprint unlock works after resume. In particular, journal evidence of probe/PAM startup before suspend and any reader initialization errors would help distinguish the remaining race. No rush; thanks for the hardware reports already in this thread.

The earlier Dell XPS/Goodix report above tested a separate combined local workaround, not this branch. I have not installed this development branch as the laptop's desktop or claimed hardware validation of it. Work and automated verification were performed with Codex.

The deferred-probe check waits for the service's own startup probe before installing its controlled command, and that probe runs the real fprintd-list. On a machine with a fingerprint reader set up, a slow activation could hold it past the check's two-second deadline and fail the test before it tested anything. Stop the startup probe instead of waiting on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Codex Medium <noreply@openai.com>
@omarchybot

Copy link
Copy Markdown
Collaborator

This branch conflicted with quattro after #15294, so I fast-forwarded it to @prabhatCH's update and added one test fix on top. The head is now 3f9a46f. Nothing was rebased or force-pushed. Claude Opus 5.5 did the review and Codex Medium gave a second opinion over two rounds.

What landed. @prabhatCH's merge of quattro (4933ce3) resolves the one conflict by keeping both gates in startFingerprint(): #15294's fingerprintPaused and this branch's suspending. I made the same merge independently and got an identical tree. Their second commit (0d20c4b) adds a runtime check to the lock service fixture: a check requested after PrepareForSleep(true) does not start, starts on PrepareForSleep(false), and actually runs. That closes the coverage gap Greptile raised.

What Codex found, fixed in 3f9a46f. The new check waited for the service's startup probe first, and that probe runs the real fprintd-list. On a machine with a reader set up, a slow activation could hold it past the check's 2-second deadline and fail the test before it tested anything. The fixture now stops that probe instead of waiting for it. This changes only the test. The shell code is the same as at 0d20c4b, so results from testing that commit still count.

What ran, on a disposable Omarchy VM running this branch's shell. ./test/cli passed, and all 26 lock, sleep and fingerprint tests in test/shell.d passed except lock-appear-budget. That test also fails on quattro (087f73d) on the same VM and passed once on this branch, so it is a timing problem on this VM, not this change. The fixture fails when the held-back check is removed from resume. With a fprintd-list stub that sleeps 10 seconds, 0d20c4b's fixture fails and 3f9a46f's passes. I did not repeat the logind suspend timing run from the earlier review. The resolved conflict is one line and leaves this branch's suspend handling unchanged.

Still open, and not pushed.

Waiting on a hardware test. No real reader has run this code with quattro merged in. @wulujia, @andershfranzen, @efecege: if you can, please test 3f9a46f (or 0d20c4b, which runs the same shell code) through several lid-close suspends, including one long sleep. Say here whether fingerprint unlock works after each one, and name the commit you ran:

git clone https://github.com/basecamp/omarchy.git ~/omarchy-9919
cd ~/omarchy-9919
git fetch origin pull/9919/head
git checkout --detach 3f9a46f09641c6c522617268b074c3bec9f72fb4
omarchy dev link ~/omarchy-9919

omarchy dev link reboots onto the checkout, and omarchy dev unlink puts the packaged install back. @prabhatCH, thank you for the merge and the test. Your Goodix report used a separate workaround, so it does not yet count as a test of this branch. A run of this commit on that machine would.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working compatibility Make Omarchy work better on everything!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants