Bug 312633

Summary: nepomuk crashes wiith no apparent cause
Product: [Unmaintained] nepomuk Reporter: Alin M Elena <alinm.elena>
Component: fileindexerAssignee: Nepomuk Bugs Coordination <nepomuk-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: Joerg.Ehrichs, nepomuk-bugs
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Alin M Elena 2013-01-04 20:11:11 UTC
Application: nepomukindexer (0.1.0)
KDE Platform Version: 4.10.60 "release 16"
Qt Version: 4.8.3
Operating System: Linux 3.7.1-3-desktop x86_64
Distribution: "openSUSE 12.3 Milestone 2 (x86_64)"

-- Information about the crash:
nepomuk crashes wiith no apparent cause,,, I close it and then crashes again

The crash can be reproduced every time.

-- Backtrace:
Application: NepomukIndexer (nepomukindexer), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x00007f598bfd7af1 in Poppler::Page::text(QRectF const&, Poppler::Page::TextLayout) const () from /usr/lib64/libpoppler-qt4.so.4
#6  0x00007f598bfd7c6b in Poppler::Page::text(QRectF const&) const () from /usr/lib64/libpoppler-qt4.so.4
#7  0x00007f598c23232a in Nepomuk2::PopplerExtractor::extract (this=<optimized out>, resUri=..., fileUrl=..., mimeType=...) at /usr/src/debug/nepomuk-core-git/services/fileindexer/indexer/popplerextractor.cpp:98
#8  0x000000000040af30 in Nepomuk2::Indexer::fileIndex (this=this@entry=0x7fffbd07bdd0, uri=..., url=..., mimeType=...) at /usr/src/debug/nepomuk-core-git/services/fileindexer/indexer/indexer.cpp:146
#9  0x000000000040baa0 in Nepomuk2::Indexer::indexFile (this=0x7fffbd07bdd0, url=...) at /usr/src/debug/nepomuk-core-git/services/fileindexer/indexer/indexer.cpp:101
#10 0x0000000000408f4e in main (argc=2, argv=0x7fffbd07bf38) at /usr/src/debug/nepomuk-core-git/services/fileindexer/indexer/main.cpp:113

Reported using DrKonqi
Comment 1 Jörg Ehrichs 2013-01-06 21:46:38 UTC

*** This bug has been marked as a duplicate of bug 312569 ***