I’m happy to announce new bugfix versions of KDE Partition Manager 2.0.1 and KPMcore 2.0.1.
- Btrfs used space detection should work without crashing (it was actually cause by crash in btrfs-debug-tree program btrfs filesystem show is used).
- Improved support for FAT12 partitions. They were not recognized before. For now they are reported as FAT16 (gparted behaves in the same way).
- Installation path for libparted plugins is not force to be in system prefix anymore. This is consistent with how other KDE Applications work, but cmake might require KDE_INSTALL_USE_QT_SYS_PATHS to be set if you are installing kpmcore to /usr.
- We know try to find KF5 version of kdesu in libexec even when kdesu is not in $PATH.
- Fixed visible HTML in one dialog box (#354925).
There is still an open issue that Partition Manager reports itself as 2.0.0 instead of 2.0.1. I tried to bump the version but there seem to be some kind of bug that prevents KDE Partition Manager and Calamares to compile or work. We will continue to investigate this issue but 2.0.1 should work well despite incorrectly reporting it’s own version
Edit: KDE Partition Manager 2.0.3 is now released to fix a crash in settings dialog (it can be used with KPMcore 2.0.x but please use the latest KPMcore 2.0.1).
I’m happy to announce KDE Partition Manager 2.0.0 and the first stable release of KPMcore. This release mostly focused on splitting user interface and partitioning library which will be used in the next release of Calamares. It also brings some bugfixes but unfortunately I wasn’t able to go through all reported bugs in bugzilla yet (but they don’t seem to be regressions).
I am happy to announce that upcoming release of KDE Partition Manager is split into library (KPMcore) and GUI parts to allow other projects reuse partitioning code. KPMcore is already used by the development versions of distribution independent installer Calamares whose maintainer Teo Mrnjavac contributed a lot to help get this release of KDE Partition Manager out.
In the meantime you can download and test alpha versions of KPMcore and KDE Partition Manager.
KPMcore library is also licensed under GNU GPLv3+ (it links to parted which is GPLv3+).
I would like to announce two releases of KDE Partition Manager. Version 1.1.1 is a bugfix release. It was ported away from Solid to avoid the unfortunate udisks2 bug and uses libparted directly (partitionmanager was using libparted already anyway). That means packagers do not have to select -DENABLE_UDISKS2 cmake option anymore.
Version 1.2.0 is a new feature release. It doesn’t have that many new features but the port to KDE Frameworks is complete.
Download links can be found in usual locations on download.kde.org:
In the next release there are some plans to separate core part of KDE Partition Manager and the GUI part, so that other projects like distribution-independent installer Calamares would be able to reuse Partition Manager code easier.
Edit: It looks like 1.2.0 version have a broken docs that adds unintentional dependency on kdelibs4support (bug #344256). I will try to release 1.2.1 soon that fixes this issue.
Edit: KDE Partition Manager 1.2.1 is now released. docs are fixed and don’t require kdelibs4support anymore. KDE_INSTALL_USE_QT_SYS_PATHS is also enabled by default.
The long awaited KDE Partition Manager 1.1.0 is now released. However, there are some sad news first. This release is dedicated to the memory of Volker Lanz who passed away this April. He was the main developer of KDE Partition Manager who wrote almost all of its code and maintained it for 5 years.
The most important changes in this release are support for Btrfs file system and GPT partition table. This release also adds support for exFAT, NILFS 2 and very basic support for ZFS, encrypted LUKS containers and LVM2 physical volumes. There are some nice GUI improvements as well, partition widget design was improved by Hugo Pereira Da Costa.
On the other hand, there are still missing features and bugs. It would be nice to have a better support for LUKS and LVM volumes. There is also a slightly annoying bug #311408 which prevents detection of disks without any partition table when Solid is used with udisks2 backend. It seems that udisks2 does not let you easily obtain a block device corresponding to a particular drive, so Solid backend has to guess it (usually incorrectly) and then partition manager fails to find any disks. I have implemented a workaround to look for partition tables instead of drives (then Partition Manager has to be compiled with -DENABLE_UDISKS2).
As you can see Partition Manager really needs a few more developers. Its code is less scary then it might seem. After all it is a GUI and most of low level stuff is done my external programs.
Port to KDE Frameworks 5 is also almost complete and will be released once all issues are fixed. There is still some unported code, e.g. at src/backend/corebackenmanager.cpp. If any KF5 porting experts know how to fix this it would be very appreciated.
KDE Partition Manager can be downloaded from http://download.kde.org/stable/partitionmanager/1.1.0/src/partitionmanager-1.1.0.tar.xz.mirrorlist
SHA256Sum: 30ac75f85bb61e6ec9b6f5d80dee4a2c8501a0a0c62997f6d734e63459802cc8 partitionmanager-1.1.0.tar.xz
SHA1Sum: 797964522d077ec9daae752bd2d40f1bd284d149 partitionmanager-1.1.0.tar.xz
MD5Sum: 4a752c250fc5c98e22aba1d2ea309bec partitionmanager-1.1.0.tar.xz
GPG signature can be found at https://stikonas.eu/files/partitionmanager-1.1.0.tar.xz.sig