Bug 439462

Summary:	partitionmanager crashes after changing system colorscheme
Product:	[Applications] partitionmanager	Reporter:	ba.tahaaziz
Component:	general	Assignee:	Andrius Štikonas <andrius>
Status:	REPORTED ---
Severity:	crash
Priority:	NOR
Version First Reported In:	21.04.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description ba.tahaaziz 2021-07-04 06:20:37 UTC

SUMMARY
Changing Plasma's colorscheme while a job is active, e.g. resizing a partition, causes partitionmanager to crash.

STEPS TO REPRODUCE
1. Resize a partition (for example)
2. Change Plasma's colorscheme (System Settings > Appearance > Colors)
3. partitionmanager crashes.

OBSERVED RESULT
partitionmanager crashes after changing Plasma's colorscheme (although the the crash did not result in horrific consequences, I think.)

EXPECTED RESULT
partitionmanager should not crash mid-job when the system's colorscheme is modified.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux, Linux 5.10.47-1-lts.
KDE Plasma Version: 5.22.2
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

Comment 1 Andrius Štikonas 2021-07-04 10:30:12 UTC

Have you saved the crash backtrace?

Otherwise, I'll try to reproduce it but if it's not reproducible there might not be much I can do...

P.S. Yes, there is a bit of protection against data loss during crashes in partititonmanager, maybe that's what has saved you. KDE Partition Manager GUI runs as normal user and there is a small process running as root that actually executes all jobs. When crash happens, only GUI part crashes but root process should complete currently running partitioning command (it won't start remaining jobs in queue but that's still better than aborting in the middle of e.g. resize/move operation).

Comment 2 ba.tahaaziz 2021-07-04 17:13:09 UTC

> Have you saved the crash backtrace?

Unfortunately, I didn't. I'm sorry I can't provide this for you :/

Anyways, I'm glad partitionmanager does what it does so crashes aren't as severe. After examining for bad blocks after the crash, it turned out completely okay, and smartctl reports 0 issues.