Application: nepomukindexer (0.1.0) KDE Platform Version: 4.9.97 Qt Version: 4.8.3 Operating System: Linux 3.7.0-7-generic x86_64 Distribution: Ubuntu Raring Ringtail (development branch) -- Information about the crash: Hello Community! I set up my Laptop with Kubuntu Raring alpha yesterday and installed all the available Updates. Today I got serveral error messages of nepomuk crashing with segfaults (every 5 minutes or so). I didn't do anything funny. I was just surfing the web and editing text. Strangely nepomuk seems to have stopped crashing while I'm writing this bug report. I installed the debug symbols as requested and did the report with them enabled. If you need anything else please feel free to contact me. I am a more or less experienced user but no programmer. So please go easy on me ;) Thanks and keep up the good work! The crash can be reproduced every time. -- Backtrace: Application: NepomukIndexer (nepomukindexer), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #5 Poppler::Page::textList (this=0x0, rotate=Poppler::Page::Rotate0) at poppler-page.cc:441 #6 0x00007f8e2825c600 in Nepomuk2::PopplerExtractor::parseFirstPage (this=this@entry=0x1cae800, pdfDoc=pdfDoc@entry=0x1d25c40) at ../../../../services/fileindexer/indexer/popplerextractor.cpp:118 #7 0x00007f8e2825ce41 in Nepomuk2::PopplerExtractor::extract (this=0x1cae800, resUri=..., fileUrl=..., mimeType=...) at ../../../../services/fileindexer/indexer/popplerextractor.cpp:73 #8 0x000000000040a5f0 in Nepomuk2::Indexer::fileIndex (this=this@entry=0x7fff1adb00c0, uri=..., url=..., mimeType=...) at ../../../../services/fileindexer/indexer/indexer.cpp:146 #9 0x000000000040b160 in Nepomuk2::Indexer::indexFile (this=0x7fff1adb00c0, url=...) at ../../../../services/fileindexer/indexer/indexer.cpp:101 #10 0x000000000040860e in main (argc=2, argv=0x7fff1adb0228) at ../../../../services/fileindexer/indexer/main.cpp:113 Reported using DrKonqi
Created attachment 76331 [details] First Crash after bug report submission And here we go again...
*** This bug has been marked as a duplicate of bug 312569 ***