Bug 503148

Summary: KDE Partition Manager crash on start
Product: [Applications] partitionmanager Reporter: Steve Cossette <farchord>
Component: generalAssignee: Andrius Štikonas <andrius>
Status: RESOLVED DUPLICATE    
Severity: crash CC: agurenko, d3niskh, derekenz, piedro.kulman
Priority: NOR Keywords: drkonqi
Version First Reported In: 25.04.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/165340/events/1885fd9415b147ad9b4bce39d25334a7/
Attachments: New crash information added by DrKonqi

Description Steve Cossette 2025-04-22 01:25:20 UTC 
Application: partitionmanager (25.04.0)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.0
Frameworks Version: 6.13.0
Operating System: Linux 6.14.2-300.fc42.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 42 (KDE Plasma Desktop Edition)"
DrKonqi: 6.3.4 [CoredumpBackend]

-- Information about the crash:
Everytime I start KDE Partition Manager, it just hard-crashes after I enter the admin password.

Gparted is working just fine.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  0x00007f51749a0cc7 in SfdiskBackend::readSectorsUsed (d=..., p=..., mountPoint=...) at /usr/src/debug/kpmcore-25.04.0-1.fc42.x86_64/src/plugins/sfdisk/sfdiskbackend.cpp:523
#6  0x00007f51749a0f0f in SfdiskBackend::scanWholeDevicePartition (this=this@entry=0x55f2f09fd650, d=...) at /usr/src/debug/kpmcore-25.04.0-1.fc42.x86_64/src/plugins/sfdisk/sfdiskbackend.cpp:345
#7  0x00007f51749a89bf in SfdiskBackend::scanDevice (this=0x55f2f09fd650, deviceNode=...) at /usr/src/debug/kpmcore-25.04.0-1.fc42.x86_64/src/plugins/sfdisk/sfdiskbackend.cpp:297
#8  0x00007f51749a7077 in SfdiskBackend::scanDevices (this=0x55f2f09fd650, scanFlags=...) at /usr/src/debug/kpmcore-25.04.0-1.fc42.x86_64/src/plugins/sfdisk/sfdiskbackend.cpp:106
#9  0x00007f518e5e432b in DeviceScanner::scan (this=0x55f2f0a05e90) at /usr/src/debug/kpmcore-25.04.0-1.fc42.x86_64/src/core/devicescanner.cpp:56


Reported using DrKonqi
Comment 1 Steve Cossette 2025-04-22 01:25:21 UTC 
Created attachment 180506 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Steve Cossette 2025-04-22 12:38:50 UTC 
So I did some work yesterday to rule things out related to this bug:

1- I originally had 2 USB devices plugged in to my laptop when this first happened: My Sandisk USB Thumb Drive, and a Samsung T5 SSD (1TB). 

2- I unplugged both drives and restarted KDE Partition Manager. Everything works fine, app starts normally.

3- I plugged in my Sandisk Thumb drive and restarted again. Same thing: Seems to work just fine. Starts without crashing.

4- I unplugged my Sandisk thumb drive and plugged the Samsung T5 SSD and restarted. Crash.

At first, I thought, "Okay, maybe it's a bit somewhere on that SSD that's not liked by kpmcore?", but this morning, on my other computer (desktop) where I have another Samsung T7 SSD (2TB in this case), and KDE Partition Manager also crashes on start.

Is there maybe something in those drives that's tripping kpmcore?
Comment 3 Bug Janitor Service 2025-04-22 12:41:15 UTC 
A possibly relevant merge request was started @ https://invent.kde.org/system/kpmcore/-/merge_requests/63
Comment 4 xniksysx 2025-04-22 12:44:11 UTC 
Yes i have same things. Partitionmanager crash on USB external HDD disk. Latest Arch Linux updates.
In console last line with error:

unknown file system type  "dos"  on  "/dev/sdd"
KCrash: Application 'partitionmanager' crashing... crashRecursionCounter = 2
Comment 5 Antonio Rojas 2025-04-22 14:48:18 UTC 
*** Bug 503171 has been marked as a duplicate of this bug. ***
Comment 6 Andrius Štikonas 2025-04-24 11:42:01 UTC 

*** This bug has been marked as a duplicate of bug 502141 ***