https://bugs.kde.org/show_bug.cgi?id=400540
--- Comment #8 from Andrius Štikonas <andr...@stikonas.eu> --- (In reply to Dal Monico from comment #7) > This may be kernel related. There was a similar report just made on the > Manjaro forum regarding gparted. The user reported the same long start time > on kernels above 4.17. I can't shut down to test different kernels presently > as I'm in the middle of an operation on my server that will require it being > up for at least 12 hours. > > https://forum.manjaro.org/t/gparted-scanning-all-devices-in-4-19/64170 Indeed, could be something in the kernel. We might still be able to pinpoint what causes it. GParted uses libparted for a lot of jobs just as KPM 3.3. On the other hand you saw the same problem in kpmcore-git/partitionmanager-git. And this version does not use any libraries and just calls various linux command line programs. I'll try to write a small patch that outputs commands that are being executed to terminal. It's probably a good idea to just include it by default and hide it behind some shell variable. e.g. "KPMCORE_DEBUG=1 partitionmanager" would enable more verbose output. After that you can ask maintainer of kpmcore-git/partitionmanager-git packages to rebuild those. Then you wouldn't need to compile it yourself. -- You are receiving this mail because: You are watching all bug changes.
