Bug 341403

Summary: Crash
Product: [Unmaintained] Baloo Reporter: martinjeanpierre
Component: Baloo File DaemonAssignee: Vishesh Handa <me>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: triaged
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: PCLinuxOS   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description martinjeanpierre 2014-11-29 14:49:46 UTC
Crash message when booting computer.

KCrash: Attempting to start /usr/bin/baloo_file from kdeinit
KCrash: Connect sock_file=/root/.kde4/socket-petrolette/kdeinit4__0
baloo_file(4341): Communication problem with  "baloo_file" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " 

version : 4.14.3-1pclos2014
Comment 1 Vishesh Handa 2014-12-01 11:06:52 UTC
Hi. Could you possibly please attach a backtrace?

You can do that by manually running `baloo_file` and seeing if it crashes? If it does you should run it under gdb.
Comment 2 Andrew Crouthamel 2018-09-04 19:46:19 UTC
Hello! This project has been replaced with a newer system so I will be closing this bug. If you could please re-test on the latest Baloo. If the issue still present, please open a new bug under "frameworks-baloo". Thank you!
Comment 3 Andrew Crouthamel 2018-09-28 03:34:05 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-29 02:09:52 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!