[Pkg-kde-extras] Bug#760885: partitionmanager: HTML report produced for operations applied gives incorrect KDE version
Package: partitionmanager Version: 1.0.2-1 Severity: minor Dear Maintainer, This is a silly and (presumably) cosmetic bug: if you use KDE Partition Manager to make some changes to a hard drive, and then, when it has successfully completed, you click the 'Open in external browser' button (first clicking 'Details ' if necessary to show the 'Open ...' button) to cause an HTML report to be generated detailing the changes, the report shows the KDE Partition Manager version correctly (1.0.2), but reports the KDE version as '4.4.3', instead of the '4.8.4' that it actually is. This is despite KDE Partition Manager being fully aware elsewhere of the correct KDE version, as shown if you do 'Help | About', in which case the KDE version is shown correctly as 4.8.4. I have screenshots illustrating this bug, which I'll try to attach to the report. The bug is repeatable at will (on every run). There is no apparent adverse effect on the requested disk operation, so this is just a cosmetic bug, albeit a rather strange one. -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages partitionmanager depends on: ii kdebase-runtime4:4.8.4-2 ii libblkid1 2.20.1-5.3 ii libc6 2.13-38+deb7u3 ii libgcc11:4.7.2-5 ii libkdecore54:4.8.4-4+deb7u1 ii libkdeui5 4:4.8.4-4+deb7u1 ii libkio54:4.8.4-4+deb7u1 ii libparted0debian1 2.3-12 ii libqtcore4 4:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libstdc++6 4.7.2-5 ii libuuid1 2.20.1-5.3 partitionmanager recommends no packages. Versions of packages partitionmanager suggests: ii dosfstools 3.0.13-1 pn hfsplusnone pn hfsutils none pn jfsutils none pn ntfsprogs none pn reiser4progs none pn reiserfsprogs none pn xfsprogs none -- no debconf information More A quick look through the package source code shows the following code fragment in file src/util/report.cpp : s += tableLine(i18n(Date:), KGlobal::locale()-formatDateTime(KDateTime::currentLocalDateTime())); s += tableLine(i18n(Program version:), KGlobal::mainComponent().aboutData()-version()); s += tableLine(i18n(LibParted version:), ped_get_version()); s += tableLine(i18n(KDE version:), KDE_VERSION_STRING); but there are no other references to the variable KDE_VERSION_STRING anywhere in any of the source package files, and I'm not a KDE programmer so don't know whether this is a standard data item in a KDE development environment. FWIW, the system in which I experience this bug is a Wheezy VM, hosted by Virtualbox running on a Squeeze host - which of course is KDE 4.4.3 . ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#759610: Small correction (typo/braino)
Aaaargh ... when I wrote : bug 754580 filed against package pkg-kde-extras by Colin Watson that should have been filed against partitionmanager (I had altogether too many tabs open at the time). Also, it's worth noting that 754580 is marked closed/done, with comments that both an NMU of a (minimally, to support parted 3.1) tweaked 1.0.3 has been prepared (by Colin W), and that upstream 1.1.0 is being packaged (by a new maintainer). It's still unclear (to me) whether or not 1.1.0 addresses 4KiB sector partition alignment issues. Cheers Nick ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#759697: partitionmanager: HTML report produced after disk operation gives incorrect KDE version
Package: partitionmanager Version: 1.0.2-1 Severity: minor This is a silly and peculiar cosmetic bug: if you use KDE Partition Manager to make some changes to a hard drive, and then, when it has successfully completed, you view the operation report in HTML format by clicking the 'Open in external browser' button (first clicking 'Details ' if necessary to show the 'Open ...' button), the report shows the KDE Partition Manager version correctly (1.0.2), but reports the KDE version as '4.4.3', instead of the '4.8.4' that it actually is. This is despite KDE Partition Manager being fully aware elsewhere of the correct KDE version, as shown if you do 'Help | About', in which case the KDE version is correctly shown as 4.8.4. A quick look through the package source code shows the following code fragment in file src/util/report.cpp : s += tableLine(i18n(Date:), KGlobal::locale()-formatDateTime(KDateTime::currentLocalDateTime())); s += tableLine(i18n(Program version:), KGlobal::mainComponent().aboutData()-version()); s += tableLine(i18n(LibParted version:), ped_get_version()); s += tableLine(i18n(KDE version:), KDE_VERSION_STRING); but there are no other references to the variable KDE_VERSION_STRING anywhere in any of the source package files, and I'm not a KDE programmer so don't know whether this is a standard data item (external environment variable ?) in a KDE development environment. This bug is being reported against the Wheezy version of partitionmanager, but exactly the same fault is observed using the Squeeze version - perhaps unsurprising given that both Debian releases have the same partitionmanager version. Squeeze KDE is 4.4.5, and that in Wheezy is 4.8.4, so the reporting of KDE version 4.4.3 is mysterious - perhaps it was on the package maintainer's development workstation at the time the package was built, and has somehow become hard-coded ? There is no obvious adverse effect on the requested disk operation, so this is just a cosmetic bug, albeit a rather strange one. -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages partitionmanager depends on: ii kdebase-runtime4:4.8.4-2 ii libblkid1 2.20.1-5.3 ii libc6 2.13-38+deb7u3 ii libgcc11:4.7.2-5 ii libkdecore54:4.8.4-4+deb7u1 ii libkdeui5 4:4.8.4-4+deb7u1 ii libkio54:4.8.4-4+deb7u1 ii libparted0debian1 2.3-12 ii libqtcore4 4:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libstdc++6 4.7.2-5 ii libuuid1 2.20.1-5.3 partitionmanager recommends no packages. Versions of packages partitionmanager suggests: ii dosfstools 3.0.13-1 pn hfsplusnone pn hfsutils none pn jfsutils none pn ntfsprogs none pn reiser4progs none pn reiserfsprogs none pn xfsprogs none -- no debconf information -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages partitionmanager depends on: ii kdebase-runtime4:4.8.4-2 ii libblkid1 2.20.1-5.3 ii libc6 2.13-38+deb7u3 ii libgcc11:4.7.2-5 ii libkdecore54:4.8.4-4+deb7u1 ii libkdeui5 4:4.8.4-4+deb7u1 ii libkio54:4.8.4-4+deb7u1 ii libparted0debian1 2.3-12 ii libqtcore4 4:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libstdc++6 4.7.2-5 ii libuuid1 2.20.1-5.3 partitionmanager recommends no packages. Versions of packages partitionmanager suggests: ii dosfstools 3.0.13-1 pn hfsplusnone pn hfsutils none pn jfsutils none pn ntfsprogs none pn reiser4progs none pn reiserfsprogs none pn xfsprogs none -- no debconf information ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#759610: partitionmanager: partition alignment attribute missing from 'new partition' dialog
Package: partitionmanager Version: 1.0.2-1 Severity: important Tags: upstream KDE Partition Manager 1.0.2 lacks a feature which it seems is needed with modern large hard drives - specifically the ability to specify partition alignment when creating new partitions. More accurately, the feature is needed when creating partitions on drives with 4KB physical sectors but which still report a logical sector size of 512 bytes (so-called first-generation advanced format drives) which is a feature of most modern drives over about 1TB in size. On such drives, if a partition is created starting at a logical sector which is itself not at the beginning of a 4KB physical sector then disk transfers to/from such a partition may require 2 physical sectors to be transferred when 1 would have otherwise been sufficient, depending on filesystem cluster size, access pattern (sequential/random) and transfer direction (read/write), potentially resulting in serious performance problems. See [1] [2] [3] [4] [5]. The situation is complex, and I may not have understood it completely :-) It is compounded by an apparent difference of opinion among drive manufacturers as to whether sector numbering should begin at 0 (traditional) or 1 (easier for 4K-drive firmware ?) - see the LKML thread at [6]. At any rate the general advice seems to be that if partitions are aligned to MiB boundaries on advanced format drives then the performance problems will be avoided. This means the first partition on the drive will start at sector 2048, rather than the traditional sector 63 - which will be fine unless the drive needs to be shared (dual-booted) with a Windows=XP installation (in which case I haven't been able to figure out what is recommended). Since at least 2012, GParted has had a partition alignment widget (a dropdown) on the 'new partition' dialog, offering a choice of cylinder, MiB, or 'none' for the alignment attribute (I assume 'none' means logical sector alignment). Unless partitionmanager is somehow automagically detecting the need for 4KiB-style alignment and silently doing the Right Thing, then I suggest it needs enhancing to offer a similar alignment choice. I note there is a new upstream partitionmanager version 1.1.0, at a new homepage [7], where it is stated the changes include support for GPT partition tables, and some nice GUI improvements in the area of partition widget design (paraphrasing), but there are no screen shots, and I'm still attempting to understand the source code to see whether or not partition alignment issues are addressed. If the new version *does* address the problem then bug 754580 filed against package pkg-kde-extras by Colin Watson [8] (a request for version 1.1.0 to be packaged) will probably be sufficient for Jessie+ releases. [1] http://hothardware.com/Reviews/WDs-1TB-Caviar-Green-w-Advanced-Format-Windows-XP-Users-Pay-Attention/?page=2 [2] http://en.wikipedia.org/wiki/4_KB_sector_alignment#512e [3] http://johannes-bauer.com/linux/wdc/?menuid=3 [4] http://www.ibm.com/developerworks/library/l-4kb-sector-disks/ [5] https://ata.wiki.kernel.org/index.php/ATA_4_KiB_sector_issues [6] https://lkml.org/lkml/2009/2/25/444 [7] https://stikonas.eu/wordpress/?p=8 [8] https://bugs.debian.org/754580 Sorry for the length of this bug report - it seemed helpful to try to give a full statement of the problem. -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages partitionmanager depends on: ii kdebase-runtime4:4.8.4-2 ii libblkid1 2.20.1-5.3 ii libc6 2.13-38+deb7u3 ii libgcc11:4.7.2-5 ii libkdecore54:4.8.4-4+deb7u1 ii libkdeui5 4:4.8.4-4+deb7u1 ii libkio54:4.8.4-4+deb7u1 ii libparted0debian1 2.3-12 ii libqtcore4 4:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libstdc++6 4.7.2-5 ii libuuid1 2.20.1-5.3 partitionmanager recommends no packages. Versions of packages partitionmanager suggests: ii dosfstools 3.0.13-1 pn hfsplusnone pn hfsutils none pn jfsutils none pn ntfsprogs none pn reiser4progs none pn reiserfsprogs none pn xfsprogs none -- no debconf information ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#759610: Small correction (typo/braino)
Aaaargh ... when I wrote : bug 754580 filed against package pkg-kde-extras by Colin Watson that should have been filed against partitionmanager (I had altogether too many tabs open at the time). Also, it's worth noting that 754580 is marked closed/done, with comments that both an NMU of a (minimally, to support parted 3.1) tweaked 1.0.3 has been prepared (by Colin W), and that upstream 1.1.0 is being packaged (by a new maintainer). It's still unclear (to me) whether or not 1.1.0 addresses 4KiB sector partition alignment issues. Cheers Nick ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#759610: More info: warning from partitionmanager 1.0.2 on squeeze
I've just tried creating a test partition on the only advanced format hard drive I have, which is a new Toshiba DT01ACA200 attached to a system still running squeeze (but with the 3.2.0 kernel from backports), with partitionmanager 1.0.2-1 (identical functionality presumably to the wheezy version). Creating a partition leaving the free space before at its default value of 0MiB results in a partition that begins at sector 63. The HTML operation report produced at the end shows that ext4 filesystem creation produces the following warning: Command: mkfs.ext4 /dev/sdb1 mke2fs 1.41.12 (17-May-2010) /dev/sdb1 alignment is offset by 512 bytes. This may result in very poor performance, (re)-partitioning suggested. Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=1 blocks, Stripe width=0 blocks i.e. the partition is reported misaligned by 1 logical sector. If I repeat the test but specify a free space before of 1MiB, then the new partition begins at sector 16065 (see below), and filesystem creation reports : Command: mkfs.ext4 /dev/sdb1 mke2fs 1.41.12 (17-May-2010) /dev/sdb1 alignment is offset by 3584 bytes. This may result in very poor performance, (re)-partitioning suggested. Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=1 blocks, Stripe width=0 blocks i.e. the partition is reported misaligned by 7 logical sectors. The seemingly bizarre start sector 16065 would correspond in virtual (BIOS- style) CHS disk geometry to 255heads x 63sectors, i.e. 1 cylinder, so it's possible that partitionmanager has a further bug where it works in cylinders even when claiming to work in MiB :) It is not possible to use the free space before widget to enter a quantity in any unit other than MiB, so it appears impossible to create a properly aligned partition. Cheers, Nick ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
