Description of problem: crash on launch while having an mbr 1tb disc with a single partiotion of 100gb Version-Release number of selected component: kde-partitionmanager-25.04.0-1.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: partitionmanager killed by SIGSEGV journald_cursor: s=5a3c09978ddf48d79ba4380dc9e4ee13;i=27de07c;b=b25bbe08df4c4b12a9f14702a5f3d4b2;m=1e221b7;t=6334a83873387;x=a57da81b08cbccae 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.2-300.fc42.x86_64 package: kde-partitionmanager-25.04.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler comment: crash on launch while having an mbr 1tb disc with a single partiotion of 100gb Truncated backtrace: Thread no. 1 (1 frames) #3 KCrash::defaultCrashHandler at /usr/src/debug/kf6-kcrash-6.13.0-1.fc42.x86_64/src/kcrash.cpp:605
Created attachment 2086191 [details] File: proc_pid_status
Created attachment 2086192 [details] File: maps
Created attachment 2086193 [details] File: limits
Created attachment 2086194 [details] File: environ
Created attachment 2086195 [details] File: open_fds
Created attachment 2086196 [details] File: mountinfo
Created attachment 2086197 [details] File: os_info
Created attachment 2086198 [details] File: cpuinfo
Created attachment 2086199 [details] File: core_backtrace
Created attachment 2086200 [details] File: dso_list
Created attachment 2086201 [details] File: backtrace
I refreshed disks in the KDE Partition manager reporter: libreport-2.17.15 type: CCpp reason: partitionmanager killed by SIGSEGV journald_cursor: s=202b9ec6f7684e4ab930ed994f823b6d;i=58356b0;b=287279d4c2654dd3af473cc2f2da9408;m=82cdac0;t=633805e46bbb7;x=68b6c0dfbebf5bac 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.2-300.fc42.x86_64 package: kde-partitionmanager-25.04.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler comment: I refreshed disks in the KDE Partition manager
Bus 002 Device 042: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub Bus 002 Device 043: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s x4 sdc 3:0:0:0 disk ST316081 ST3160813AS CC2F 5SY05RM6 usb sdd 4:0:0:0 disk KINGSTON KINGSTON SA400S37480G S3H01103 50026B778421B58E usb sde 5:0:0:0 disk ST4000VX ST4000VX013-2XG104 CV11 ZTT5TZRR usb sdf 6:0:0:0 disk ST4000VX ST4000VX013-2XG104 CV11 ZTT5W673 usb reporter: libreport-2.17.15 type: CCpp reason: partitionmanager killed by SIGSEGV journald_cursor: s=abbb8593869543c5a2a7ad31458328af;i=15c5099;b=0d895e724d2b454cadfebd36c65475fe;m=311e9c1238;t=6337a0cc4eee9;x=c018b4e4eccb81a4 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.2-300.fc42.x86_64 package: kde-partitionmanager-25.04.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler
FEDORA-2025-d439dd68d8 (kpmcore-25.04.0-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-d439dd68d8
FEDORA-2025-d439dd68d8 has been pushed to the Fedora 42 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-d439dd68d8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d439dd68d8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-d439dd68d8 (kpmcore-25.04.0-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
This crash happened while I was trying to get an external USB disk drive set up for OpenZFS (with zfs installed properly). reporter: libreport-2.17.15 type: CCpp reason: partitionmanager killed by SIGSEGV journald_cursor: s=91ba45852f654d9bad2452285cad606c;i=6174977;b=9928580374394894b39d1028dcda074c;m=12812f8ffb;t=63a10f7d06854;x=8e31bde650f5b223 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.15.5-200.fc42.x86_64 package: kde-partitionmanager-25.04.3-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler
So I am using a newer kde-partitionmanager version, apparently it's unsufficient to fix such bugs. How do we proceed? Either we can reopen this bug, or I need help (instructions) on how to tell the bug reporting stuff such as abrt-cli that this isn't a duplicate.