Summary: | Nepomuk doesn't log and handle strigi crashes sensibly | ||
---|---|---|---|
Product: | nepomuk | Reporter: | Michael Schuerig <michael> |
Component: | general | Assignee: | Sebastian Trueg <sebastian> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | Martin, trueg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Michael Schuerig
2010-03-31 11:50:58 UTC
This is similar to bug #232395 I reported some days ago, except that in my case, strigi nepomuk services complains loudly of too many crashes in ~/.xsession-errors. Did you grep your ~/.xsession-errors just for the word "crash"? But you put emphasis on how nepomuk handles those crashes. I did so as well already in bug #232398. I think your bug report contains two bug reports. I suggest you to add here all information on the UTF-8 related crashes you encounter as I am not yet sure, whether you are seeing a duplicate of bug #232395, your description sounds different. And to add your suggestions how Nepomuk should handle those crashes in bug #232398 or report a new wish if your suggestions differ. Martin, I don't agree with your assessment. Your problem and bug report is concerned with behavior that occurs in the storage backend Nepomuk uses. In contrast, this bug report is about a problem in the frontend used for extracting data from files. Ok, seems you have a clearer understanding. Point taken, bugs are linked, may the Sebastian Trueg or some other strigi / nepomuk developer finally decide on similarity. I agree that this needs to be done since there are too many cases in which strigi crashes. Are there any takers for this bug? *** Bug 232402 has been marked as a duplicate of this bug. *** *** Bug 232395 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 232398 *** |