Fix updates for user installs in sandbox#1415
Merged
kolunmi merged 1 commit intobazaar-org:mainfrom Apr 14, 2026
Merged
Conversation
Collaborator
|
I can confirm this fixes the issue under these conditions refresh and click update in bazaar 
|
Collaborator
|
looks good! However |
Collaborator
Author
Collaborator
|
o nvm :vlone: |
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
3 participants
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.
Flatpak would set the
.desktopfile to point to the Flatpak executable found in the Bazaar sandbox, so breaking the.desktopfile. Overwriting theFLATPAK_BINARYenvironment variable with the true Flatpak executable path fixes this.I made it so user update fetching gets disabled if it can’t find the correct path.