I'm also having this problem, with it having created 7GB of error logs in less than 24 hours filling up my /home partition.
The errors in my case seemed to be...
17 Nov 2007, 23:19:21:915 - ERROR: CreateService uri is /home/mendez/.local/share/applications/vlc-usercustom.desktop
17 Nov 2007, 23:19:21:915 - ERROR: could not get file id for /home/mendez/.local/share/applications/vlc-usercustom.desktop - unable to continue indexing this file
17 Nov 2007, 23:19:21:916 - ERROR: execution of prepared query CreateService failed due to database disk image is malformed with return code 11
And as these started after an unexpected loss of power I can believe that it is caused by database corruption (or possibly filesystem - I'd installed VLC prior to the power loss) so I'm doing a reindex.
My suggestion would be that if the program encounters more than a certain continuous number of errors it simply shuts itself down (or black lists the files causing the error if that's more appropriate). I can't see any merit in it persisting, nor to creating huge volumes of logs no-one is likely to ever wade through. It's also made worse by the logs being in /home - it would be much better if they were saved to /var - I've just had problems saving work due to home being unexpectedly full.
I'm also having this problem, with it having created 7GB of error logs in less than 24 hours filling up my /home partition.
The errors in my case seemed to be...
17 Nov 2007, 23:19:21:915 - ERROR: CreateService uri is /home/mendez/ .local/ share/applicati ons/vlc- usercustom. desktop .local/ share/applicati ons/vlc- usercustom. desktop - unable to continue indexing this file
17 Nov 2007, 23:19:21:915 - ERROR: could not get file id for /home/mendez/
17 Nov 2007, 23:19:21:916 - ERROR: execution of prepared query CreateService failed due to database disk image is malformed with return code 11
And as these started after an unexpected loss of power I can believe that it is caused by database corruption (or possibly filesystem - I'd installed VLC prior to the power loss) so I'm doing a reindex.
My suggestion would be that if the program encounters more than a certain continuous number of errors it simply shuts itself down (or black lists the files causing the error if that's more appropriate). I can't see any merit in it persisting, nor to creating huge volumes of logs no-one is likely to ever wade through. It's also made worse by the logs being in /home - it would be much better if they were saved to /var - I've just had problems saving work due to home being unexpectedly full.