Repository navigation
Show the real wallpaper, not its snapshot, when nothing is on screen yet - #3
Merged
Merged
Conversation
kwsantiago
force-pushed
the
first-background
branch
from
October 19, 2026 18:06
e68ae18 to
5956eb4
Compare
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.
A freshly flashed phone could boot to a blank desktop instead of the theme's wallpaper.
On the first theme set,
omarchy-theme-sethands the shell a snapshot of the wallpaper and deletes it three seconds later. With nothing on screen yet,Background.qmldisplayed the snapshot rather than the real file. If the phone had not decoded the 5120x2880 image within those three seconds, the image failed to open, and re-reading the background link did nothing because the shell took the real file as already shown.Change
pkgbuilds/omarchy-config/first-background.patch: when nothing is displayed, showfinalPathinstead ofpath. Upstream made the same change after our pin, so the patch is dropped at the next bump.pkgbuilds/omarchy-config/PKGBUILD: applies it after the other two patches under the same no-fuzz, no-offset guards; pkgrel 8.Testing
Replayed
prepare()against the pinned tarball (sha256 matches): all three patches apply with no offset and no stray.orig/.rej, and theColor.guard passes. The resulting file differs from the shipped one by that single line.On a Pixel 3a, with the shell started with nothing displayed and the snapshot gone before it loads, which is the state the first boot reached: the stock file logs
Cannot open: .../background-transitions/next-repro.jpgand stays blank after abackground refresh; the patched file shows the wallpaper and logs nothing.