Starting partition manager with QT_QPA_PLATFORM=wayland fixes this, so why doesn't start like this by default? Also when run with the command above the cursor is wrong and the program is unstable, so I wouldn't trust it doing anything with my partitions. KDE Plasma Version: 5.14.90 KDE Frameworks Version: 5.54 Qt Version: 5.12.1 ADDITIONAL INFORMATION Only on wayland
(In reply to mthw0 from comment #0) > Starting partition manager with QT_QPA_PLATFORM=wayland fixes this, so why > doesn't start like this by default? Also when run with the command above the > cursor is wrong and the program is unstable, so I wouldn't trust it doing > anything with my partitions. > > KDE Plasma Version: 5.14.90 > KDE Frameworks Version: 5.54 > Qt Version: 5.12.1 > > ADDITIONAL INFORMATION > Only on wayland I don't think cursor is wrong. It uses the cursor that is defined in user's settings (which is root). As for QT_QPA_PLATFORM=wayland, partitionmanager 3.3 only depends on Qt 5.10 but new Plasma releases don't set QT_QPA_PLATFORM when Qt is 5.11 or newer. Anyway, the points above become moot with latest beta version of kpmcore/partitionmanager 4.0 since the GUI no longer runs as root. Since you are running beta version of Plasma desktop, you can try beta version of KDE Partition Manager too.
Oh, and can you mention in more details what is unstable? Just "unstable" is not very helpful for me.
(In reply to Andrius Štikonas from comment #2) > Oh, and can you mention in more details what is unstable? Just "unstable" is > not very helpful for me. Yeah, I know that isn't a very good description, but I was running it with gdb and it didn't show me a single line when it crashed. I will build and try the new version (3.80.0) anyway.
(In reply to mthw0 from comment #3) > (In reply to Andrius Štikonas from comment #2) > > Oh, and can you mention in more details what is unstable? Just "unstable" is > > not very helpful for me. > > Yeah, I know that isn't a very good description, but I was running it with > gdb and it didn't show me a single line when it crashed. I will build and > try the new version (3.80.0) anyway. Version 3.80.0 is easier to debug with gdb too. In version 3.3, when you start partitionmanager, it starts another instance of partitionmanager which runs as root. It could be that your gdb was attached to the wrong intance of partitionmanager. Version 4 beta also has two processes but different ones. One is partitionmanager process which is most of the code and a small daemon (kpmcore_externalcommandhelper) which runs as root. And the good thing is that even if partitionmanager crashes or is killed, kpmcore_externalcommandhelper will keep running until it finishes current job (not the whole operation, just particular job, but that's already much safer).
[20:09] <d_ed> stikonas: there are constant fixes to QtWayland wrt popup handling [20:10] <d_ed> there's another one on review ATM