https://bugs.kde.org/show_bug.cgi?id=403980
--- Comment #2 from Bruce Blore <[email protected]> --- 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? -- You are receiving this mail because: You are watching all bug changes.
