| Summary: | PartitionManager crashes on start when a factory new hard drive is attached to computer | ||
|---|---|---|---|
| Product: | [Applications] partitionmanager | Reporter: | Michael <kde> |
| Component: | general | Assignee: | Andrius Štikonas <andrius> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | 25.04.0 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | screenshot of interface while hanging | ||
*** This bug has been marked as a duplicate of bug 502141 *** |
Created attachment 180718 [details] screenshot of interface while hanging SUMMARY I unboxed a new Seagate 8TB hard drive, attached it via a powered SATA->USB bridge, tried to run Partition Manager, but would crash. So I ran PM from the command line and it was crashing while scanning for the /dev/sdb device, which is the new Seagate drive: $ partitionmanager Loaded backend plugin: "pmsfdiskbackendplugin" "Using backend plugin: pmsfdiskbackendplugin (1)" "Scanning devices..." "Device found: SOLIDIGM SSDPFKNU010TZ" getting temp failed for "/dev/nvme0n1" : No such file or directory getting powered on time failed for "/dev/nvme0n1" : No such file or directory getting power cycles failed for "/dev/nvme0n1" : No such file or directory "Device found: HFM512GD3JX013N" getting temp failed for "/dev/nvme1n1" : No such file or directory getting powered on time failed for "/dev/nvme1n1" : No such file or directory getting power cycles failed for "/dev/nvme1n1" : No such file or directory unknown file system type "" on "/dev/nvme1n1p2" 166399 21111 4096 5767167 2369036 4096 "Device found: ST4000DM004-2U9104" "Device found: ST8000DM004-2U9188" getting powered on time failed for "/dev/sdb" : No such file or directory unknown file system type "" on "/dev/sdb" KCrash: Application 'partitionmanager' crashing... crashRecursionCounter = 2 fish: Job 1, 'partitionmanager' terminated by signal SIGSEGV (Address boundary error) I've also attached a screenshot of the interface as it was hung up scanning and just before it crashed. I suspected that PM didn't like that it was a raw disk, so I ran fdisk to verify that it could see the disk, it could: $ sudo fdisk -l ... Disk /dev/sdb: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: 004-2U9188 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes ... Acting on a hunch, I found the solution was to tell fdisk to give the disk a GPT partition table. Then I re-ran PM and it did not crash. I was able to select the unformatted disk and format it just fine. STEPS TO REPRODUCE 1. attach a factory fresh hard drive to your computer 2. run PM OBSERVED RESULT it crashes on initial scan EXPECTED RESULT shouldn't crash SOFTWARE/OS VERSIONS Operating System: KDE neon 6.3 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.8.3 Kernel Version: 6.11.0-24-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor 1: AMD Radeon 680M Graphics Processor 2: NVIDIA GeForce RTX 3050 Ti Laptop GPU Manufacturer: ASUSTeK COMPUTER INC.