[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 232814] New: Nepomuk doesn't log and handle strigi crashes
From:       Michael Schuerig <michael () schuerig ! de>
Date:       2010-03-31 9:51:12
Message-ID: bug-232814-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=232814

           Summary: Nepomuk doesn't log and handle strigi crashes sensibly
           Product: nepomuk
           Version: unspecified
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: sebastian@trueg.de
        ReportedBy: michael@schuerig.de


Version:            (using KDE 4.4.1)
OS:                Linux
Installed from:    Debian testing/unstable Packages

I had a PDF file from which pdftotext apparently extracted malformed UTF-8 text
which causes an assert failure in strigi (LineEventAnalyzer::handleUtf8Data).
Strigi, in turn aborts with a SIGABRT.

Nepomuk doesn't log an error nor does it in any other way indicate that
something went wrong -- which makes it rather hard to realize that something
went wrong in the first place and even harder to track down the file causing
the problem.

Currently, Nepomuk just restarts strigi and starts over from the beginning.
Instead it would be much better to

- Notify the user that a file is causing problems.
- Exclude this file from indexing as long as it remains unchanged.
- Resume indexing after the offending file.

See also
https://sourceforge.net/tracker/?func=detail&atid=856302&aid=2979889&group_id=171000
for a ticket asking strigi to be more helpful when encountering malformed
UTF-8.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]