https://bugs.kde.org/show_bug.cgi?id=356389
--- Comment #2 from eric <[email protected]> --- (In reply to Vishesh Handa from comment #1) > Could you please provide a backtrace? > > Perhaps you could start baloo manually via gdb? First kill `baloo_file` and > then start it via `gdb baloo_file` and then 'start'. When it crashes, type > `backtrace` to obtain the backtrace. hello thanks for answer, i've try it but no backtrace file created, crash corrupt all answer of the system, unable to create report bug file and there is nothing in ksystemlog border crash is not reported if i start baloo in konsole and i create a folder uname i can see the crash line text but nothing else, now i'm tired about that i have disinstall baloo and suppress all folders. My system now is working fine i can't see speed difference for find folder in my ssd disk so may be a stable baloo_file will be released for my system. My kubuntu 14.10 wasn't corrupt eveything was working fine so new plasma may be the problem. regards (sorry for my bad english) -- You are receiving this mail because: You are watching all bug changes.
