Comment 3 for bug 89506

Enigma, you seem to be having the problem on a regular basis. With a little effort, you may be able to provide valuable input in identifying the problem. After you login, in a terminal give,
$ beagled --replace --fg

This will start beagle in the terminal and print all kind of lines saying what it is doing. You can ignore them. Then create a new folder or file which you think might trigger the crash. We expect the terminal at that point to have some informative output like a stacktrace of some lines saying Exception. If you see them, please copy those lines (maybe 20 more lines before that to preserve the context) and attach it to the bug.

Another user had some success by stopping the evolution-mail backend. You can give this command from a terminal,
$ beagle-config daemon DenyBackend EvolutionMail
restart beagle (using beagled --restart or logout/login) and see if it crashes.

Thanks.