KDE Partition Manager reports partition not properly aligned?

Partition manager is reporting misaligned partitions (Log Output pasted below), but before fixing it, I want to confirm it is my doing/ignorance and not a bug.

Using Partition Manager version 24.08.2 in a Wayland session of KDE 6.2.1 on KF 6.7.0 of Arch 6.11.3-arch1-1 (64-bit). The drive is a Crucial T705 (CT1000T705SSD5) in a PCIe x5.0 m.2 slot as /dev/nvme1n1.

Formatted the nvme lba to 1 (best). Using gdisk for gpt, p1 (Fat32 EFI) defaults with +1G on last sector, p2 (swap) defaults and +4G on last sector, p3 (btrfs linux root x86-64) all defaults. I did not set the sector alignment value in the expert options though it reports 256.

fdisk/gptfdisk is supposed to automatically handle partition alignment. Everything reports 4096 for physical/logical, the first sector starts at 1 MiB offset. Is this just something to ignore (maybe bug report?) or is it actually misaligned? Or am I just missing something?

parted align-check reports all 3 partitions are aligned for both minimal and optimal.

~$ sudo parted /dev/nvme1n1 align-check optimal 1
1 aligned
~$ sudo parted /dev/nvme1n1 align-check minimal 1
1 aligned
~$ sudo parted /dev/nvme1n1 align-check optimal 2
2 aligned
~$ sudo parted /dev/nvme1n1 align-check minimal 2
2 aligned
/home/rob $ sudo parted /dev/nvme1n1 align-check optimal 3
3 aligned
/home/rob $ sudo parted /dev/nvme1n1 align-check minimal 3
3 aligned

This is Partition Manager’s output log:

2024-10-27 15:07:34: Using backend plugin: pmsfdiskbackendplugin (1)
2024-10-27 15:07:34: Scanning devices...
2024-10-27 15:07:34: Device found: WDS500G3XHC-00SJG0
2024-10-27 15:07:34: Partition ‘/dev/nvme0n1p1’ is not properly aligned (first sector: 256, modulo: 256).
2024-10-27 15:07:34: Partition ‘/dev/nvme0n1p1’ is not properly aligned (last sector: 122,096,639, modulo: 1,024).
2024-10-27 15:07:34: Device found: CT1000T705SSD5
2024-10-27 15:07:34: Partition ‘/dev/nvme1n1p1’ is not properly aligned (first sector: 256, modulo: 256).
2024-10-27 15:07:34: Partition ‘/dev/nvme1n1p1’ is not properly aligned (last sector: 262,399, modulo: 256).
2024-10-27 15:07:34: Partition ‘/dev/nvme1n1p2’ is not properly aligned (first sector: 262,400, modulo: 256).
2024-10-27 15:07:34: Partition ‘/dev/nvme1n1p2’ is not properly aligned (last sector: 1,310,975, modulo: 256).
2024-10-27 15:07:34: Partition ‘/dev/nvme1n1p3’ is not properly aligned (first sector: 1,310,976, modulo: 256).
2024-10-27 15:07:34: Partition ‘/dev/nvme1n1p3’ is not properly aligned (last sector: 244,190,463, modulo: 1,280).
2024-10-27 15:07:34: Device found: Samsung SSD 870 EVO 1TB
2024-10-27 15:07:34: Device found: SanDisk 3.2Gen1
2024-10-27 15:07:34: Partition ‘/dev/sdb1’ is not properly aligned (last sector: 240,351,135, modulo: 1,952).
2024-10-27 15:07:34: Scan finished.
~$ nvme id-ns -H /dev/nvme1n1 | grep "Relative Performance"
LBA Format  0 : Metadata Size: 0   bytes - Data Size: 512 bytes - Relative Performance: 0x1 Better 
LBA Format  1 : Metadata Size: 0   bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use)
~$ lsblk -td
NAME    ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED       RQ-SIZE  RA WSAME
sda             0    512      0     512     512    0 mq-deadline      64 128    0B
sdb             0    512      0     512     512    1 mq-deadline       2 128    0B
nvme0n1         0   4096      0    4096    4096    0 none           1023 128    0B
nvme1n1         0   4096      0    4096    4096    0 none           1023 128    0B
~$ sudo smartctl -a /dev/nvme1n1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.11.3-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       CT1000T705SSD5
Serial Number:                      -
Firmware Version:                   PACR5111
PCI Vendor/Subsystem ID:            0xc0a9
IEEE OUI Identifier:                0x00a075
Controller ID:                      0
NVMe Version:                       2.0
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Formatted LBA Size:     4096
Namespace 1 IEEE EUI-64:            00a075 01e897824a
Local Time is:                      Sun Oct 27 16:27:45 2024 EDT
Firmware Updates (0x12):            1 Slot, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005e):     Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x3e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Log0_FISE_MI
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     87 Celsius
Critical Comp. Temp. Threshold:     89 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +    11.50W       -        -    0  0  0  0      800    1000
 1 +     8.00W       -        -    0  0  0  0      800    1000
 2 +     6.00W       -        -    0  0  0  0      800    1000
 3 -   0.1440W       -        -    0  0  0  0     3000    3000
 4 -   0.1440W       -        -    0  0  0  0     3000    3000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 -     512       0         1
 1 +    4096       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        47 Celsius
Available Spare:                    100%
Available Spare Threshold:          5%
Percentage Used:                    0%
Data Units Read:                    85,459,132 [43.7 TB]
Data Units Written:                 14,915,277 [7.63 TB]
Host Read Commands:                 832,806,459
Host Write Commands:                935,522,030
Controller Busy Time:               533
Power Cycles:                       104
Power On Hours:                     188
Unsafe Shutdowns:                   14
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Error Information (NVMe Log 0x01, 16 of 16 entries)
No Errors Logged

Read Self-test Log failed: Invalid Field in Command (0x002)
~$ fdisk -l
Disk /dev/nvme1n1: 931.51 GiB, 1000204886016 bytes, 244190646 sectors
Disk model: CT1000T705SSD5                          
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: EF91EB1B-7AE3-4486-8AE0-F270518CCC07

Device           Start       End   Sectors   Size Type
/dev/nvme1n1p1     256    262399    262144     1G EFI System
/dev/nvme1n1p2  262400   1310975   1048576     4G Linux swap
/dev/nvme1n1p3 1310976 244190463 242879488 926.5G Linux root (x86-64)
~$ sudo parted /dev/nvme1n1 unit b print
Model: CT1000T705SSD5 (nvme)
Disk /dev/nvme1n1: 1000204886016B
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start        End             Size           File system     Name                   Flags
 1      1048576B     1074790399B     1073741824B    fat32           EFI system partition   boot, esp
 2      1074790400B  5369757695B     4294967296B    linux-swap(v1)  Linux swap             swap
 3      5369757696B  1000204140543B  994834382848B  btrfs           Linux x86-64 root (/)

I saw the same thing on partition on a 4kiB sector size disk, but nothing on an identically aligned partition on a 512B sector size disk. As all other sources/tools indicate a 1MiB alignment is correct, I suspect partitionmanager to misinterpret the alignment.

I was doing some research about it while writing this originally and shortly after posting which led me to that conclusion was as well, but I was very unsure. Helps to have another person back that up, thank you.