Bug 503595 - KDE Partitionmanager crashes if an USB stick is plugged in
Summary: KDE Partitionmanager crashes if an USB stick is plugged in
Status: RESOLVED DUPLICATE of bug 502141
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.04.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Andrius Štikonas
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-04-30 22:24 UTC by CodeBreaker
Modified: 2025-04-30 22:43 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/171213/events/52e8a5e787a44ecdb510f1109b8dd6fe/


Attachments
New crash information added by DrKonqi (64.33 KB, text/plain)
2025-04-30 22:24 UTC, CodeBreaker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description CodeBreaker 2025-04-30 22:24:10 UTC
Application: partitionmanager (25.04.0)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.0
Frameworks Version: 6.13.0
Operating System: Linux 6.14.4-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:
On a fresh installation of Fedora 42 KDE Plasma Edition, the partitionmanager crashes while it tries to read / access all available hard drives. It happens constantly as long as the USB stick - which was used to install Fedora - is plugged in. If I unplug the USB stick the partitionmanager opens as expected.

Steps to reproduce:

1. Install Fedora 42 KDE on an available system
2. Keep the USB stick plugged in after the installation
3. Try to open partitionmanager and unlock it via polkit
4. It crashes as long as the USB stick is plugged in

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  0x00007f2e1ca6acc7 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  0x00007f2e1ca6af0f in SfdiskBackend::scanWholeDevicePartition (this=this@entry=0x562895afd9d0, d=...) at /usr/src/debug/kpmcore-25.04.0-1.fc42.x86_64/src/plugins/sfdisk/sfdiskbackend.cpp:345
#7  0x00007f2e1ca729bf in SfdiskBackend::scanDevice (this=0x562895afd9d0, deviceNode=...) at /usr/src/debug/kpmcore-25.04.0-1.fc42.x86_64/src/plugins/sfdisk/sfdiskbackend.cpp:297
#8  0x00007f2e1ca71077 in SfdiskBackend::scanDevices (this=0x562895afd9d0, scanFlags=...) at /usr/src/debug/kpmcore-25.04.0-1.fc42.x86_64/src/plugins/sfdisk/sfdiskbackend.cpp:106
#9  0x00007f2e369f232b in DeviceScanner::scan (this=0x562895b08110) at /usr/src/debug/kpmcore-25.04.0-1.fc42.x86_64/src/core/devicescanner.cpp:56


Reported using DrKonqi
Comment 1 CodeBreaker 2025-04-30 22:24:11 UTC
Created attachment 180833 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Antonio Rojas 2025-04-30 22:43:41 UTC

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