Bug 2362719 - [abrt] kde-partitionmanager: KCrash::defaultCrashHandler(): partitionmanager killed by SIGSEGV
Summary: [abrt] kde-partitionmanager: KCrash::defaultCrashHandler(): partitionmanager ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-partitionmanager
Version: 41
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mattia Verga
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:272a8d523cc9db174096c9543b0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-28 15:11 UTC by Dan
Modified: 2025-05-04 03:02 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-04 03:02:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: proc_pid_status (1.49 KB, text/plain)
2025-04-28 15:11 UTC, Dan
no flags Details
File: maps (3.99 KB, text/plain)
2025-04-28 15:11 UTC, Dan
no flags Details
File: limits (1.29 KB, text/plain)
2025-04-28 15:11 UTC, Dan
no flags Details
File: environ (2.89 KB, text/plain)
2025-04-28 15:11 UTC, Dan
no flags Details
File: open_fds (4.71 KB, text/plain)
2025-04-28 15:11 UTC, Dan
no flags Details
File: mountinfo (3.99 KB, text/plain)
2025-04-28 15:11 UTC, Dan
no flags Details
File: os_info (719 bytes, text/plain)
2025-04-28 15:11 UTC, Dan
no flags Details
File: cpuinfo (3.19 KB, text/plain)
2025-04-28 15:11 UTC, Dan
no flags Details
File: core_backtrace (40.28 KB, text/plain)
2025-04-28 15:11 UTC, Dan
no flags Details
File: dso_list (182 bytes, text/plain)
2025-04-28 15:11 UTC, Dan
no flags Details
File: backtrace (119.08 KB, text/plain)
2025-04-28 15:11 UTC, Dan
no flags Details

Description Dan 2025-04-28 15:11:03 UTC
Description of problem:
I wanted to change the label name on a Linux formatted external drive.
I strated partitionmanager from the application menu.
It asked for my user password.
I entered the password, pressed Enter.
It displays "Scanning Devices", or something like that.
Then the program crashes.
This happens every time now.

Renaming the drive worked fine with the Disks program.

Version-Release number of selected component:
kde-partitionmanager-25.04.0-1.fc41

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         partitionmanager killed by SIGSEGV
journald_cursor: s=491c2bba56af446f9203390febd70efd;i=1224753;b=90cb5f626d8c4f0087455c30a9dc65ca;m=1c442c749;t=633d7d0c22ceb;x=a91ec8bc2454b39f
executable:     /usr/bin/partitionmanager
cmdline:        /usr/bin/partitionmanager
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.partitionmanager
rootdir:        /
uid:            1000
kernel:         6.14.3-200.fc41.x86_64
package:        kde-partitionmanager-25.04.0-1.fc41
runlevel:       N 5
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler

Truncated backtrace:
Thread no. 1 (10 frames)
 #3 KCrash::defaultCrashHandler at /usr/src/debug/kf6-kcrash-6.13.0-1.fc41.x86_64/src/kcrash.cpp:605
 #5 SfdiskBackend::readSectorsUsed at /usr/src/debug/kpmcore-25.04.0-1.fc41.x86_64/src/plugins/sfdisk/sfdiskbackend.cpp:523
 #6 SfdiskBackend::scanWholeDevicePartition at /usr/src/debug/kpmcore-25.04.0-1.fc41.x86_64/src/plugins/sfdisk/sfdiskbackend.cpp:345
 #7 SfdiskBackend::scanDevice at /usr/src/debug/kpmcore-25.04.0-1.fc41.x86_64/src/plugins/sfdisk/sfdiskbackend.cpp:297
 #8 SfdiskBackend::scanDevices at /usr/src/debug/kpmcore-25.04.0-1.fc41.x86_64/src/plugins/sfdisk/sfdiskbackend.cpp:106
 #9 DeviceScanner::scan at /usr/src/debug/kpmcore-25.04.0-1.fc41.x86_64/src/core/devicescanner.cpp:56
 #10 operator() at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/thread/qthread_unix.cpp:375
 #11 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/thread/qthread_unix.cpp:311
 #12 QThreadPrivate::start at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/thread/qthread_unix.cpp:339
 #14 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78


Potential duplicate: bug 2361447

Comment 1 Dan 2025-04-28 15:11:07 UTC
Created attachment 2087616 [details]
File: proc_pid_status

Comment 2 Dan 2025-04-28 15:11:08 UTC
Created attachment 2087617 [details]
File: maps

Comment 3 Dan 2025-04-28 15:11:10 UTC
Created attachment 2087618 [details]
File: limits

Comment 4 Dan 2025-04-28 15:11:11 UTC
Created attachment 2087619 [details]
File: environ

Comment 5 Dan 2025-04-28 15:11:12 UTC
Created attachment 2087620 [details]
File: open_fds

Comment 6 Dan 2025-04-28 15:11:14 UTC
Created attachment 2087621 [details]
File: mountinfo

Comment 7 Dan 2025-04-28 15:11:15 UTC
Created attachment 2087622 [details]
File: os_info

Comment 8 Dan 2025-04-28 15:11:16 UTC
Created attachment 2087623 [details]
File: cpuinfo

Comment 9 Dan 2025-04-28 15:11:18 UTC
Created attachment 2087624 [details]
File: core_backtrace

Comment 10 Dan 2025-04-28 15:11:20 UTC
Created attachment 2087625 [details]
File: dso_list

Comment 11 Dan 2025-04-28 15:11:21 UTC
Created attachment 2087626 [details]
File: backtrace

Comment 12 Fedora Update System 2025-04-28 16:17:56 UTC
FEDORA-2025-a14dc9f0cf (kpmcore-25.04.0-2.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-a14dc9f0cf

Comment 13 Fedora Update System 2025-04-29 03:12:18 UTC
FEDORA-2025-a14dc9f0cf has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-a14dc9f0cf`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-a14dc9f0cf

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2025-05-04 03:02:28 UTC
FEDORA-2025-a14dc9f0cf (kpmcore-25.04.0-2.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.