- Apr 10, 2018
-
-
Kalev Lember authored
-
Kalev Lember authored
-
- Mar 20, 2018
-
-
- Mar 11, 2018
-
-
- Mar 09, 2018
-
-
Kalev Lember authored
We don't have any UI in the app row to cancel an ongoing install/remove operation.
-
Kalev Lember authored
It only makes sense to make the Install/Remove buttons insensitive while we're in INSTALLING or REMOVING state.
-
Kalev Lember authored
We only have 1 page that uses it, out of 7, which makes non-colorful a better default.
-
- Mar 03, 2018
-
-
Marek Cernocky authored
-
- Mar 02, 2018
-
-
Kalev Lember authored
-
Kalev Lember authored
-
There was a comment left by mistake (copy&paste) indicating that flatpak_installation_list_installed_refs_for_update doesn't do any no network I/O which is false.
-
These changes avoid a race when apps are refined from within a different thread, as their properties' notification were being emitted (and thus triggering) code from those. Specifically there was a race when setting up the CSS for the background tile as this code was not getting run from the main loop.
-
Kalev Lember authored
If we happened to refresh the whole page while unreveal idle has not yet had a chance to run, we may end up with the row already removed from the list box. In that case, return early and avoid printing a critical warning.
-
Kalev Lember authored
-
Kalev Lember authored
This regressed in commit f007e5e7
-
-
Kalev Lember authored
When adding related apps for sources, avoid updating their state when they already have a state set. This fixes state change warnings when opening the repos dialog: State change on system/flatpak/flathub/desktop/org.gnome.Recipes.desktop/stable from updatable-live to installed is not OK
-
Kalev Lember authored
-
Kalev Lember authored
Don't mark apps we can't find in the repos as UNAVAILABLE as this state is for apps that we _do_ find in the repos, but the repo is disabled (but metadata_enabled=1 so it's searchable). Instead, leave these in UNKNOWN state so they don't show up in the UI. This fixes apps we have in the appstream metadata (such as Google Chrome on Fedora), but not in any available repos to correctly not show. This should also help with https://bugzilla.redhat.com/show_bug.cgi?id=1464139
-
Kalev Lember authored
We've been using ODRS instead, and the Fedora tagger service is now going away.
-
This applies changes to the flatpak remote which come from the summary file, such as updated keys, titles or the URL. Adding it into the appstream refresh function means it's behind the timestamp checks and skipping broken remotes, which avoids adding network roundtrips to the refresh. libflatpak caches the summary file in the common case that the remote details have not changed. https://phabricator.endlessm.com/T20328
-
- Feb 23, 2018
-
-
Fixes: GLib-GIO-ERROR **: Settings schema 'org.gnome.software' does not contain a key named 'external-appstream-system-wide'
-
Joaquim Rocha authored
It needs to be installed in the libexecdir that's given as an option.
-
Joaquim Rocha authored
The key is GnomeSoftware::quirks::not-launchable and is useful if we want to override this quirk more directly than using the component type and the inexistence of the launchable tag.
-
Joaquim Rocha authored
It used to be 10 minutes which can be too much for some users.
-
The Details page uses a fixed size frame, which doesn't scale down when running on low resolution devices. This renders the main window way too big on low resolution displays. Fix that by making the Details page scroll horizontally when needed. https://phabricator.endlessm.com/T11698
-
Joaquim Rocha authored
Meson was not well configured for this plugin and thus building it was failing.
-
Joaquim Rocha authored
It was calling GET_POPULAR with no refine flags, which effectively ends up performing no refine at all after getting the popular apps (and this left the apps invalid and thus not considered).
-
Joaquim Rocha authored
Among other possible issues, these changes fix a problem when overriding the popular apps (through GSettings) because it would end up showing invalid apps as those were not being filtered.
-
The header buttons are the major offenders when dealing with low resolution displays, and they render the window unresizable even on views that can resize. In order to detect that, this commit adds a new method to check if the current display has a low resolution. We're considering anything below 800x600 as low resolution right now. This assumption can change as we see fit. The header buttons are adapted on realize, when it is guaranteed that the window is in a monitor, and the fix is making the views buttons non-homogeneous. https://bugzilla.gnome.org/show_bug.cgi?id=787366
-
Administrator authored
-
- Feb 20, 2018
-
-
Robert Ancell authored
This in particular caused the Snap search results to be alphabetically ordered. They are returned from the search API in importance order so they shouldn't be changed. If all quality properties of a search result are the same, there doesn't seem to be an issue keeping them in the order the plugins returned.
-
- Feb 18, 2018
-
-
Robert Ancell authored
-
- Feb 16, 2018
-
-
Richard Hughes authored
This reverts commit 728877d7.
-
Richard Hughes authored
See https://blogs.gnome.org/hughsie/2018/02/16/ for more details.
-
- Feb 09, 2018
-
-
Robert Ancell authored
-
Robert Ancell authored
-
- Feb 08, 2018
-
-
Kalev Lember authored
-
Kalev Lember authored
-
Kalev Lember authored
Temporarily disable the infobar on the overview page until we've fixed all the quirks and reworded the text. This makes it possible for us to move forward with 3rd party repos in F27 and installing them through the Software Sources dialog, without having to first make the overview page code work work reliably.
-