Bug 403980

Summary:	Partition manager crashes with segmentation fault when finished moving or resizing partitions
Product:	[Applications] partitionmanager	Reporter:	Bruce Blore <bruceblore>
Component:	general	Assignee:	Andrius Štikonas <andrius>
Status:	RESOLVED FIXED
Severity:	crash	CC:	nate
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Bruce Blore 2019-02-06 02:49:02 UTC

SUMMARY
I am in the process of migrating my system from Debian to Kubuntu. I used the Kubuntu LiveCD (which contained the partition editor) to delete the old root and swap partitions, move and shrink the old home partition, and grow the new root partition. All partitions were ext4 except the swap partition, and my disk has MBR partitioning because my laptop does not properly support UEFI booting. At the end of both of the move/resize operations, the editor crashed with a segmentation fault. Because it crashed right at the end both times, no data was lost. I didn't have this account when it happened, but I can get a backtrace if it happens again when I finish my partitioning later.

STEPS TO REPRODUCE
1. Open the partition editor
2. Use the move and resize operation on a partition
3. Click the apply button and wait until it finishes. It seems to happen every time.

OBSERVED RESULT
All operations up to and including the first move and resize operation are performed successfully, then the editor crashes with a segmentation fault.

EXPECTED RESULT
All of my partitioning operations being completed and the editor not crashing.

SOFTWARE/OS VERSIONS
Linux: Kubuntu 18.10 livecd
(I'm not 100% sure what's on the livecd, the software below is on my Kubuntu 18.10 installation, so I'm guessing it's the same there, I'll post an update if it isn't)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
I have more partitioning to do. If I can reproduce the error and get a backtrace, I'll post it here.

Comment 1 Andrius Štikonas 2019-02-06 22:34:48 UTC

Yes, if you can obtain backtrace, it would be useful. Otherwise it's hard to fix this since I can't reproduce it.

Just to make sure, you were not closing any windows? Have operations just finished and KDE Partition Manager crashed without any of your actions or have you closed Apply Progress Dialog?

Comment 2 Bruce Blore 2019-02-07 06:07:48 UTC

I'll be more specific about what happened near the end. After I started the operation, I pressed Ctrl+Alt+F2 to switch to a console. I did this because the nouveau drivers that come with the live usb regularly cause my system to kernel panic (I'm going to get Intel integrated graphics when I upgrade), and not having a GUI on the screen was a workaround that I found. I played video games on another device while glancing at my hard drive light occasionally, so it is possible that the partition editor sat idle for a few minutes.

When I pressed Ctrl+Alt+F1 to switch back to the GUI, the partition editor window looked exactly as it did when I switched to the console. A fraction of a second later, it "jumped" to 100% (I kinda expected that) and then crashed with the segfault. This did not happen when I briefly switched to the GUI to check on the progress when it was not finished. I think the crash happened before I was actually able to interact with it, but I *might* have been able to close the Apply Progress dialog.

I will try doing a somewhat long operation and switching to the console at the start and to the GUI at the end. Hopefully, I'll be able to reproduce it then.

Based on this info I just provided, I'm thinking that the issue could be related to the parts of the application responsible for drawing the UI rather than the parts responsible for the actual partitioning. Do you recommend that I try it on my main hard drive for consistency or a flash drive that I don't care about to lower the risk of data loss?

Comment 3 Andrius Štikonas 2020-05-14 00:25:32 UTC

Tjis might be fixed in kpmcore git master although a bit hard to tell since reported didn't provide any backtrace. If it still doesn't work in future releases (I guess 4.2.0) please reopen.