Hide Forgot
Description of problem:The bug reporting icon appeared after restarting my computer yesterday. The tool reported seven apparently identical bugs dated 01/11/2012 - 01/13/2012. No additional bugs have appeared since the seventh bug. I was unable to report these bugs using the Reporting Tool because a backtrace wasn't generated. Version-Release number of selected component (if applicable): 6.12.35 How reproducible: Unknown Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: This is a copy of the log showing the backtrace failure: --- Running analyze_LocalGDB --- Analyzing coredump 'coredump' Coredump references 1 debuginfo files, 1 of them are not installed Setting up yum repositories Looking for needed packages in repositories Can't find packages for 1 debuginfo files Missing debuginfo file: /usr/lib/debug/.build-id/ee/01073456c86c3a349e64d2e4090d57b17f0a2c.debug Generating backtrace Can't set gid 989: Operation not permitted Backtrace is generated and saved, 0 bytes Can't open file './component': No such file or directory Backtrace parsing failed for . 1:0: No frame and no thread found.
Seti@home appears to be running normally at this time.
It looks like this was a bug in that particular project application, not boinc itself, I'm closing for now.