1. 10 Mar, 2019 1 commit
  2. 15 Jan, 2019 1 commit
  3. 12 Jan, 2019 1 commit
  4. 11 Jan, 2019 4 commits
  5. 18 Sep, 2018 1 commit
    • Kai Lüke's avatar
      Remove redundant error showing · f0a7acaf
      Kai Lüke authored
      The gdu_*_ensure_unused machinery already
      displays the unmounting error. At many places
      in the UI (but not in every case) the error
      was shown again a second time.
      
      This error was discovered as part of
      #101
      f0a7acaf
  6. 12 Sep, 2018 1 commit
  7. 03 Sep, 2018 1 commit
  8. 11 Aug, 2018 1 commit
  9. 27 Jul, 2018 1 commit
    • mtvoid's avatar
      Fix swapped "Number of Samples" tooltips in benchmark dialog · 3b7e850f
      mtvoid authored
      In the benchmark dialog, there are two values for the
      number of samples, one for the transfer rate, and the
      other for the access time measurements.
      The tooltips for the two are swapped.
      
      This patch corrects this error by swapping the tooltips
      for "Transfer Rate" and "Access Time".
      
      !3
      3b7e850f
  10. 24 Jul, 2018 1 commit
  11. 30 May, 2018 1 commit
    • Kai Lüke's avatar
      Query NTFS tooling from UDisks · 27d1bcb0
      Kai Lüke authored
      Disks queried for mkntfs in the $PATH directly
      which does not work for non-sudoers.
      
      Port the gdu_utils_is_ntfs_available function
      to ask UDisks 2.7.2 (if available) whether
      NTFS creation is supported.
      
      #83
      27d1bcb0
  12. 25 May, 2018 1 commit
    • segfault3's avatar
      Add TrueCrypt/VeraCrypt support · 30422ec7
      segfault3 authored
      This is a combination of 4 commits:
      
      - Disable "Encryption Options" for non-LUKS devices
      
      - Disable "Change Passphrase" for non-LUKS devices
      
      - Rename volume-content-luks to volume-content-crypto
      
      - Add TCRYPT option widgets to the unlock dialog
      
      This extends the unlock dialog by widgets which allow specifying the
      parameters supported by TrueCrypt and VeraCrypt volumes. This includes:
      
       - Whether the volume to be unlocked is hidden.
       - Whether the volume to be unlocked is a system partition.
         Note: TrueCrypt and VeraCrypt only support encrypting Windows system
         partitions [1], so the label for this option is "Windows system".
       - Whether to use a PIM [2].
       - Whether to use one or multiple keyfiles. In the beginning there is
         only one button to choose a single keyfile. When a keyfile is chosen,
         another button appears below to allow selecting another keyfile, and
         so on.
      
      Since TCRYPT volumes cannot be reliably detected as such, a label is
      displayed at the top of the unlock dialog to indicate to the user that
      this volume might not actually be encrypted.
      
      [1] https://www.veracrypt.fr/en/System%20Encryption.html
      [2] https://www.veracrypt.fr/en/Header%20Key%20Derivation.html
      30422ec7
  13. 08 May, 2018 1 commit
  14. 12 Mar, 2018 1 commit
  15. 20 Feb, 2018 2 commits
  16. 04 Feb, 2018 1 commit
  17. 18 Jan, 2018 1 commit
    • Will Thompson's avatar
      restore: don't attempt to open target read-only · bfd153d7
      Will Thompson authored
      This code seems to be duplicated from gducreatediskimagedialog.c, but in
      this context we need 'fd' to be writable. We could still attempt to
      open() the device directly (with O_WRONLY) but as the comment says, by
      definition /dev/sr* is read-only by nature (or at least, cannot be
      written to in this way), so it is unlikely to be of any use.
      
      In any case, in practice this code path will never be taken since the
      "Restore" action is not available for optical media.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=792581
      bfd153d7
  18. 15 Nov, 2017 1 commit
  19. 13 Nov, 2017 2 commits
  20. 20 Oct, 2017 1 commit
  21. 29 Sep, 2017 1 commit
    • Kai Lüke's avatar
      Keep FS mounted while growing partition · 987823a1
      Kai Lüke authored
      Growing the partition for offline resize caused
      a rediscovery in UDisks to led to GVFs automount
      which lets the Disks filesystem resize call fail.
      
      A good solution is to keep the filesystem mounted
      while growing the partition, as it is done in the
      online resize already. This way there will be no
      rediscovery and automount, and the filesystem can
      be unmounted afterwards to be grown. From this point
      there will be no automount coming because the partition
      size is not touched anymore.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=788326
      987823a1
  22. 18 Sep, 2017 5 commits
  23. 11 Sep, 2017 2 commits
  24. 21 Aug, 2017 2 commits
  25. 15 Aug, 2017 1 commit
    • Kai Lüke's avatar
      Correct text for partition size entry · 5d7b90aa
      Kai Lüke authored
      The tooltip was always claiming to have MB as unit
      while the unit could be changed to any other.
      The new image dialog was talking about partitions.
      
      Mentioning the unit is removed. In the label and tooltip
      of the new image dialog "partition" is replaced by "image".
      The tooltip markup text is deleted instead of updated
      because it's not in use.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=786276
      5d7b90aa
  26. 10 Aug, 2017 2 commits
  27. 08 Aug, 2017 1 commit
  28. 07 Aug, 2017 1 commit