https://bugs.kde.org/show_bug.cgi?id=487808
--- Comment #1 from Phil Hord <phil.h...@gmail.com> --- On later tests, I found that baloo_file_extractor was the busy process consuming CPU while the desktop failed to start. The file it was scanning was /home/$USER/ude_installations/.VSCode-linux-x64.*/code. It was not named ".desktop" or anything similar. I tried to repro by copying the the same binary to /home/$USER/test/, but I didn't see the same result. Removing the file from where it was solved my startup problem for now. -- You are receiving this mail because: You are watching all bug changes.
