Skip to content
  1. Jul 19, 2019
  2. May 08, 2019
  3. Mar 21, 2018
  4. Mar 05, 2018
  5. Feb 07, 2018
  6. Jan 16, 2018
  7. Nov 18, 2017
  8. Oct 24, 2017
  9. Sep 22, 2017
  10. Aug 27, 2017
  11. Aug 23, 2017
  12. Aug 19, 2017
    • Georges Basile Stavracas Neto's avatar
      online-accounts: Fix parameter parsing · f914f54c
      Georges Basile Stavracas Neto authored
      The Online Accounts panel supports two commands: 'add'
      and 'show-account'. The 'add' command must receive an
      additional parameter, the 'provider' name, and an
      optional 'preseed' parameter.
      
      In the past, Settings would just push all the parameters
      to a GVariant and pass to the panels. Now, however, it
      skips the first one, making the parameter parsing code
      in Online Accounts panel wrong.
      
      This patch fix that by refactoring add_account() code,
      and fixing the GVariant parameter parsing.
      f914f54c
  13. Aug 17, 2017
    • Georges Basile Stavracas Neto's avatar
      online-accounts: Fix crash after aborting web view and changing panels · d838d035
      Georges Basile Stavracas Neto authored
      The panel owns both the GtkDialog, and the GoaProvider that is used
      with the dialog during goa_provider_add_account. When the panel is
      destroyed, it drops its references to the provider but not the dialog,
      which is a separate top-level widget. Therefore, if the panel is
      switched while the WebKitWebView inside the dialog was still
      navigating across pages, then WebKitWebView::decide-policy will be
      called with an invalid provider.
      
      To avoid this, and a memory leak, the panel should also destroy the
      dialog when it is itself getting destructed.
      
      Note that since the GtkDialog is a template child, it must be
      destroyed in dispose. GtkWidget's (ie. the panel's) default default
      destroy signal handler NULLifies all template children pointers, so
      finalize is too late.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=782043
      d838d035
  14. Aug 07, 2017
  15. Aug 01, 2017
  16. Jul 22, 2017
  17. Jul 20, 2017
  18. Jul 18, 2017
  19. Jul 13, 2017
  20. Jul 07, 2017
  21. Jul 06, 2017
  22. Jul 05, 2017
    • Jason Gerecke's avatar
      wacom: Correct order of area calibration values · 83bdd852
      Jason Gerecke authored and Carlos Garnacho's avatar Carlos Garnacho committed
      Commit cf408c27 changed how the values stored in the "area" key were
      calculated in order be compatible with its updated schema. Unfortunately,
      it overlooked the fact that updated schema also changed the order of the
      values from "left, top, right, bottom" to "left, right, top, bottom".
      Because of this, corrections intended to be applied to the top and right
      screen edges were swapped. This can cause a noticible cursor offset to
      occur after finishing calibration.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=784009
      83bdd852
    • Jason Gerecke's avatar
      wacom: Drop old_axes from calibration API · be835b32
      Jason Gerecke authored and Carlos Garnacho's avatar Carlos Garnacho committed
      The calibration utility was modified in cf408c27 to return unitless
      padding measurements instead of axis values for storage in gsettings.
      Unfortunately, the code still assumes in some places that it is working
      with axes rather than paddings. This causes subtle math errors that
      result in undesired cursor offsets after the calibration is applied.
      
      Fortunately, this can be simplified, since tablet area is always reset
      to the default state before starting calibration, we are sure that the
      value will remain constant. Since both axes are in the same 0..1 scale,
      calibration code doesn't need to swap X/Y back and forth to calculate
      each axis scale.
      
      Additionally, the code to get the calibrated axis values has been moved
      into its own function along with a new function that returns padding
      values suitable for consumption by g-c-c. All calculations are performed
      internally in the 0..1 range.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=784009
      
      
      
      Co-Authored-By: default avatarCarlos Garnacho <carlosg@gnome.org>
      be835b32
  23. Jun 30, 2017
  24. Jun 21, 2017
  25. Jun 16, 2017
  26. Jun 12, 2017
  27. Jun 02, 2017
  28. May 17, 2017
  29. May 12, 2017
  30. May 10, 2017
  31. May 05, 2017
    • Mohammed Sadiq's avatar
      hostname-helper: don't read past '\0' · 7ca14779
      Mohammed Sadiq authored and Bastien Nocera's avatar Bastien Nocera committed
      g_utf8_find_next_char() doesn't do checks whether the char
      is '\0' or not. We have to take care of that ourself.
      
      This commit fixes heap-buffer-overflow found by test-hostname
      
      ERROR: AddressSanitizer: heap-buffer-overflow on address
      READ of size 1 at 0x60200000cd76 thread T0
       #0 0x7f8b26920d08 in g_utf8_find_next_char glib/glib/gutf8.c:179
       #1 0x55c2b8eacaee in pretty_hostname_to_ssid gnome-control-center/shell/hostname-helper.c:199
      
      https://bugzilla.gnome.org/show_bug.cgi?id=782216
      7ca14779