abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice comment: This occurs every time I log in or restart the service. I have indexing enabled for many folders in my home and a large source code tree seems to cause the most crashes. I've seen the status window indicate it was indexing that same source tree which contains a Maven build with some very large RPMs (750MB+) in the folder. It crashes on either a 300MB RPM or the 750MB RPM almost every time I've checked it. I currently have 132,367 files in a 1.5GB index. component: kdebase-runtime crash_function: QString::shared_null executable: /usr/bin/nepomukservicestub global_uuid: bff06dab59e170bc80243a4438376fbb7b6a0433 kernel: 2.6.33.5-124.fc13.x86_64 package: kdebase-runtime-4.4.4-1.fc13 rating: 4 reason: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- 1. Log in to KDE 2. Wait for a while while it indexes my home folder 3. While indexing very large RPM files Strigi will crash
Created attachment 426923 [details] File: backtrace
*** This bug has been marked as a duplicate of bug 609541 ***