abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice component: kdebase-runtime executable: /usr/bin/nepomukservicestub kernel: 2.6.32.10-90.fc12.x86_64 package: kdebase-runtime-4.4.1-1.fc12 rating: 4 reason: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine)
Created attachment 405399 [details] File: backtrace
This is an issue which needs to be addressed by the upstream developers. Please file a report at http://bugs.kde.org once that is done please add the upstream bug information to this report. We will monitor the upstream report for a resolution. Thanks
KDE Version 4.4.4 is now available. Please update to the this latest release and retest the application. Please advise if you are still having the same issue as documented. Any reports not updated within 30 days will be closed. Thanks from the Fedora KDE Team
In kdebase-runtime-4.4.3-1.fc12.1, I have two further ABRT crash reports from signal 6 death. I also have two with signal 11 death, one with the 4.4.3 package, and one with the updated -4.4.4-1.fc12 as requested. The different return code probably is from a different software issue, of course. Since the 4.4.4 crash is a signal 11, should I open another bugzilla report for it? The corresponding KDE report, bug 230592, seems like it's been neglected.
Created attachment 426467 [details] Backtrace of Crash in version 4.4.4 I caught one with the same signal, in the updated packages. Looks like free-ing previously-free'd memory, to my non-expert eye.
This is two different crashed. First is duplicate of bug 583350 and the second from comment 5 is dup of bug 597611 *** This bug has been marked as a duplicate of bug 583350 ***