1. 21 Sep, 2018 1 commit
  2. 17 Sep, 2018 1 commit
  3. 14 Sep, 2018 1 commit
  4. 13 Sep, 2018 5 commits
  5. 08 Sep, 2018 1 commit
  6. 07 Sep, 2018 4 commits
  7. 06 Sep, 2018 2 commits
  8. 30 Aug, 2018 3 commits
  9. 23 Aug, 2018 1 commit
  10. 22 Aug, 2018 7 commits
  11. 17 Aug, 2018 2 commits
  12. 16 Aug, 2018 2 commits
    • Matthias Clasen's avatar
      network monitor: Update portal implementation · 7ddd1de0
      Matthias Clasen authored
      The network monitor portal interface is changing.
      Version 2 is no longer using properties, but getters
      instead (this lets the portal apply access control
      and avoid sending information to non-networked
      sandboxes).
      
      To support both version 1 and 2 of the interface,
      we stop using generated code and instead deal with
      the api differences in our own code, which is not
      too difficult.
      
      Support version 1 as well
      7ddd1de0
    • Milan Crha's avatar
      gnetworkmonitor: Fix use-after-free when using from another thread · edcce31f
      Milan Crha authored
      When using g_network_monitor_get_default() from another thread, it’s
      possible for network-changed events to be processed after an instance of
      GNetworkMonitor has been disposed, causing use-after-free problems.
      
      Fix that by moving some of the initialisation into the GInitable.init()
      chain, rather than in a main context idle callback.
      
      This includes a unit test which probabilistically reproduces the bug
      (but can’t do so deterministically due to it being a race condition).
      
      Commit amended by Philip Withnall <withnall@endlessm.com> before
      pushing.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=793727
      edcce31f
  13. 09 Aug, 2018 4 commits
  14. 03 Aug, 2018 2 commits
    • Ondrej Holy's avatar
      gio-tool: Hold GVolumeMonitor reference during operations · 2c1aee19
      Ondrej Holy authored
      Releasing GVolumeMonitor before g_volume_mount finish cause that
      g_volume_get_mount returns NULL, because the mount is not correctly
      propagated to the volume.
      
      (Backported from commit 88b8ebb5 with
      minor merge conflicts.)
      
      #1458
      2c1aee19
    • Ondrej Holy's avatar
      gio: Update mounts after g_volume_mount · f9ab3558
      Ondrej Holy authored
      The documentation claims that g_volume_get_mount should	succeed	after
      g_volume_mount. Let's update mounts before releasing g_volume_mount to
      be sure that the mount is added to the corresponding volume. The same
      is done in GVfsUDisks2VolumeMonitor.
      
      (Backported from commit 9b6b282e with no
      merge conflicts.)
      
      #1458
      f9ab3558
  15. 29 Jun, 2018 1 commit
  16. 13 Jun, 2018 3 commits