# Generated by Makefile. Do not edit.

2018-08-22  Curtis Gedak <gedakc@gmail.com>

    ==========   gparted-0.32.0   ==========

2018-08-22  A S Alam <amanpreet.alam@gmail.com>

    Update Punjabi translation

2018-08-21  صفا الفليج <safa1996alfulaij@gmail.com>

    Update Arabic translation

2018-08-20  Fabio Tomat <f.t.public@gmail.com>

    Add Friulian translation

2018-08-20  Alan Mortensen <alanmortensen.am@gmail.com>

    Updated Danish translation

2018-08-19  Daniel Șerbănescu <daniel@serbanescu.dk>

    Update Romanian translation

2018-08-19  Daniel Șerbănescu <daniel@serbanescu.dk>

    Update Romanian translation

2018-08-18  Mario Blättermann <mario.blaettermann@gmail.com>

    Update German translation

2018-08-18  Jiri Grönroos <jiri.gronroos@iki.fi>

    Update Finnish translation

2018-08-18  Hannie Dumoleyn <hannie@ubuntu-nl.org>

    Update Dutch translation

2018-08-17  Mario Blättermann <mario.blaettermann@gmail.com>

    Update German translation

2018-08-17  Aurimas Černius <aurisc4@gmail.com>

    Updated Lithuanian translation

2018-08-17  Baurzhan Muftakhidinov <baurthefirst@gmail.com>

    Update Kazakh translation

2018-08-17  Trần Ngọc Quân <vnwildman@gmail.com>

    Updated Vietnamese translation
    
    Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>

2018-08-16  Anders Jonsson <anders.jonsson@norsjovallen.se>

    Update Swedish translation

2018-08-16  Claude Paroz <claude@2xlibre.net>

    Updated French translation

2018-08-16  Anders Jonsson <anders.jonsson@norsjovallen.se>

    Update Swedish translation

2018-08-16  Emin Tufan Çetin <etcetin@gmail.com>

    Update Turkish translation

2018-08-09  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update help manual with opening and closing encrypted partitions (#795617)
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2018-08-13  Yi-Jyun Pan <pan93412@gmail.com>

    Update Chinese (Taiwan) translation

2018-07-28  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update Autoconf macro AX_CXX_COMPILE_STDCXX_11 to latest serial 18
    
    Update to the latest version of the AX_CXX_COMPILE_STDCXX_11 macro from
    the Autoconf Archive,  Note that the macro now depends on
    AX_CXX_COMPILE_STDCXX so this macro has to be included too.

2018-07-09  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Remove unused member Win_GParted::menu_item
    
    Usage of menu_item was removed in this commit from 2006.
    
        fb672f5219c5cceaae26246fb2c914478b8d2bbd
        happy new year ;) fixed some alignment issues removed confirmation dialogs

2018-07-09  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Remove unused members Win_GParted::label_device_info[12]
    
    Usage of members label_device_info1 and label_device_info2 was removed
    in this commit from 2004.
    
        8ae5ebb2e6d91e2671851e25659e19a90925d65c
        several (mostly) i18n related fixes/cleanups

2018-07-30  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Re-add getting EXT2/3/4 free space from dumpe2fs as a fallback (#8)
    
    If an EXT2/3/4 file system needs checking, then resize2fs will report an
    error, rather than report the minimum file system size.
    
        # mkfs.ext4 /dev/sdb11
        # resize2fs -P /dev/sdb11
        resize2fs 1.42.9 (28-Dec-2013)
        Estimated minimum size of the filesystem: 17012
        # debugfs -w -R "ssv state 0" /dev/sdb11
        # resize2fs -P /dev/sdb11
        resize2fs 1.42.9 (28-Dec-2013)
        Please run 'e2fsck -f /dev/sdb11' first.
    
        # echo $?
        1
    
    This will prevent GParted reading the file system usage and in turn
    GParted won't allow the file system to be shrunk.  Re-add the previous
    method of reading the free space from dumpe2fs output as a fallback.
    
    With this change, the worst case scenario is that GParted allows the
    user to attempt to shrink an unclean EXT4 file system, smaller that that
    which resize2fs allows and gets an error telling them so.  As part of
    the failed shrink operation GParted will have checked the file system so
    on refresh GParted will get the correct minimum size next time.
    
    This scenario only seems to apply to unclean EXT4 file systems because
    resize2fs has a larger minimum size that the free blocks would suggest
    because of extra space requirements when resizing EXT4 file systems [1].
    
    [1] e2fsprogs 1.44.3, resize/resize2fs.c:calculate_minimum_resize_size()
        https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/resize/resize2fs.c?h=v1.44.3#n2946
        /*
         * For ext4 we need to allow for up to a flex_bg worth of
         * inode tables of slack space so the resize operation can be
         * guaranteed to finish.
         */
    
        /*
         * We need to reserve a few extra blocks if extents are
         * enabled, in case we need to grow the extent tree.  The more
         * we shrink the file system, the more space we need.
         *
         * The absolute worst case is every single data block is in
         * the part of the file system that needs to be evacuated,
         * with each data block needs to be in its own extent, and
         * with each inode needing at least one extent block.
         */
    
    Closes #8 - Shrinking an EXT4 partition does not respect resize2fs
                limits

2018-07-19  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Use resize2fs -P to get minimum EXT2/3/4 FS size (#8)
    
    A user reported GParted failed to shrink an EXT4 file system because
    GParted tried to shrink it smaller than resize2fs reported minimum size.
    Operation details were:
    
        Shrink /dev/sdc1 from 931.51 GiB to 605.00 GiB             (ERROR)
          calibrate /dev/sdc1                                      (SUCCESS)
            path: /dev/sdc1 (partition)
            start: 63
            end: 1953520064
            size: 1953520002 (931.51 GiB)
          check file system on /dev/sdc1 for errors and (if poss...(SUCCESS)
            e2fsck -f -y -v -C 0 '/dev/sdc1'                       (SUCCESS)
              ...
              158165624 blocks are used (64.77% of 244190000)
              ...
          shrink file system                                       (ERROR)
            resize2fs -p '/dev/sdc1' 634389176K                    (ERROR)
              resize2fs 1.44.2 (14-May-2018)
              resize2fs: New size smaller than minimum (171882113)
    
    The GParted figures:
     *  Partition size    = 1953520064 (512b sectors) = 976760032 KiB
     *  FS size           = 244190000 (4K blocks)     = 976760000 KiB
     *  Used FS size      = 158165624 (4K blocks)     = 632662496 KiB
     *  Requested FS size                             = 634389176 KiB
    The resize2fs figure:
     *  Minimum FS size   = 171882113 (4K blocks)     = 687528452 KiB
    
    GParted uses the number of free blocks in the file system to determine
    the minimum size it can shrink a file system to.  However resize2fs uses
    it's own internally calculated minimum size and won't shrink a file
    system below that size, as seen in the above details.  Resize2fs does
    have a force flag, (-f) which overrides some safety checks which are
    normally enforced, to allow it to try to shrink a file system smaller
    than it's calculated minimum.  GParted currently doesn't use the force
    flag and it seems unwise for it to start to do so.
    
    So for unmounted EXT2/3/4 file systems, change GParted to use
    'resize2fs -P' to get the minimum file system size, rather than using
    the number of free blocks direct from the super block, as reported by
    'dumpe2fs -h'.
    
    Mounted file systems still use statvfs() to provide file system usage.
    As mounted EXT2/3/4 file systems can't be shrunk the fact that statvfs()
    produces different, possibly smaller than minimum, figures than those
    from 'resize2fs -P' doesn't matter.
    
    Closes #8 - Shrinking an EXT4 partition does not respect resize2fs
                limits

2018-07-30  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Work in FS blocks until later while reading EXT2/3/4 usage (#8)
    
    No functional change.  Just work in FS block sized units until as late
    as possible in ext2::set_used_sectors(), before converting to device
    sector size units.  This is to make the following change simpler and
    easier to understand.
    
    Closes #8 - Shrinking an EXT4 partition does not respect resize2fs
                limits

2018-07-24  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Stop xmllint scrollkeeper-omf.dtd fetch failure breaking CI tests (#9)
    
    The GitLab Continuous Integration test stage jobs can fail like this:
    
        $ make check
        ...
        Making check in help
        make[1]: Entering directory `/builds/mfleetwo/gparted/help'
        ...
        xmllint --noout --xinclude --dtdvalid 'http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd' gparted-C.omf
        warning: failed to load external entity "http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd"
        Could not parse DTD http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd
        xmllint --noout --xinclude --dtdvalid 'http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd' gparted-cs.omf
        ...
        make[1]: *** [check-doc-omf] Error 2
        make[1]: Leaving directory `/builds/mfleetwo/gparted/help'
        make: *** [check-recursive] Error 1
        ERROR: Job failed: exit code 1
    
    It fails when the scrollkeeper.sourceforge.net site reports that
    SourceForge is undergoing maintenance or is temporarily unavailable.  I
    have seen this occur on 3 separate occasions in the last 4 weeks since I
    started experimenting with GitLab CI, which is rather too often.
    
    Xmllint comes from the GNOME 2 gnome-doc-utils.make rules used to build
    and validate GNOME 2 documentation.
    
    Fragment of useful Debian bug report 730688:
        https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730688
        --disable-scrollkeeper requieres scrollkeeper installed
    
        "You can reproduce the problem in mdbtoools version 0.7.1-1 with no
        network, and rarian-compat not installed.
    
        When the network is available, buildd downloads the DTD for checks.
        When there is no network, gnome-doc-utils fails.
        "
    
    Fix by:
    (1) adding the rarian-compat package to the CI Docker images, which
        provides a local copy of the scrollkeeper-omf.dtd file;
    (2) adding the xmllint --nonet option to prevent fetching of DTDs
        remotely.
    
    With reference to earlier commit:
        0eb9f1fcfb2a438ecd85ad7e526f0ec3d01e2da6
        Reduce dependency on scrollkeeper (#743318)
    That commit allowed GParted to be installed on GNOME 3 desktops without
    requiring rarian-compat package to be installed.  This commit adds
    rarian-compat to the CI images so that 'make check' can succeed without
    accessing the Internet.  Just the intricate path to continue to build
    and test a GNOME 2 application in a world of GNOME 3 desktops with
    beginning to be reduced backward compatibility.
    
    Closes #9 - CI test jobs occasionally fail with xmllint not loading
                external entity http://scrollkeeper.sourceforce.net/dtds/
                scrollkeeper-omf-1.0/scrollkeeper-omf.dtd

2018-07-06  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Stop parallelising make distcheck in GitLab CI test jobs (!6)
    
    Unfortunately parallelising 'make distcheck' causes it to fail like
    this:
    
        $ nproc=`grep -c '^processor' /proc/cpuinfo` || nproc=1
        $ echo nproc=$nproc
        nproc=8
        ...
        $ make -j $nproc distcheck
        ...
        make[1]: Entering directory '/builds/mfleetwo/gparted/gparted-0.31.0-git/_build/sub'
        ERROR: files left after uninstall:
        ./share/icons/hicolor/icon-theme.cache
        Makefile:896: recipe for target 'distuninstallcheck' failed
        make[1]: Leaving directory '/builds/mfleetwo/gparted/gparted-0.31.0-git/_build/sub'
        make[1]: *** [distuninstallcheck] Error 1
        make: *** [distcheck] Error 1
        Makefile:840: recipe for target 'distcheck' failed
        ERROR: Job failed: exit code 1
    
    Therefore go back to serial 'make distcheck'.
    
    Closes !6 - Reduce the time taken by the GitLab CI jobs

2018-07-06  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Parallelise building GParted in GitLab CI jobs (!6)
    
    Reduce the time taken by the GitLab Continuous Integration jobs by
    parallelising make to use all available CPUs in the Docker CI image
    when it is building GParted code.  This includes 'make diskcheck'
    because that also does a second build of the GParted code in a separate
    subdirectory.
    
    Closes !6 - Reduce the time taken by the GitLab CI jobs

2018-06-19  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Move enum CUSTOM_TEXT into FileSystem.h
    
    The CUSTOM_TEXT enumeration is exclusively used as the type of one of
    the parameters to the functions get_generic_text() and get_custom_text()
    in the FileSystem class and derived classes.  The definition of the
    enumeration therefore belongs in FileSystem.h.  Move it.

2018-06-13  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Set FSType when constructing FS in luks::get_filesystem_support()
    
    This is functionally identical, but is just to follow established coding
    pattern [1] of specifying the FSType when constructing struct FS, rather
    and setting it afterwards.  luks.cc was added after the aforementioned
    commit, but was being developed in parallel so was created [2] following
    the old coding pattern.
    
    [1] 1a4cefb9601de47a1d4fdd31d60be9e37fadda2d
        Initialise all struct FS members
    
    [2] 070d734e57e8c10cfc4264b34e8bd95bba7cf3ff
        Add busy detection of LUKS mapping (#760080)

2018-07-17  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Recognise additional GRUB2 core.img signatures (!5)
    
    Bootinfoscript v0.77 (2018-06-10) added additional signatures to
    recognise GRUB2 core.img by.  Commit:
    
        https://github.com/arvidjaar/bootinfoscript/commit/9a00c1a8877c9693ef908211f3dfd264c6172986
        Add more core.img diskboot signatures
    
    Specifically the new signatures are:
        5256be63 - trustedgrub2 1.4
        5256be56 - diskboot.S with mjg TPM patches (e.g. in openSUSE
                   Tumbleweed)
    
    Add those signatures into GParted.
    
    Closes !5 - Recognise additional GRUB2 core.img signatures

2018-06-24  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Add CI job to test GParted on Ubuntu (!4)
    
    Closes !4 - Add GitLab CI jobs to build and test GParted

2018-06-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Add CI job to build GParted on Ubuntu (!4)
    
    Closes !4 - Add GitLab CI jobs to build and test GParted

2018-06-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Parameterise CI config ready for also using a Ubuntu image (!4)
    
    Prepare the GitLab Continuous Integration configuration for also
    building and testing GParted on a Ubuntu image.  The definition of the
    image and before_script, which so far specify the CentOS Docker image
    and how to install the required RPM packages, need to move from being
    top level nodes to being defined per job.  Namely within jobs
    'centos_build' and 'centos_test'.
    
    To avoid duplicating various nodes within multiple jobs, YAML anchors
    (&LABEL) and references (*LABEL) are used.  They are defined in ignored
    jobs, job names starting with a dot (.).
    
    Closes !4 - Add GitLab CI jobs to build and test GParted

2018-06-22  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Rename CI jobs to reflect that they use a CentOS Docker image (!4)
    
    Ready for adding additional Continuous Integration jobs using different
    distribution Docker images.  Rename thus:
        build -> centos_build
        test  -> centos_test
    
    Closes !4 - Add GitLab CI jobs to build and test GParted

2018-06-22  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Exclude unit test which fails in Docker CI image (!4)
    
    Fragment of the tests/test-suite.log from the Docker CI image showing
    details of the unit test failure:
    
        Running main() from gtest_main.cc
        [==========] Running 26 tests from 1 test case.
        [----------] Global test environment set-up.
        [----------] 26 tests from BlockSpecialTest
        ...
        [ RUN      ] BlockSpecialTest.NamedBlockSpecialObjectBySymlinkMatches
        test_BlockSpecial.cc:137: Failure
        Failed
        get_link_name(): Failed to open directory '/dev/disk/by-id'
        test_BlockSpecial.cc:168: Failure
        Failed
        follow_link_name(): Failed to resolve symbolic link ''
        test_BlockSpecial.cc:255: Failure
        Expected: (lnk.m_name.c_str()) != (bs.m_name.c_str()), actual: "" vs ""
        [  FAILED  ] BlockSpecialTest.NamedBlockSpecialObjectBySymlinkMatches (0 ms)
        ...
        [==========] 26 tests from 1 test case ran. (1 ms total)
        [  PASSED  ] 25 tests.
        [  FAILED  ] 1 test, listed below:
        [  FAILED  ] BlockSpecialTest.NamedBlockSpecialObjectBySymlinkMatches
    
         1 FAILED TEST
    
    So the code is trying to find a symbolic link to a block device to use
    in the test.  It is trying to read the directory /dev/disk/by-id to find
    a symbolic link, but the directory doesn't exist in the Docker CI image.
    
    The used directory was recently changed [1] to use one which existed on
    all distributions.  Docker images don't even have the /dev/disk
    directory.  Exclude just this specific test.
    
    [1] 7fe41480749c795dfb79daeba7b058cece2dfdd2
        Use /dev/disk/by-id/ to get device symlink in test_BlockSpecial
    
    Closes !4 - Add GitLab CI jobs to build and test GParted

2018-06-22  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Debug unit test failure in CI test job (!4)
    
    Recursively list all the files below /dev as part of the 'test' job as
    certain block device names are needed by the failing test_BlockSpecial
    unit test.
    
    The artifact captures all the files from the directory in which the CI
    script runs to build and test GParted.  It creates a ZIP file which can
    be downloaded after the job finishes, whether the job succeeds of fails.
    This is to capture logs from the failure of the test_BlockSpecial unit
    test.
    
    Closes !4 - Add GitLab CI jobs to build and test GParted

2018-06-22  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Add CI testing job on CentOS (!4)
    
    Add GitLab Continuous Integration job named 'test' which runs the
    GParted unit tests and distcheck.  Note that the job starts from a fresh
    official CentOS Docker image so also has to rebuild GParted too.
    
    So far this job fails on unit test test_BlockSpecial.  Fragment of the
    CI job log:
    
        make  check-TESTS
        make[2]: Entering directory `/builds/mfleetwo/gparted/tests'
        make[3]: Entering directory `/builds/mfleetwo/gparted/tests'
        PASS: test_dummy
        FAIL: test_BlockSpecial
        PASS: test_PasswordRAMStore
        PASS: test_PipeCapture
        make[4]: Entering directory `/builds/mfleetwo/gparted/tests'
        make[4]: Nothing to be done for `all'.
        make[4]: Leaving directory `/builds/mfleetwo/gparted/tests'
        ============================================================================
        Testsuite summary for gparted 0.31.0-git
        ============================================================================
        # TOTAL: 4
        # PASS:  3
        # SKIP:  0
        # XFAIL: 0
        # FAIL:  1
        # XPASS: 0
        # ERROR: 0
        ============================================================================
        See tests/test-suite.log
        Please report to https://bugzilla.gnome.org/enter_bug.cgi?product=gparted
        ============================================================================
    
    Closes !4 - Add GitLab CI jobs to build and test GParted

2018-06-22  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Create initial GitLab CI job which builds on CentOS (!4)
    
    Initial GitLab Continuous Integration configuration with a single job
    named 'build' which just confirms GParted can be built and installed on
    the latest official CentOS Docker image.
    
    Closes !4 - Add GitLab CI jobs to build and test GParted

2018-07-02  Jordi Mas <jmas@softcatala.org>

    Update Catalan translation

2017-10-09  Jordi Mas <jmas@softcatala.org>

    Fixes to Catalan translation

2018-06-10  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Remove support for obsolete devkit-disks automount inhibitor
    
    Back in 2009 devicekit-disks package was renamed to udisks [1].  All
    supported distributions use udisks (or more recently udisks2).  None
    have the old devkit-disks command.  Therefore remove it from the GParted
    shell wrapper.
    
    [1] https://www.freedesktop.org/wiki/Software/DeviceKit-disks/
        "Note
        On December 1st 2009, DeviceKit-disks was renamed to udisks. This
        release is expected to appear in distributions released in the first
        half of 2010."

2018-06-22  Daniel Mustieles <daniel.mustieles.contractor@bbva.com>

    Updated Spanish translation

2018-06-11  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Fix LVM2 PV shrinking with lvm2 2.02.171 and later (#1)
    
    Shrinking an LVM2 Physical Volume on CentOS 7 with the latest
    lvm2 2.02.177 fails like this:
    
      Shrink /dev/sda9 from 1.00 GiB to 768.00 MiB
      * calibrate /dev/sda9
      * check file system on /dev/sda9 for errors and (if possib...(SUCCESS)
      * shrink file system                                         (ERROR)
        * lvm pvresize -v --setphysicalvolumesize 786432K '/dev/...(ERROR)
            0 physical volume(s) resized / 1 physical volume(s) not resized
    
            Wiping internal VG cache
            Wiping cache of LVM-capable devices
            /dev/sda9: Requested size 712.00 MiB is less than real size 1.00 GiB.  Proceed? [y/n]:[n]
            Physical Volume /dev/sda9 not resized.
    
    This upstream change to lvm2 [1] makes pvresize prompt for confirmation
    whenever the --setphysicalvolumesize option is used.  (The change was
    included in lvm2 2.02.171 and later, which is used in recent
    distributions.  The reporter found the issue on Ubuntu 18.04 LTS and I
    reproduced the issue on RHEL/CentOS 7.5).  The set size option has to be
    used when shrinking the PV before shrinking the partition therefore fix
    this issue by adding lvm common option --yes when using the set size
    option.
    
    [1] https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=cbc69f8c693edf0d1307c9447e2e66d07a04bfe9
        pvresize: Prompt when non-default size supplied.
    
    Closes #1 - Can't shrink LVM partition due to pvresize prompt

2018-05-26  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Clear previous LUKS unlock failure error before next attempt (#795617)
    
    After a failed LUKS unlock attempt the password entry dialog shows the
    error "Failed to open LUKS encryption".  Improve the user experience by
    clearing that error message at the start of the next attempt to avoid
    contradictory information with the main windows status of "Opening
    encryption on $PARTITION" whilst performing the next unlock attempt.
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2018-05-25  Mike Fleetwood <mike.fleetwood@googlemail.com>

    After LUKS unlock failure select failed password (#795617)
    
    When the wrong LUKS password is entered and the [Unlock] button clicked,
    the wrong password is left in the entry box and focus remains on the
    [Unlocked] button.  Improve the user experience by selecting
    (highlighting) the whole of the wrong password ready for deletion or
    retyping and ensuring that the entry box always has focus.
    
    Just for completeness also programmatically make the password entry box
    have focus when the dialog box is created and first displayed, even
    though it gets this by default.
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2018-06-19  Piotr Drąg <piotrdrag@gmail.com>

    Avoid unnecessary string change
    
    Restore whitespace to previous version,
    so no translations need to be updated.

2018-05-27  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Increment GParted Manual version

2018-05-27  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update SystemRescueCd URL in the GParted Manual
    
    http://www.sysresccd.org redirects to http://www.system-rescue-cd.org.
    Update the GParted Manual to the new address.

2018-05-27  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update URLs in the remaining files to https://gparted.org (#796411)
    
    Update URLs in the README file, man page, metadata files and polkit
    action file.
    
    Bug 796411 - Enhancements request - URL links

2018-05-27  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update URLs in the app to https://gparted.org (#796411)
    
    We previously migrated our web site from http://gparted.org to
    https://gparted.org under:
        bug 786707 - gparted.org does not use HTTPS
    
    and updated URLs in the GParted Manual to match in commit:
        a8172ecb04afabd636e3ad3d6f6665af894516f1
        Convert Manual links to HTTPS where possible and update version
    
    Now update the URLs displayed in the GParted application too.
    
    Bug 796411 - Enhancements request - URL links

2018-05-21  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Rework scope of fat16:: and ntfs::Change_UUID_Warning vectors
    
    The Change_UUID_Warning vectors were fat16 and ntfs class member
    variables, but are only ever accessed in the get_custom_text() method.
    Make them local variables in get_custom_text() instead.  Static so that
    references to them can be returned.

2018-05-19  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Move the xfs_db -r flag to the start when reading XFS usage
    
    I completely missed that when reading XFS file system size and usage it
    was using the '-r' read-only flag to xfs_db because it was at the end of
    the string on the following line of code.  Move it to the start of the
    xfs_db command line, like it is when reading the file system label.

2018-05-16  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Simplify from Gtk::Table to HBox in Partition Name dialog
    
    Same case as for FileSystem Label dialog before; the Partition Name
    dialog only has a single line of just 2 widgets.  Therefore switch to a
    simpler horizontal box widget to lay them out.

2018-05-15  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Simplify from Gtk::Table to HBox in FileSystem Label dialog
    
    The FileSystem Label dialog only has a single line of just 2 widgets; a
    text label and entry box widget.  There is no need to use a multi-line
    capable table to hold this.  Switch to a simpler horizontal box widget.
    
    Note that this change is not related to porting to Gtk 3 and stopping
    using deprecated APIs because both HBox [1] and Table [2] are deprecated
    in Gtk 3.2 and Gtk 3.4 and replaced by Box with horizontal orientation
    and Grid respectively.
    
    [1] NEWS file from gtkmm 3.2, actually first released in gtkmm 3.1.6
        (unstable):
        https://git.gnome.org/browse/gtkmm/tree/NEWS?h=3.2.0#n91
            "Gtk:
            * All H* or V* specialized classes have been deprecated, to
              match the deprecations in the GTK+ C API. You should now
              set the orientation instead.
              This includes HBox, VBox, HButtonBox, VButtonBox, HPaned,
              VPaned, HScale, VScale,  HSeparator, VSeparator, HScrollbar
              and VScrollbar."
    
    [2] NEWS file from gtkmm 3.4, actually first released in gtkmm 3.3.2
        (unstable):
        https://git.gnome.org/browse/gtkmm/tree/NEWS?h=3.4.0#n162
            "* Deprecate Gtk::Table in favour of Gtk::Grid."

2018-01-30  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Make get_custom_text() and get_generic_text() return by reference
    
    Replace return by value of const strings from
    FileSystem::get_custom_text() and get_generic_text() because that
    implies duplication of those strings.  Return a reference to constant
    strings instead.

2018-05-18  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Recognise blkid identified BitLocker encrypted partitions (#795127)
    
    Future util-linux release after v2.32 will include this commit for blkid
    to recognise BitLocker encrypted partitions.  It is much better than
    GParted's inbuilt detection.
    
        https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=136f89ce5ed8cd159a1c56b5a775dada2363ecd3
        libblkid: add BitLocker detection
    
    Make GParted also recognise BitLocker encrypted partitions reported by
    blkid.
    
    Bug #795127 - Displayed Name is incorrect for bitlocker encrypted
                  partitions

2018-06-13  Curtis Gedak <gedakc@gmail.com>

    Add Mike Fleetwood as GParted maintainer

2018-05-25  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Add logo.png for automatic GitLab/GitHub project avatar
    
    Generated from GParted SVG icon using:
        rsvg -w 256 -h 256 data/icons/hicolor_apps_scalable_gparted.svg logo.png

2018-05-21  Robert Ancell <robert.ancell@canonical.com>

    Fix null pointer check accidentally disabled (#796293)
    
    Compiling (with new enough g++) produces this warning:
    
        PasswordRAMStore.cc: In member function 'void GParted::PWStore::erase_all()':
        PasswordRAMStore.cc:177:2: warning: this 'if' clause does not guard... [-Wmisleading-indentation]
          if ( protected_mem != NULL );
          ^~
        PasswordRAMStore.cc:193:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if'
           memset( protected_mem, '\0', ProtectedMemSize );
           ^~~~~~
    
    Looks like a stray semicolon...
    
    Bug 796293 - Fix null pointer check accidentally disabled

2018-05-06  Piotr Drąg <piotrdrag@gmail.com>

    Update Polish translation

2018-05-02  Rafael Fontenelle <rafaelff@gnome.org>

    Update Brazilian Portuguese translation

2018-04-30  Marek Černocký <marek@manet.cz>

    Updated Czech translation

2018-04-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Change to insert or replace PasswordRAMStore::store() interface (#795617)
    
    Replace the insert() method (which reports an error when inserting a
    password with a key which already exists) with the store() method which
    replaces or inserts the password depending on whether the key already
    exists or not respectively.  There is also an optimisation that nothing
    is changed if the password to be replaced is the same as the one already
    stored.  The code in Win_GParted::open_encrypted_partition() is
    simplified now it doesn't have to implement this pattern of behaviour
    itself.
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2018-03-26  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Report LUKS unlock errors into the password dialog (#795617)
    
    Reports generic GParted error "Failed to open LUKS encryption" on any
    failure unlocking the partition.  Choosing not to display cryptsetup
    reported errors because those messages and their translations are not
    under GParted control.
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2018-03-22  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Stop copying password into insecure memory when getting entry (#795617)
    
    The underlying C coded Gtk Entry widget is careful to zero memory after
    use, allowing the widget to be safely used for password entry [1].
    However the C++ method Gtk::Entry::get_text() just takes the underlying
    C string from the Gtk Entry widget and copies it when constructing a
    Glib::ustring for the return value [2].
    
    So directly use the Gtk/C API to get the C string instead.
    
    [1] https://git.gnome.org/browse/gtk+/tree/gtk/gtkentrybuffer.c?h=3.22.28#n92
        See function trash_area() which zeros memory and its use in
        gtk_entry_buffer_normal_insert_text(),
        gtk_entry_buffer_normal_delete_text() and
        gtk_entry_buffer_finalize().
    
    [2] https://git.gnome.org/browse/gtkmm/tree/gtk/src/entry.hg?h=3.22.2#n104
        _WRAP_METHOD(Glib::ustring get_text() const, gtk_entry_get_text)
    
        https://git.gnome.org/browse/glibmm/tree/docs/internal/using_gmmproc.txt?h=2.46.1#n53
        _WRAP_METHOD(Glib::ustring METHOD const, FUNC) is processed to:
            Glib::ustring METHOD() const
            {
                return Glib::convert_const_gchar_ptr_to_ustring(
                    FUNC(const_cast<GtkEntry*>(gobj())));
            }
    
        https://git.gnome.org/browse/glibmm/tree/glib/glibmm/utility.h?h=2.46.1#n82
            Glib::ustring convert_const_gchar_ptr_to_ustring(const char* str)
            {
                return (str) ? Glib::ustring(str) : Glib::ustring();
            }
    
        So Gtk::Entry::get_text() calls Glib::ustring() constructor which
        copies the C string to create the Glib::ustring object returned.
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2018-02-11  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Keep password dialog open until successful unlock or cancellation (#795617)
    
    To keep password dialog open, just keep running it in a loop performing
    LUKS mapping unlock attempts with the entered passphrase until it
    succeeds or the dialog is cancelled or closed.  This is the same model
    that is already used for the File Support System dialog and how the
    [Rescan For Supported Actions] button is implemented.
    
    Also any error from attempting to open the LUKS mapping is no longer
    displayed in a separate error dialog or at all.  Will add some sort of
    error reporting into the password entry dialog in a following commit.
    
    Creates new method Win_GParted::open_encrypted_partition() which handles
    the non UI parts of attempting to open an encrypted partition.  Running
    "cryptsetup luksOpen" and updating the stored passphrase as needed.
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2017-10-22  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Add password entry dialog and attempt LUKS unlock once (#795617)
    
    Initial addition of a password entry dialog.  Looks like:
    
        +------------------------------------------------+
        |           LUKS Passphrase /dev/sdb1            |
        +------------------------------------------------+
        | Enter LUKS passphrase to open /dev/sdb1        |
        | Passphrase:    [                             ] |
        |                                                |
        |                          [ Cancel ] [ Unlock ] |
        +------------------------------------------------+
    
    A standard Gtk Dialog is used to accept the password once, with any
    errors displayed in a separate error dialog afterwards.  This is poor UI
    design.  A password dialog should remain open for all authentication
    attempts and only close when successful or the dialog is cancelled or
    closed.  This UI design issue will be improved in following commits.
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2017-10-18  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Add closing LUKS mappings (#795617)
    
    Implement Close Encryption partition menu item.
    
    The Open Encryption action is not yet implemented and instead reports an
    error detailing the open encryption command.  A dialog needs to be
    written to accept the password entry and pass it to the open encryption
    command.
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2016-10-25  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Add unimplemented open/close encryption to the partition menu (#795617)
    
    Add new item to the partition menu to allow the user to open and close
    the LUKS mapping.  However for now the menu item is always disabled and
    there is no implementation behind it to actually open or close the LUKS
    mapping.  Fragment of the partition menu is now:
    
        ...
        Format to       >
        -----------------
        Open Encryption      <- New menu item
        Mount
        -----------------
        Name Partition
        ...
    
    Has to be two separate menu items to clearly represent to the user that
    LUKS mappings and file system mounting are two separate busy states.
    And also in the case of an open but unmounted file system to offer both
    actions; close encryption and mount file system.
    
    The text of the menu item automatically changes similarly to how it does
    for the Mount/Unmount, Swapon/Swapoff, Activate/Deactivate item
    depending on the state of the LUKS mapping.  For open LUKS mappings it
    will show "Close Encryption" and for all other cases (closed LUKS
    mapping or partition is not encrypted) "Open Encryption".  Again similar
    to how the default of "Mount" is shown for unallocated and unknown
    partitions.
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2016-10-25  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Rename some Win_GParted members to *toggle_fs_busy* (#795617)
    
    In preparation for adding the ability to toggle the encryption busy
    state (open/close the encryption volume), rename existing members to
    reflect that they are related to changing the file system state.  (Swap
    and LVM2 Physical Volumes are handled as file systems by GParted).
    
    class Win_GParted renaming:
        MENU_TOGGLE_BUSY             -> MENU_TOGGLE_FS_BUSY
        allow_toggle_busy_state()    -> allow_toggle_fs_busy_state()
        toggle_busy_state()          -> toggle_fs_busy_state()
        check_toggle_busy_allowed()  -> check_toggle_fs_busy_allowed()
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2017-10-20  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Stop using shell when reading jfs file system usage (#795617)
    
    Replace echoing "dm" into jfs_debugfs via a shell command to directly
    writing "dm" to the input of the jfs_debug command.  One less use of the
    shell.
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2017-10-20  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Add ability for small writes to stdin of child processes (#795617)
    
    As discussed in "LUKS password handling, threats and preventative
    measures" [1] GParted must be able to pass LUKS passphrases to
    cryptsetup via standard input to avoid having to write passwords to the
    file system and deal with additional security requirements.  Therefore
    add a way to write input into created child processes.  For small
    amounts of input, writing up to the pipe buffer capacity won't block
    [2].  This is 64K on versions of Linux in any currently supported
    distributions.
    
    [1] LUKS password handling, threats and preventative measures
        https://bugzilla.gnome.org/show_bug.cgi?id=627701#c56
    
        GParted must not become a password manage so it must never save
        LUKS passwords to disk across separate invocations of GParted.
        ...
    
        GParted should avoid writing a temporary file containing the LUKS
        password as it introduces extra complexity with trying to safely
        handle and erase file content.  Instead GParted must
        programmatically pass the LUKS password via standard input to the
        cryptsetup command.
    
    [2] pipe(7) manual page:
    
        Pipe capacity
            A pipe has a limited capacity.  If the pipe is full, then a
            write(2) will block or fail, depending on whether the O_NONBLOCK
            flag is set (see below).  ...
    
            In Linux versions before 2.6.11, the capacity of a pipe was the
            same as the system page size (e.g., 4096 bytes on i386).  Since
            Linux 2.6.11, the pipe capacity is 65536 bytes.
    
    Bug 795617 - Implement opening and closing of LUKS mappings

2017-11-10  Mike Fleetwood <mike.fleetwood@googlemail.com>

